NANb Chat — Privacy Policy
Last updated: June 27, 2026
NANb Chat (“the app”, “we”, “us”) is a privacy-focused, end-to-end-encrypted messenger operated by the independent developer of NANb Chat. This policy explains what information the app handles, what we can and cannot see, and the choices you have.
- We can’t read your messages. Every message and media file is end-to-end encrypted on your device. Our servers only store and relay encrypted data — we never have the keys.
- No phone number, no email. You sign up with a username you choose.
- No tracking. No analytics, no telemetry, no third-party crash reporting, and no advertising.
- Network privacy by default. The app routes its traffic through the Tor network, so our servers don’t see your device’s IP address.
- You’re in control. You can delete your account and data from inside the app at any time.
1. Who we are and how to contact us
NANb Chat is operated by its independent developer. For any privacy question or request, contact us at contact@nanb.us.
2. Information the app handles
2.1 Account information
When you create an account you choose a username. We store:
- your username and an internal account identifier;
- one or more device identifiers for the devices you link;
- the public cryptographic keys for each of your devices (public keys and “key packages” used to establish encryption — never private keys).
We do not collect your real name, phone number, email address, date of birth, or any government identifier.
2.2 Messages and media
Messages, photos, videos, voice messages, and files you send are end-to-end encrypted on your device before they leave it. Our servers store and forward only the resulting ciphertext and cannot decrypt it.
- Encrypted messages are held on our servers only until delivered to the recipient’s devices, then removed. Undelivered messages expire after a limited period.
- Encrypted media is stored in encrypted form in cloud object storage and delivered over time-limited signed links.
- We use sealed sender delivery, so our servers do not learn who is messaging whom.
- Your message history is stored on your own device in an encrypted local database (SQLCipher). Keys are held in your device’s secure storage / keystore.
2.3 Push notifications (optional, off by default)
Push notifications are disabled by default. If you turn on “Google push (FCM)” in the app:
- your device registers with Google Firebase Cloud Messaging (FCM) and, on Apple devices, with Apple Push Notification service (APNs), and we store the resulting push token so we can wake your device when a message is waiting;
- this registration is made by your device directly to Google/Apple and reveals your device’s IP address to those providers (this step is not routed through Tor);
- push messages do not contain message content or sender identity. The rich notification you actually see is generated locally on your device after the message is decrypted.
If you leave push off, the app receives messages over its own encrypted connection while it is running and never contacts Google/Apple for push.
2.4 Connection / technical data
To deliver messages, our servers process the network connection your app makes. Because the app routes traffic through the Tor network by default, our servers generally see a Tor address rather than your device’s real IP address. We do not build advertising or tracking profiles from connection data.
3. What we do NOT collect
- Phone number or email address
- Real name or contact / address-book data
- Precise or coarse location
- Analytics, usage telemetry, or behavioral tracking
- Third-party crash / diagnostics reporting
- Advertising identifiers; we show no ads and sell no data
4. How we use information
We use the limited information above only to:
- create and operate your account and linked devices;
- route and deliver your encrypted messages and media between devices;
- wake your device for new messages if you have enabled push;
- keep the service secure and reliable (e.g. preventing abuse).
We do not sell or rent your information, and we do not use it for advertising or profiling.
5. How information is stored and protected
- End-to-end encryption protects message and media content; our servers never hold the keys.
- Sealed sender hides who is communicating with whom from our servers.
- On-device encryption (SQLCipher) protects your local message history.
- Tor by default minimizes what our servers learn about your network identity.
- Server infrastructure is hosted on Amazon Web Services in the United States.
6. Sharing and disclosure
We do not sell your data and we do not share it with third parties for their own purposes. Limited processing happens through infrastructure providers acting on our behalf:
- Amazon Web Services — hosting and encrypted storage of ciphertext.
- Google (FCM) and Apple (APNs) — only if you enable push notifications, and only to deliver content-free wake-up pushes.
Because your content is end-to-end encrypted and our servers do not hold the keys, we cannot produce the plaintext of your messages — including in response to a legal request. We may comply with valid legal process to the limited extent it concerns data we actually hold (such as account/username records).
7. Data retention
- Encrypted messages in transit: kept only until delivered, then removed; undelivered messages expire after a limited period.
- Account records (username, device public keys, push token if enabled): kept while your account exists.
- Account deletion: devices are revoked and server-side data is purged; the username is held 30 days before reuse.
- Local data on your device: removed when you delete the app’s data or uninstall the app.
8. Your rights and choices
- Delete your account and data at any time from inside the app (see Section 9).
- Turn push notifications on or off (off by default).
- Block other users so they can no longer message you.
- Report abusive content or users from within the app.
- App lock (PIN / biometric) to protect access on your device.
Depending on where you live, you may have additional rights (access, correction, erasure). Contact contact@nanb.us to exercise them. By design, we cannot access the content of your messages.
9. How to delete your account and your data
You can delete your account directly in the app:
- Open Settings → Account → Delete account, then confirm.
This revokes all linked devices and purges your server-side account data. Your username is reserved for 30 days before it can be reused, then released. Message history stored locally on your devices is removed when you delete the app’s data or uninstall the app.
If you can no longer access the app and want your account deleted, email contact@nanb.us with the username you want removed. A standalone page describing this process is available at https://www.nanb.us/terms-of-service/nanb-chat-deletion-policy.
10. Children’s privacy
NANb Chat is not directed to children. The app is intended for users aged 13 and older (or the minimum age of digital consent in your country, if higher). We do not knowingly collect information from children below that age.
11. International users
The app is operated from, and its servers are located in, the United States. If you use the app from outside the United States, the limited data described above is processed in the United States.
12. Changes to this policy
We may update this policy from time to time. When we do, we will revise the “Last updated” date above and post the new version at this URL.
13. Contact
Questions or requests about this policy or your data: contact@nanb.us.
NANb Chat — messages that only you can read.