Privacy Policy

1. Scope of this policy

This policy covers the BasyaNet public download website, files served from it, native Android/ChromeOS and iOS source packages, and BasyaNet desktop browser packages made available through the site.

It does not replace the privacy policies of third-party websites, operating-system vendors, search providers, hosting providers, download mirrors, or websites you visit through BasyaNet. Once you interact with a third-party service, that service's own terms and privacy practices apply to its processing.

2. About the BasyaNet project

BasyaNet is an independent browser project. This package does not identify BasyaNet as a subsidiary, partner, sponsored product, or official product of any operating-system or search-provider company.

3. Information the BasyaNet website collects directly

The public download pages remain simple, but this package also contains an optional serverless /api/account endpoint for BasyaNet Account. The ordinary download pages do not require an account.

The BasyaNet site code does not provide:

• a payment or checkout system;
• a BasyaNet advertising network;
• a BasyaNet marketing-profile database;
• a BasyaNet server-side search engine or crawler;
• a custom first-party analytics script in this package.

Browsing and downloading BasyaNet does not require a name, password, birthday, postal address, telephone number, or payment card. If you voluntarily use BasyaNet Account, the client sends the normalized email address and password over HTTPS during create/sign-in. The password is immediately verified with a salted scrypt hash and is not stored as plaintext.

4. Website hosting and infrastructure data

The public BasyaNet site may be deployed through Vercel. Like other web-hosting and content-delivery providers, Vercel may process technical information necessary to receive a request and deliver the site or a download.

According to Vercel's published privacy information, that can include:

• Internet Protocol (IP) address;
• city/country or approximate location derived from IP address;
• system configuration and device/network information;
• request, diagnostic, performance, and security information;
• traffic associated with visits and file requests.

BasyaNet does not control Vercel's infrastructure logging or retention practices. Vercel's own Privacy Notice governs information Vercel processes as a platform provider.

4A. Account infrastructure

The BasyaNet account API uses a dedicated BasyaNet schema in Supabase PostgreSQL to retain account authentication metadata, expiring session records, rate limits, and encrypted sync blobs. Supabase may process technical request information under its own privacy terms. Legacy Upstash Redis records may be read only to migrate accounts created before this change.

After successful account creation or sign-in, BasyaNet may use Gmail to send a rate-limited transactional message only to the authenticated account address. Google receives that email address and the message content needed for delivery. The endpoint does not accept a separate arbitrary recipient.

Credentials are kept in private server environment variables and are not included in public website files, browser source, or downloadable archives.

5. Cookies, browser storage, and local browser data

The BasyaNet download-page code does not intentionally set a first-party advertising or tracking cookie. The website is static and this package does not include a BasyaNet advertising SDK, Google Analytics, Meta Pixel, or equivalent first-party tracking script.

Browsers and third-party sites can still keep their own normal cache, history, cookies, permissions, site data, or download metadata according to their settings.

6. ChromeOS native application

The ChromeOS edition is a genuine Android application designed for ChromeOS's Android subsystem (ARC/ARCVM). It is not a PWA and does not require the Linux/Crostini development environment.

On supported Chromebooks, the normal no-Linux distribution route for Android apps is Google Play. Google Play and ChromeOS may process device, account, installation, diagnostic, and security information under Google's own privacy policies.

7. Search queries and third-party websites

In the ChromeOS native edition, text that is not recognized as a direct website address is turned into a Google Search URL locally in your browser. The resulting request is then opened directly with Google. BasyaNet does not operate a BasyaNet search backend for that query and does not store the search query in a BasyaNet server-side index.

Google and other websites you choose to open may receive and process information such as your query, IP address, browser/device information, request date/time, referrer information, cookies, account state, and other data under their own privacy policies and account settings.

Quick links such as YouTube, Gmail, Google Drive, or Wikipedia simply open those third-party destinations. They are not hosted or operated by BasyaNet.

8. Software downloads and installer network requests

