TCC Browser

Privacy Policy

TCC Browser ยท updated 24 September 2026 ยท applies to the Android and iOS apps

TCC Browser is a web browser that runs on your own device. It has no user account, no cloud sync, and sends no usage data anywhere. Everything you browse stays on this device until you delete it yourself.

๐Ÿ’พ
Your data stays on your device
History, bookmarks and settings are kept in the app's private storage on your device.
๐Ÿ”•
No analytics, no advertising
No telemetry, no user profiles, no selling data to anyone.
๐Ÿ”‘
Passwords use your OS keystore
Android Keystore, or the Secure Enclave on iPhone. Never readable on disk, and never passed to a web page.
๐Ÿ•ถ
Private sessions leave nothing behind
History, cookies and site data from a private session are thrown away when you close it.

1. What is stored on this device

All of it lives in TCC Browser's private storage on your phone โ€” an area the operating system lets only this app read. No copy is sent anywhere else.

DataWhere it livesHow to delete it
Browsing historyhistory.json Settings โ†’ Clear browsing data, or the clear button in the History panel
Bookmarksbookmarks.json Remove them one by one in the Bookmarks panel
Settings and the list of open tabssettings.json, the-dang-mo.json Turn off Reopen the tabs you had open and the tab list is no longer written
Permissions you granted to sitesquyen.json Settings โ†’ Permissions you granted to sites โ†’ Revoke
Saved passwordsAndroid: matkhau.bin, encrypted with the Android Keystore. iPhone: the system Keychain, guarded by the Secure Enclave and Face ID Settings โ†’ Saved passwords โ†’ delete one or delete all
Cookies, cache, data sites store locallyManaged by the browser engine Settings โ†’ Clear browsing data
Downloaded ad-filter rulesadblock-engine.bin Nothing to delete โ€” these are rule lists fetched from the network and contain nothing about you. Turning ad blocking off stops using them.

2. What leaves this device

Only the following, and every item is a direct consequence of something you just did:

When youโ€ฆWhat is sentWhere it goes
Open a web pageOrdinary web requests, same as any browser That site, and whatever servers that site calls
Type a search into the address barYour search terms The default search engine (Google)
Turn on ad blockingNothing about you โ€” the rule lists are only downloaded EasyList, EasyPrivacy, Peter Lowe, ABPVN
Open the TCC WalletThe web wallet talks to the TCC chain itself network3.tcc-coin.com and the TCC chain RPC
Allow a tcc-coin.com page to send notifications A device token issued by Google (Firebase Cloud Messaging) or Apple (APNs). The TCC page sends it, with the TCC account you are signed in to, to the TCC server so it can tell you about messages and incoming funds. No token is created until you allow it. Google/Apple, TCC account server ram2.tcc-coin.com
On iPhone, turn on Send speech to Apple in Settings, then speak into the microphone in a language your iPhone can't recognise by itself (for example Vietnamese) The audio of what you say, only while the microphone is listening. The app shows "your speech is sent to Apple" each time. TCC Browser doesn't keep it. Apple's speech recognition service, under Apple's privacy policy

Voice input is recognised on your device by default. On Android it always is: if the speech pack for your language isn't on the phone yet, Android downloads it once, and recognition then happens on the phone. On iPhone, Send speech to Apple is off until you turn it on. While it's off, the microphone is hidden for languages your iPhone can't recognise by itself.

Nothing here phones home. TCC Browser has no analytics server, no telemetry code, and sends the list of pages you visit to nobody โ€” including us.

3. Site permissions default to DENY

Microphone, camera, location, clipboard, notifications โ€” when an unfamiliar site asks, the browser asks you. It never grants silently. Answer once and the answer is remembered, and you can review or revoke it at any time under Settings โ†’ Permissions you granted to sites.

One exception: the browser's own infrastructure โ€” the TCC Wallet, under tcc-coin.com โ€” plus the internal tcc:// pages. That is code we wrote ourselves, and without it the wallet would have to ask for permission every time you open it.

Site notifications. Every site must ask before sending notifications, TCC's own pages included, and the default answer is NO. Each notification names the site that sent it. Only pages on tcc-coin.com can get a device token to notify you while the browser is closed. Revoke it in the same place as other permissions.

Third-party cookies are blocked by default. That kind of cookie exists almost entirely to follow you from site to site. You can turn the block off in Settings if a site genuinely needs it.

4. Private sessions

A private session is a separate browsing session, opened with the glasses button in the top bar. While you are in one the bar keeps a single fixed colour, so you can always tell which kind of session you are looking at.

5. Saved passwords

Both apps have a password store, and both follow the same four hard rules. They differ only in where the key lives: the Android Keystore on Android, the Secure Enclave (Keychain) on iPhone, unlocked with Face ID, Touch ID or your passcode. On iPhone a password is never included in an iCloud or computer backup, and it is destroyed if you remove the passcode from the device.

The four rules:

  1. Never readable on disk โ€” encrypted with your operating system's keystore (Android Keystore). The key is held by the OS and tied to your device, so another user on the same device cannot decrypt the file even if they copy it. On a device where the keystore is unavailable the browser refuses to save rather than falling back to plain text.
  2. Never passed to a web page. There is no API a page could use to ask the store anything.
  3. It only leaves the store when you ask for it โ€” you pick the account yourself, and every single time the operating system asks for your fingerprint, face or device code first.
  4. Exact hostname match โ€” no subdomain matching, no fuzzy matching. erp.tcc-coin.com.spoofed.net merely looks similar; matching by suffix would hand your password to an attacker.

On http:// pages (no lock) the browser never offers to save.

6. Children

TCC Browser is a general-purpose browser. It is not aimed at children, and it collects no data about anyone โ€” so it collects none about children either.

7. When this policy changes

The update date sits directly under the title of this page. The policy ships with the copy installed on your device, so it only changes when you update the browser. Check which build you are running under Settings โ†’ About this build.

8. Contact

Questions, or a security issue to report: admin@tcc-coin.com.