Privacy
Last updated: 28 September 2026 (for 0.4.7)
This page covers two separate things: what this website records, and what Zeron Browser sends out once you install it. For the browser, only measured facts are stated. Anything not yet measured is marked “still being checked” (nothing is at the moment). We do not write “we don't send that” about something we have not looked at.
1. This website
This site (zeron-browser.i-data.ai)
- runs no visitor analytics. No Google Analytics, no analytics script of any kind.
- sets no cookies. That is why there is no cookie banner.
- requests nothing from anyone else's servers. Even the fonts are hosted here, so while this page is open your browser connects to this server and nowhere else.
One thing is recorded: the web server's access log, the same one every web server keeps.
IP address · time · requested address · response code · what the browser says about itself (User-Agent)
It is used to run the server and to look into failures. It is not passed to anyone else, not used for advertising, and not combined with anything else to identify a person.
It is kept for 15 days. The log rolls over daily and 14 days are retained; anything older is deleted by the server automatically. No separate backup is kept.
2. Downloading the installer
Downloads are served from this server directly. No third-party service is used to distribute the files. The request appears in the access log described above.
3. What the browser sends
3.1 Update check — Windows
When only when you open [Settings → About Zeron Browser]
no periodic check, no check at startup
Where zeron-browser.i-data.ai (this site)
What just the request. There is no body
ID no install ID, no unique number, no cookies attached
The Linux build has no automatic updates. You download new versions from this site yourself.
3.2 Ad-block list updates
Every 6 hours the browser fetches the block lists from this site. It does not connect to the EasyList or EasyPrivacy servers. Those lists are fetched and converted ahead of time and placed on this server, so your browser only ever talks to this one. No cookies are attached to this request either.
3.3 Requests that go to Google — they differ by version
Zeron Browser is based on Chromium, and some of the requests Chromium makes on its own are still there; they are being removed version by version. Read the five tables as a stack: anything removed in a version later than yours is still sent by yours. If you run 0.4.3, for example, all five tables apply.
This was measured by starting the browser on a fresh profile and logging every request that left the machine. 0.4.7 was measured on Windows on pages with forms and right after a clean Windows install; 0.4.6 was measured on Windows with the settings language screen opened; 0.4.5 was measured on Linux (Windows runs the same code). 0.4.4 was measured twice on Linux and once on Windows, 0.4.3 on Linux.
Still sent by the current version (0.4.7) — applies to every version
| Destination | What the request is for |
|---|---|
update.googleapis.com andclients2.google.com · clients2.googleusercontent.com · edgedl.me.gvt1.com | Checking for and downloading browser components. From 0.4.5 only two are fetched: the revoked-certificate list (CRLSet) and certificate infrastructure data (PKI Metadata), both used for secure connections |
www.google.com/complete/search | Address-bar search suggestions. Each character you type goes to the default search engine. Opening a new tab sends an empty request first, before you type anything |
redirector.gvt1.com | Downloading a spell-check dictionary — when you turn on spell checking for a language other than Korean or English, that language's dictionary may be downloaded once. From 0.4.7 the Korean and English dictionaries ship with the installer on both Windows and Linux, so they are not downloaded |
Component updates stay — cutting them would weaken security. Address-bar suggestions stay with Google. The default search engine is Google, and the search box on the start page goes to Google search only when you search.
Removed in 0.4.7 — still sent by 0.4.6 and earlier
| Destination | What the request was for |
|---|---|
content-autofill.googleapis.com | Autofill lookups. When a page with a form was opened (including pages with just a search box), the form's structure (hashes built from field names and types) and the browser version were sent to Google's autofill server. Typed values, saved addresses, cards and passwords, and cookies were not sent. From 0.4.7 nothing is sent; filling in saved information still works, and field types are worked out inside the browser |
redirector.gvt1.com | Downloading spell-check dictionaries — Windows build. If the operating system had no spell checker for a language, the Korean and English dictionaries were downloaded too |
Removed in 0.4.6 — still sent by 0.4.5 and earlier
| Destination | What the request was for |
|---|---|
translate.googleapis.com | When you opened the settings screen, the list of languages available for translation was fetched. No visited pages or typed text were included. From 0.4.6 the list built into the browser is used |
clients2.google.com(Chrome Web Store) | On Windows, if an extension was registered for Chrome on the PC (for example Adobe Acrobat), downloading its file from the Google Web Store — even before you approved it. Without approval it was not turned on. Only on PCs with such a registration |
Removed in 0.4.5 — still sent by 0.4.4 and earlier
| Destination | What the request was for |
|---|---|
clients2.google.com/time | Checking whether the device clock is correct. Every launch |
| The default search engine (Google out of the box) | Preconnect: opening a connection in advance so the first search is faster. No path, cookies or search terms were sent |
| The default search engine (default Google: www.google.com) | Address-bar search warm-up: a real request that fetched part of the search page as soon as you clicked the address bar, with cookies (no search terms) |
redirector.gvt1.com | Downloading the spell-check dictionary — Linux build. From 0.4.5 the Korean and English dictionaries ship with the installer, so nothing is downloaded (the Windows build from 0.4.7 — see above) |
edgedl.me.gvt1.com (Google) | Seven unused components fetched through component updates: the on-device AI model list (about 2 MB per new profile), optimization hints, Privacy Sandbox attestations, trust token keys, an agent safety list, a CAPTCHA provider list and price extraction rules |
Removed in 0.4.4 — still sent by 0.4.3 and earlier
| Destination | What the request was for |
|---|---|
accounts.google.com | Asking whether a Google account is signed in on this device. Sent on every launch although Google sign-in was off, and if Google cookies were on the device, they went with it |
www.google.com/async/folaecsp.withgoogle.com | Checking whether AI Mode is available |
android.clients.google.commtalk.google.com | Registering for Google push notifications, attempted on every launch even with sign-in and sync off. When registration succeeded, an identifier and tokens issued by Google were stored on the device (Windows and Linux alike) |
Website notifications are different. If you allow a website's notifications and that site asks for a push subscription, the browser registers the device with Google's push service (FCM, android.clients.google.com) so that notifications can be delivered. A device identifier and registration token are then stored in the profile (GCM Store). This applies to every version. If you do not allow notifications, nothing is registered. Stored records can be removed the same way as below.
Push data already stored. From 0.4.4 on, this registration is not used and nothing is sent to Google. However, records already stored by 0.4.3 or earlier are not removed by updating; they stay in the profile. On Windows, close the browser and delete the folder below. If you use more than one profile, also delete the GCM Store folder inside the other profile folders, such as Profile 1 and Profile 2. Do not delete the whole User Data folder — your bookmarks and saved passwords are in it. On Linux, first update to 0.4.6 or later, then close the browser and delete ~/.config/zeron/Default/GCM Store (other profiles: ~/.config/zeron/Profile 1/GCM Store and so on). Do not do this on 0.4.5 or earlier — that version shares its profile folder with Chromium, so you could delete Chromium's data.
%LOCALAPPDATA%\ZerOn\User Data\Default\GCM Store
The Linux build has no automatic updates. Linux users on an older version keep sending whatever was removed after their version until they download and install the new file themselves — get it from the download section. On Windows, you move to a new version when you open Settings → About Zeron Browser.
We cannot claim this browser sends nothing to Google. It would read better, and it would not be true.
3.4 What does not go out
| Feature | State |
|---|---|
| Safe Browsing (sending visited addresses to Google to be checked) | Off, and removed from the settings screen |
| Translation offers | Off. Page content is not sent for translation (0.4.5 and earlier fetched only the language list on the settings screen — see 3.3) |
| Google account sign-in and sync | Off |
| Zeron account | Not offered yet. The “Sign in” button in the toolbar is a placeholder for a future Zeron account: clicking it does not sign you in, sends no request, and has nothing to do with Google accounts. Before it is offered, this page will say what it stores |
| Password breach checks | Off |
| Spell checking | Done on the device. The text being checked is not sent anywhere. With Korean as the language, Korean and English checking are both on from the start; you can turn them off in Settings → Languages |
| Suggested content on the new tab page | Not fetched |
| Alternative addresses on connection failure | Not sent |
| DNS prefetching for links on a page | Not done |
| Crash reports | Not sent. The reporting tool ships with the installer, but consent is always off |
3.5 When installing
The Windows installer does not contact Google or our servers while installing. It only unpacks what is inside the installer file; it downloads nothing and reports nothing. This was measured by running the 0.4.6 installer as released on a clean copy of Windows and recording all network traffic. At the moment installation finishes, lookups to Microsoft servers appear; Windows makes these itself when a new program is registered. After installation the browser opens, and from then on the requests in 3.3 apply.
Installing the Linux .deb registers no repository or signing key and uses no network during installation. apt does fetch required libraries from your distribution's repositories — that is apt's doing, not Zeron's.
The history, downloads, extensions, about, settings and new tab screens were also opened one by one and measured; nothing went out beyond what the tables above list (0.4.6, Windows).
3.6 Things that stay on your device
Annotations you draw on a page and the screenshots you capture are stored on your device only. They are not uploaded, and there is no upload feature to use.
History, bookmarks and saved passwords use Chromium's own storage and stay on the device. With sync off, they go neither to this server nor anywhere else.
They are stored in the folders below. From 0.4.6 the Linux build uses a folder of its own, separate from Chromium. On first run it moves the contents of the old folder (~/.config/chromium); on a PC with Chromium installed it copies them instead and leaves Chromium's copy alone.
Windows %LOCALAPPDATA%\ZerOn\User Data Linux ~/.config/zeron (from 0.4.6)
4. What we do not do
- We do not sell personal data or hand it to other companies.
- We show no advertising and build no advertising profile.
- We place no identifying number of our own in the browser. Up to 0.4.3, a successful push registration (see 3.3) stored an identifier and tokens issued by Google on the device. From 0.4.4 on, the browser no longer requests one on its own; one is received only if you allow a website's notifications. How to remove them is in 3.3.
5. Contact
For questions about this page or about privacy, and to report a security issue:
browser@i-data.ai
Details for security reports are also in security.txt.
6. When this page changes
The “last updated” date at the top changes with it. If what the browser sends changes, that change is described here.
← Back to home