When you download a BasyaNet installer, portable package, source archive, or other release file, the hosting infrastructure may process the normal technical information associated with the request, including the IP address and request metadata needed to deliver the file.

Some BasyaNet installers download the appropriate Electron/Chromium runtime during installation rather than bundling the entire runtime into the small initial installer. Those runtime requests can go to third-party release-hosting or mirror providers. Those providers can receive ordinary request information such as your IP address and user-agent/network information.

Installer downloads and application downloads saved to your computer remain on your device until you delete them.

9. Information stored by BasyaNet browsers

The Windows, macOS, and Linux desktop editions use Electron/Chromium, while Android and ChromeOS use Android System WebView. They store browser-specific information locally so features work between launches.

Depending on the features you use, local BasyaNet data can include bookmarks, normal history, theme/settings, proxy configuration on desktop, local hosted-site registrations on desktop, browser session/cache/site data, and files you intentionally download or save. Most browser data remains local unless you voluntarily enable account sync.

BasyaNet Account and encrypted sync

Desktop, Android, and ChromeOS BasyaNet include an optional account screen. Creating or signing in sends the normalized email and password over HTTPS for authentication. The backend stores the email, random salts, a versioned salted scrypt password hash, hashed session tokens, and an encrypted sync record. It never stores the plaintext password.

Bookmarks, normal history, and theme are encrypted in BasyaNet with AES-256-GCM before upload using a key derived on the device from the password and account sync salt. The backend stores the encrypted blob, not readable bookmark/history contents. Signed-in installations decrypt and merge locally, and revision-aware writes reduce accidental overwrites.

Secure-mode history, cookies, cache, website passwords, downloads, arbitrary site data, and local hosted files are not synced. Account deletion removes the server account and encrypted sync record when reachable, but local bookmarks, normal history, and theme remain until separately cleared.

After successful account creation/sign-in, Gmail may send a rate-limited transactional message to the authenticated account address. Email failure does not fail authentication and BasyaNet does not claim a message was sent when it was not.

Local protection

Desktop BasyaNet uses Electron's operating-system-backed safeStorage encryption where available. Android and ChromeOS keep account session material encrypted with Android Keystore. Website passwords are not part of the BasyaNet Account feature.

10. Secure mode

Desktop BasyaNet includes a Secure mode intended to reduce persistent local traces inside BasyaNet. Secure tabs use a temporary, non-persistent browser session and are not added to BasyaNet's own normal browsing-history list.

BasyaNet attempts to clear the temporary Secure-session storage, cache, authentication data, and network connections at appropriate lifecycle points such as startup, closing the last Secure tab, and application exit.

11. VPN, proxy, and network-routing features

BasyaNet can follow the computer's normal/system network configuration and can support manually configured proxy routing for browser sessions. If you choose to configure a proxy, the proxy operator can receive traffic and technical information according to that provider's own practices.

BasyaNet does not itself operate a public VPN or proxy service through this download website. Opening the Windows VPN settings shortcut merely sends you to the operating system's own networking controls.

12. Local site hosting

Desktop BasyaNet can host files or folders that you explicitly select so they can be viewed through the browser's local BasyaNet hosting system.

Local hosting is designed to remain local-only by default. If you explicitly enable a LAN-accessible mode, other devices that can reach the relevant computer/network address may be able to access the material you chose to host.

BasyaNet does not need to upload those selected local files to the public BasyaNet website merely to serve them through its local hosting feature.

13. Sale, sharing, and disclosure of personal data

The BasyaNet project does not operate a first-party advertising profile or data-broker business through this site. The optional experimental account backend does store account authentication metadata and encrypted sync blobs, and this package does not contain code intended to sell visitors' personal information.

Information can nevertheless be processed by independent third parties when necessary for the service you choose to use—for example Vercel when serving the website, a search provider when you search, a website when you visit it, or a runtime/download host when an installer downloads required components.

Information may also be disclosed if legally required, or where reasonably necessary to address security, fraud, abuse, or legal claims.

14. Data retention

