Transparency
Zcan transparency
Transparency
What leaves your device when you use each part of Zcan, who receives it, and how those services are doing right now.
Zcan is hosted on Vercel. Like any web host, it sees your IP address and the pages and API calls your browser requests.
Zcan is open source under the AGPL-3.0. Everything on this page can be checked against the code. Read the code on GitHub
Service health
Zcan API
Checking…
Counted by this browser during this visit, while this page or the status page is open. Checks repeat every 30 seconds.
Full status pageWhat each feature touches
Swap
- Via Zcan's server
- Browser → third party
The pair, amount, your payout address and your refund address, to get a quote and create the order. Then the deposit address, to follow the order. Coin icons load straight from jsDelivr.
Who receives it:NEAR Intents 1Click, through Zcan's server. jsDelivr, from your browser.
Send
- Via Zcan's server
- On your device
Each part of the send is its own swap order: addresses and amounts. The batch itself is saved only in this browser.
Who receives it:NEAR Intents 1Click, through Zcan's server.
Request
- On your device
The request is made on your device. The link carries the address, amount and note in its URL, so they reach Zcan's host whenever someone opens it. Zcan doesn't store requests.
Who receives it:Vercel (hosting), when the link is opened.
History
- On your device
- Via Zcan's server
History, batches, alerts and settings stay in this browser. Backups are files you download. While a swap is in progress, open Zcan pages check its status every 10 seconds, sending only the deposit address.
Who receives it:NEAR Intents 1Click for status checks, through Zcan's server. Backups go nowhere.
Markets
- Browser → third party
- Via Zcan's server
- On your device
A live price connection from your browser, which shows your IP address. Price history comes through Zcan's server. Alerts are checked in this browser and notify you locally.
Who receives it:Coinbase, from your browser. CoinGecko, through Zcan's server.
Network
- Via Zcan's server
Nothing about you. Zcan's server fetches the chain stats.
Who receives it:Blockchair and zcashexplorer.app, asked by Zcan's server.
Status
- Via Zcan's server
- Browser → third party
Nothing about you. Zcan's server checks each service, and your browser watches the Coinbase price feed.
Who receives it:1Click, CoinGecko and Coinbase, asked by Zcan's server.
Link cleaner
- On your device
Nothing. The link is cleaned on your device and never opened.
Who receives it:No one
Photo cleaner
- On your device
Nothing. The photo is read and re-saved in your browser.
Who receives it:No one
Document cleaner
- On your device
Nothing. The cleaning code loads from Zcan once, and your file never leaves your device.
Who receives it:No one
Clipboard guard
- On your device
Nothing. The clipboard is read on your device, only when you allow it.
Who receives it:No one
Address checker
- On your device
- Browser → third party
Detection is local. Only if you ask for on-chain activity does your browser send the address to a public explorer for that chain.
Who receives it:Blockchair (Zcash), PublicNode (Ethereum) or mempool.space (Bitcoin), from your browser, on request.
Password check
- Browser → third party
The first 5 characters of your password's SHA-1 hash, never the password. Responses are padded so their size gives nothing away.
Who receives it:Have I Been Pwned, from your browser.
Fingerprint test
- On your device
Nothing. Every signal is measured and scored in your browser.
Who receives it:No one
Email aliases
- On your device
Nothing. Alias ideas are made on your device. Provider sites open only if you click them.
Who receives it:No one
Agents
- Via Zcan's server
What you type, and the searches the agent writes. To limit abuse, your IP address is held in server memory for up to an hour.
Who receives it:Zcan Privacy Model, Zcan’s own model on GPUs Zcan rents from Modal, through Zcan’s server. No AI company receives it. Tavily for web searches, when switched on.
Wallet pay
- Browser → third party
- Via Zcan's server
Your wallet connects through Reown, which sees your public address. Your wallet signs the transfer; Zcan never sees your keys. The transaction hash then goes to 1Click so the swap starts sooner.
Who receives it:Reown (WalletConnect), from your browser. NEAR Intents 1Click, through Zcan's server.
Training contributions
- Opt-in
- Via Zcan's server
Only if you choose to share a finished agent run: the anonymized transcript you reviewed. You can withdraw it later from this browser.
Who receives it:Zcan's database (Upstash Redis), through Zcan's server.
Referral links
- On your device
- Via Zcan's server
Only if you opened someone’s referral link: their NEAR account, kept in this browser for 30 days and sent with your swap quotes so part of the fee is paid to them. Nothing about you is added.
Who receives it:NEAR Intents (1Click), through Zcan’s server. The referrer’s share is a public on-chain payment.
Language
- On your device
If you pick a language, a cookie named zcan-locale remembers it (one value, e.g. “es”, kept a year) so links open in your language. It identifies nothing about you. “Forget everything” on the History page removes it.
Who receives it:Zcan’s site only, with each page request, to pick the language.
Crash reports
- Via Zcan's server
Only when a page breaks, unless you switch it off in Settings: the error message and the page it happened on, with addresses, keys, emails, links and ids stripped out, plus your browser’s name and version. No IP address, cookies or query strings.
Who receives it:Zcan’s database (Upstash Redis), through Zcan’s server. Kept 14 days.
Third parties
| Service | Used for | What it receives | Policy |
|---|---|---|---|
| NEAR Intents (1Click) | Swaps, private sends and wallet pay | The addresses and amounts of your order, sent by Zcan's server to create and track it. | Website(NEAR Intents (1Click)) |
| ChangeNOW | Backup swaps, only while NEAR Intents is downOnly when switched on | For backup swaps only: both addresses, the amount and the deposit. Requests come from Zcan's server, so not your IP address. It can hold a swap for an ID check. | Privacy policy(ChangeNOW) |
| Coinbase | Live prices | A price-feed connection from your browser, which shows your IP address. Nothing else about you. | Privacy policy(Coinbase) |
| CoinGecko | Price history | Nothing about you — Zcan's server fetches the charts. | Privacy policy(CoinGecko) |
| Blockchair | Network stats and Zcash address activity | Nothing about you for network stats. For an activity check you ask for, the Zcash address, from your browser. | Website(Blockchair) |
| zcashexplorer.app | Network stats | Nothing about you. Zcan's server fetches the chain info. | Website(zcashexplorer.app) |
| Modal | GPU hosting for Zcan’s own AI model | What you type into an agent, processed by Zcan’s model deployment and not logged. No AI company receives it. | Not published |
| Tavily | Agent web searchOnly when switched on | The search queries an agent writes while it runs. | Privacy policy(Tavily) |
| Have I Been Pwned | Password check | The first 5 characters of your password's SHA-1 hash, from your browser — never the password itself. | Privacy policy(Have I Been Pwned) |
| Reown (WalletConnect) | Paying from a wallet | Wallet connection details, including your public address — only if you connect a wallet. | Privacy policy(Reown (WalletConnect)) |
| PublicNode | Ethereum address activity | The Ethereum address, from your browser, only when you ask for an activity check. | Website(PublicNode) |
| mempool.space | Bitcoin address activity | The Bitcoin address, from your browser, only when you ask for an activity check. | Website(mempool.space) |
| jsDelivr | Coin icons | Requests for icon files from your browser, which show your IP address and which coins are on screen. | Website(jsDelivr) |
| Vercel | Hosting | Your IP address and the pages and API calls your browser requests, like any web host. | Privacy policy(Vercel) |
| Upstash Redis | Training contributions, crash reports and rate limitsOpt-in | The anonymized runs people choose to share, scrubbed crash reports (kept 14 days) and salted hashes of IP addresses used for rate limits (kept 1 hour). Written by Zcan's server. | Privacy policy(Upstash Redis) |
The agents' model
Agents run on Zcan Privacy Model, Zcan’s own model, on GPUs Zcan rents from Modal. What you type goes only to that deployment: no AI company receives it, and Zcan doesn’t log it.
Web searches an agent writes still go to Tavily when search is switched on.
Zcan is also training its own privacy model, using agent runs people chose to share, anonymized before they're stored.
Proof, not promises
The link, photo and document cleaners carry a “Works offline” badge and count the network requests your browser makes while they run, using the browser's own records. Turn off Wi-Fi and try them. The count includes anything else the page does at that moment, such as a background order check, and shows where it went.