Privacy
Last updated: 23 September 2026
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”. 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 do go to Google
Zeron Browser is based on Chromium, and some of the requests Chromium makes on its own are still there. This was measured with a window open: a run on a fresh profile, a new tab, and a second run on the same profile, logging every request that left the machine.
| Destination | What the request is for |
|---|---|
clients2.google.com | Checking whether the device clock is correct |
update.googleapis.com | Checking for and downloading browser components, such as the certificate lists |
redirector.gvt1.com | Downloading the spell-check dictionary, handed off to a nearby server that serves the file |
accounts.google.com | Asking whether a Google account is signed in on this device |
android.clients.google.com | Registering for Google push notifications |
mtalk.google.com | The push service's connection endpoint. Only a name lookup was observed |
www.google.com | Address-bar search suggestions |
Three of these deserve to be spelled out.
The account query. Zeron Browser has Google sign-in turned off, and Chromium sends this query anyway. If Google cookies are present on the device, those cookies go with the request. If the browser holds no Google cookies, nothing identifying is sent.
Push registration. With sign-in and sync both off, the browser still tries to register the device with Google. Google currently rejects it — the reply says the endpoint no longer exists. Being rejected does not stop the request from going out. And on first run the browser receives an identifier from Google, stores it on the device and uses it from then on.
We have decided to remove this push registration. The request is rejected, so it does nothing for you, and it leaves an identifier behind. The version currently offered, 0.4.3, still sends it. When a version without it ships, this page will be updated, along with how the stored identifier is cleared.
Address-bar suggestions. What you type in the address bar is sent to fetch suggestions. Opening a new tab sends an empty request first, before you type anything.
In the current version, none of these seven are blocked. update.googleapis.com is how revoked-certificate lists arrive — cutting it would weaken security. Address-bar suggestions stay with Google. Google is the default search engine, and getting suggestions as you type is a useful feature. The empty request sent when a new tab opens is part of that feature.
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 |
| Google account sign-in and sync | Off |
| Password breach checks | Off |
| Spell checking | Done on the device. The text being checked is not sent anywhere (only the dictionary file is downloaded) |
| Suggested content on the new tab page | Not fetched |
| Alternative addresses on connection failure | Not sent |
| DNS prefetching | Not done |
| Crash reports | Not sent. The reporting tool ships with the installer, but consent is always off |
3.5 Still being checked
One thing remains: whether the Windows installer uses the network while installing. Everything above was measured on the Linux build with a window open; if the Windows build differs, that will be stated here.
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.
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. Note, however, that the push registration in 3.3 means an identifier issued by Google is stored on the device.
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