Privacy Policy
Last updated: 22 November 2026
Short version: we collect as close to nothing as a working messenger allows. No email, no phone number, no real name, no profile picture, no bio, no IP address logs, no analytics, no trackers, no ads, no cookies other than the one that keeps you logged in. Your messages are encrypted on your device and we cannot read them.
1. What we store
| Data | Why | Can we read it? | How long |
|---|---|---|---|
| Your username | So friends can find you and so you can log in | Yes | Until you delete your account |
| A hash of a key derived from your password | To check your login | No — your actual password never reaches our server; we receive a derived key and hash it again (PBKDF2 in your browser, then scrypt on the server) | Until you delete your account |
| Your public encryption key and your encrypted private key | So others can send you encrypted messages, and so you can log in on another device | Public key: yes (it is public by design). Private key: no — it is locked with your password, which we never see | Until you delete your account |
| Your 2FA secret and hashed backup codes (only if you enable 2FA) | To check your Google Authenticator codes | Yes — the server must be able to verify codes | Until you disable 2FA or delete your account |
| Friend list and pending friend requests | So the app can show your friends | Yes (who is friends with whom) | Until removed / account deleted |
| Group memberships, which member owns a group, and the group key encrypted separately for each member | So groups work | Membership: yes. Group key and group name: no (encrypted) | Until you leave / the group is deleted |
| Messages | To deliver them to devices that are offline | No. Content is end-to-end encrypted. We can see the sender, the conversation it belongs to and its size. We store only the date it was sent (no time of day), which is needed for automatic deletion. The exact time you see in the chat is encrypted inside the message | Deleted automatically after 30 days (counted in whole days), or earlier when you delete it, remove the friend, delete the group or delete your account |
| Invite links | So invite links work | We store only a hash of the link token, who created it, how many uses are left and when it expires. The group key in a group link sits after the "#" and is never sent to us | Until it expires, is used up or is revoked |
| Login session | To keep you logged in | We store only a hash of your session token | 30 days, or until you log out |
2. What we do not collect
- No email address, phone number, real name, date of birth, profile picture, bio or "about me".
- No IP addresses in our database, and our software writes no logs. Note: the company that hosts this website may keep standard web-server access logs (for example IP address, time and the file requested) for a limited period under its own policy. Invite codes and group keys are placed after the "#" in links, so they never appear in those logs, and message contents are encrypted either way.
- No device fingerprinting, no user-agent storage, no location.
- No analytics, telemetry, crash reporters, ad networks, social widgets or third-party scripts. The app loads no external fonts or resources.
- No "last seen", online status, read receipts or typing indicators.
- No account creation date or login history.
- No exact message times — only the date is stored; the time of day is end-to-end encrypted.
3. Cookies and local storage
We set exactly one cookie, sid, which is strictly necessary to keep you logged in. It is HttpOnly and SameSite=Strict. Because it is strictly necessary there is no cookie banner. Your browser also keeps your private key in IndexedDB (in a form that cannot be exported) so you don't need to type your password on every reload; logging out wipes it. When you open an invite link before logging in, the link is kept in your browser's session storage until you log in.
4. Encryption
Direct messages are encrypted with a key derived from an ECDH (P-256) exchange between your key and your friend's key. Groups use a random 256-bit key that is encrypted separately for each member. All content uses AES-256-GCM. Encryption and decryption happen only in your browser. You can compare a safety code with a friend to make sure no one is impersonating them.
5. Sharing
We do not sell, rent or share data with anyone. We have no advertisers or data partners. If we receive a valid legal order, the most we could possibly hand over is what is listed in section 1 — and message contents are unreadable to us.
6. Your control
- Delete a message: hover your message → delete. It is removed from the server for everyone.
- Remove a friend: deletes your direct-message history with them for both of you.
- Delete your account: Settings → Delete account. Your account, keys, friendships, memberships, every message you sent and all your direct-message histories are permanently erased immediately. The database uses secure delete mode to overwrite removed data.
Because we hold no contact details, we cannot identify you outside the app, cannot contact you, and cannot recover your account. That is intentional.
7. Children
3ncrypt is not intended for children under 16. Since we collect no age or identity information we cannot verify age; by signing up you confirm you meet this requirement.
8. Changes
If this policy changes, the new version will be posted on this page with a new "last updated" date. We will never change it to start collecting personal data retroactively.
9. Contact
We deliberately don't run a contact form that would collect email addresses. If the operator of this instance provides a contact method, it will be listed here.