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

DataWhyCan we read it?How long
Your usernameSo friends can find you and so you can log inYesUntil you delete your account
A hash of a key derived from your passwordTo check your loginNo — 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 keySo others can send you encrypted messages, and so you can log in on another devicePublic key: yes (it is public by design). Private key: no — it is locked with your password, which we never seeUntil you delete your account
Your 2FA secret and hashed backup codes (only if you enable 2FA)To check your Google Authenticator codesYes — the server must be able to verify codesUntil you disable 2FA or delete your account
Friend list and pending friend requestsSo the app can show your friendsYes (who is friends with whom)Until removed / account deleted
Group memberships, which member owns a group, and the group key encrypted separately for each memberSo groups workMembership: yes. Group key and group name: no (encrypted)Until you leave / the group is deleted
MessagesTo deliver them to devices that are offlineNo. 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 messageDeleted 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 linksSo invite links workWe 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 usUntil it expires, is used up or is revoked
Login sessionTo keep you logged inWe store only a hash of your session token30 days, or until you log out

2. What we do not collect

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

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.

← Back to 3ncrypt · Terms of Service