What leaves your computer
The rule
Section titled “The rule”The browser engine makes no Ant0 service calls. The app and background service make the connections below. Profile names and notes, cookies, browser storage and proxy details are stored on your computer. Optional crash reports can contain profile identifiers or operator-entered diagnostic text. While you are signed in, the app also sends profile and identity identifiers for claims and persona issuance.
Connections
Section titled “Connections”| Purpose | Where | What is sent | Switch |
|---|---|---|---|
| Stable release download and update check | releases.ant0.link | Ordinary HTTP request metadata, including IP address, requested version or file, platform headers and time. | The engine download is required. Update checks are in Settings → Network and are on by default. |
| Encrypted-engine download | api.ant0.link, then releases.ant0.link | The app requests an authenticated download grant with the exact version, platform, device and workspace. The encrypted file request also carries ordinary HTTP metadata. | Used for engine releases that require a signed-in download grant. |
| Authentication and sessions | api.ant0.link | Email and password over TLS, platform, app version, and Ed25519 and X25519 public device keys. Native clients send a hardware-derived device identifier and hash. The web account shell sends a persistent random browser-device identifier and the hash of its local random seed instead. Session records include IP address and user agent. | Required for the web account shell and for signing in on the desktop; see Account. |
| Web sign-up verification | verify.ant0.link, then challenges.cloudflare.com | A fresh random correlation value is placed in the verification URL. Cloudflare receives ordinary request and challenge data. A single-use verification token returns to the account window in memory and is not persisted. | Runs when you start verification from the web sign-up form. |
| Profile claims and identity issuance | api.ant0.link | Profile UUID, identity key and optional operating-system or browser hints. The cloud stores claim and audit hints and the issued persona. | Runs when a profile is claimed for your workspace. |
| Heartbeat | api.ant0.link | Running-profile count, app and default-engine versions, integrity hashes, device and workspace identifiers. The server also receives the request IP address and derived country. | Runs while the desktop app is signed in. |
| Proxy checks | ip.ant0.link; last-resort fallbacks api.ipify.org and ip-api.com | The request goes through the proxy being tested, exposing its exit IP and ordinary request metadata. ip.ant0.link keeps no request logs. The third-party fallbacks are used only if the primary check fails and have their own policies. | Runs only when you add or check a proxy. |
| GeoIP database | releases.ant0.link | A periodically refreshed database is downloaded directly and cached locally. The request exposes ordinary HTTP metadata; it does not go through the tested proxy. | Triggered by a proxy check when the cache is missing or stale. |
| Crash reports | errors.ant0.link | Errors and stack traces; release and environment; current route and theme; operating-system and device context; and, for background-service failures, exit status and final standard-error line. Known tokens, proxy credentials and data-folder paths are scrubbed. Profile identifiers or operator-entered text may still appear in diagnostic fields. Reports are retained for 90 days. | Settings → Network, on by default and disclosed at first run. |
The app does not intentionally send analytics. This website also runs no intentional analytics.
Cloudflare Turnstile executes only at verify.ant0.link; ant0.link/turnstile redirects there.
The /account page does not execute Turnstile. Cloudflare may inject an analytics beacon, but the
site’s content security policy blocks it.
The account service is configured to send transactional email, including verification codes, through Resend. Resend receives the recipient address and message contents. Web sign-up and email verification are live.
Paid plans are bought in the web account and paid in cryptocurrency. The account service creates the
invoice; the payment itself happens on a hosted invoice page that you open in a new tab — our own
BTCPay Server at pay.ant0.link for on-chain Bitcoin, or NOWPayments, which is a third party with
its own policies. The desktop app and the browser engine take no part in payment.
Inside a profile
Section titled “Inside a profile”When a profile is running, its browser connects to the websites you visit through the proxy you assigned, exactly as any browser would. Ant0 is not in that path and does not see the traffic. A profile without a proxy uses your computer’s connection directly.
Where your data is
Section titled “Where your data is”The data folder (Settings → Data) holds profile names and notes, cookies, browser storage, proxies (credentials encrypted at rest), installed engines and logs. Back it up like any other folder; moving it to another drive is a setting. While you are signed in, Ant0’s cloud stores profile claims and audit hints plus the issued persona associated with each claimed profile. Optional crash reports can also contain profile identifiers or operator-entered diagnostic text.
The privacy policy says the same in legal terms and covers the account data held on Ant0’s servers.
© 2026 Ant0