The experimental account backend retains account authentication metadata and the latest encrypted sync blob until the account is deleted. Session records expire automatically. Hosting/database/email providers may also retain operational logs under their own policies.

Hosting providers and third-party services keep their own logs and records according to their own retention policies. Local desktop-browser data remains on your device until BasyaNet, the operating system, the browser engine, or you remove it.

15. Security

BasyaNet aims to reduce unnecessary collection and uses ordinary platform security mechanisms where available. Download packages may include integrity checks, and desktop application data may use operating-system-backed encryption when available.

No website, browser, encryption mechanism, download, or network connection can be guaranteed perfectly secure. Users should keep their operating system and browser components updated and should use trusted networks and security practices appropriate to their situation.

16. Privacy choices and data-subject rights

Depending on where you live, privacy law may provide rights such as access, correction, deletion, restriction, objection, or portability for personal data controlled by a particular organization.

BasyaNet cannot directly delete records held independently by Vercel, Google, another website, your ISP, or another provider. Requests concerning those providers should be directed to the provider that controls the relevant information.

For BasyaNet-controlled local data, practical choices include:

• clearing BasyaNet history or browser data from the desktop application;
• using Secure mode when you do not want a visit added to BasyaNet's normal history;
• removing bookmarks, downloads, or locally hosted-site registrations you no longer want;
• deleting the experimental BasyaNet account from Experimental features, which asks the backend to delete the account and encrypted sync blob when reachable;
• clearing the native ChromeOS app data through ChromeOS/Android app settings;
• uninstalling BasyaNet if you no longer want its local application data.

Do Not Track and Global Privacy Control

The current static BasyaNet site does not run a first-party behavioral-advertising system, so it does not build a BasyaNet cross-site advertising profile regardless of a Do Not Track or Global Privacy Control signal. Third-party providers may handle such signals according to their own policies.

17. Children's privacy

The BasyaNet download website is a general-purpose software site and is not designed as a child-directed account or social service. The current site does not ask visitors to create profiles or submit age, school, parental, or other child-specific information. The optional desktop account does not request date of birth or child-specific profile information.

If the project later adds accounts, social features, advertising, forms, or other collection directed at children, this policy and the underlying product design should be reviewed before those features are deployed.

18. International processing

Internet infrastructure is global. Hosting providers, search providers, download hosts, and destination websites may process information in countries other than the one where you are physically located. Their respective privacy notices explain their international-transfer practices and legal bases.

19. Built-in copy inside BasyaNet

BasyaNet 3.7.6 includes Privacy & Legal directly inside the browser. On Windows, macOS, and Linux it is available as basyanet://privacy from the ⋮ menu and Settings. The native ChromeOS app includes its own local Privacy & Legal page in the app package.

20. Changes to this policy

This policy may be updated when BasyaNet's website, hosting, browser features, search provider, analytics, advertising, accounts, cloud synchronization, or data practices materially change. The effective date at the top of this page should be updated when substantive revisions are published.

21. Privacy contact

This package does not invent or publish an email address that has not actually been created. If the BasyaNet project publishes an official contact method on its website or project page, privacy questions can be sent through that method.

22. Platform names, trademarks, and ownership

Trademark attribution

• Microsoft and Windows are trademarks of the Microsoft group of companies.
• Apple, Mac, and macOS are trademarks of Apple Inc., registered in the U.S. and other countries and regions.
• Google, ChromeOS, Chromebook, Android, and Google Play are trademarks of Google LLC.
• Linux® is the registered trademark of Linus Torvalds in the U.S. and other countries.
• All other product names, company names, trademarks, service marks, logos, and brands remain the property of their respective owners.

BasyaNet does not claim ownership of those third-party platform names or trademarks. Their appearance on the download page is solely for identifying the system a BasyaNet build is intended to work with.

BasyaNet artwork

The cat photograph/icon used as BasyaNet's project artwork is not a Microsoft, Apple, Google, Linux, or other platform logo. It is used as BasyaNet's own visual identity.