Privacy policy
This policy explains what the GuptChat app and the GuptChat server store, and why. It is written to be read in one sitting. If anything is unclear, ask from inside the app: Settings → Help & Support.
In short
- No phone number, no email. Your account is a 6-digit Gupt ID and a password.
- Encrypted on your phone. Messages, photos, voice notes, files and polls are locked on your phone; the server only passes on content it cannot open (new encryption in version 1.0.9; an independent security review is still pending).
- Metadata is visible to the server: who writes to whom, when, and how big messages and files are.
- No ads. We do not sell your data or share it with advertisers.
- This website sets no cookies and runs no analytics.
1. Your account
We store your name, Gupt ID, profile photo, "about" text, join date and privacy settings. Your password is stored only as a one-way hash, so it cannot be read back.
To enforce the limit of 4 accounts per phone we keep a keyed hash of your phone's Android ID, not the ID itself. If you create a backup phrase, the server keeps only a public key derived from it; the 12 words never leave your phone.
2. Messages and media
Messages are encrypted on your phone before they are sent, and the server stores them in that locked form so they can reach phones that are offline.
In updated chats (version 1.0.9 and later) each phone makes its own keys, and the server only passes on locked messages, photos, voice notes, files and polls that it cannot open. An independent security review of this new encryption is still pending, which is why we do not describe GuptChat as end-to-end encrypted.
Chats with someone on an old GuptChat still use the old encryption, which the server could undo, and photos and files in those chats are not encrypted. Ask them to update.
So that phones can pass keys to each other, the server stores each phone's public keys and keeps locked key envelopes for up to 30 days, until the phone they are for collects them.
The server still sees who writes to whom and when, the size of messages and files, and that a message is a poll vote (and for which poll). Reactions are not encrypted.
The server keeps up to the last 500 messages of a chat. Messages with an auto-delete timer are removed when it runs out. Secret-chat messages are deleted from the server as soon as they are delivered; a photo in a secret chat stays until the message's timer runs out, so the other phone can still load it.
Photos, videos, voice notes and files you send are stored on the server so the other person can download them; in updated chats they are locked on your phone first. Private channels are protected with a key that travels only in their invite link. Public channels are not encrypted.
3. Calls
Calls connect phone to phone and are encrypted in transit (DTLS-SRTP), with a security code both sides can compare. When a direct connection is not possible, the call is relayed through GuptChat's relay server, which forwards encrypted data it cannot listen to. Who called whom, when and for how long is saved in the chat as a call entry.
4. Statuses, location and links
Statuses are visible for 24 hours to people you share a chat with, according to your privacy settings, and you can see who viewed yours. Locations you share are sent as encrypted messages; their map previews are loaded from OpenStreetMap. Link previews are fetched by your phone directly from the website in the link.
5. Notifications
To deliver messages and calls while the app is closed, your phone's Firebase Cloud Messaging token is stored and notifications are sent through Google's FCM service. For updated chats these notifications carry no names and no readable text: your phone unlocks the message itself.
6. Security checks
GuptChat checks on your phone whether it is rooted or tampered with, and refuses to run if it is. When Google Play Integrity is enabled, the app sends Google's integrity token with its requests so the server can verify that it is talking to the genuine app.
7. Reports and logs
Reports and bug reports you send are kept for review. Server logs record technical events, such as connections, for troubleshooting and abuse prevention; IP addresses are used to limit repeated attempts.
8. This website
gupt.chat sets no cookies and runs no analytics or trackers. The server logs requests, including IP addresses, the way any web server does. The fonts on these pages are loaded from Google Fonts, so Google sees the request for them.
9. What we do not do
No ads. We do not sell your data, and we do not share it with advertisers.
10. Deleting your account
Settings → Account → Delete my account removes your profile, password, devices, push tokens, statuses and the channels you own, and removes you from groups. Messages you already sent stay in the other person's chat. A deleted account's Gupt ID is never given to anyone else. (If you switched to a VIP number, your previous number went back into the pool.)
11. Changes to this policy
When the app changes what it stores, this page changes with it. The date at the top tells you when it was last updated.
12. Contact
Questions or problems: in the app, Settings → Help & Support → Ask a question or Report a bug.