Privacy, in plain English
Twonest is built so that the person running it cannot read what you send. Not as a policy, but because the keys are not on the server.
How it works
When you pair with your partner, your two devices establish a shared secret that never leaves them. Every message, photo and voice note is encrypted on the sending phone with that secret, and decrypted on the receiving phone.
The server in the middle stores ciphertext. It can see that a message was sent, to which paired account, and when — it has to, in order to deliver it — but not what it says.
What this makes impossible
Encryption is a trade, and it is only honest to name the cost:
- No message recovery. If both phones are lost or wiped, the messages are gone. There is no readable backup to restore from.
- No content moderation. We cannot review what you send, so abuse enforcement works at the account level instead.
- No server-side search. Your history is searchable on your device, not in our database.
- No readable legal disclosure. A request for message content can only be answered with ciphertext.
What is not encrypted
Being precise matters more than sounding impressive. The following are visible to the server because the service cannot function without them:
- your account identity (email, display name) and profile photo;
- message metadata — sender, recipient, timestamps, sizes;
- your presence "last seen" timestamp;
- the push notification registration identifier, so a notification can reach your device.
Encryption protects content. It does not hide the fact that two people are talking.
What we do not do
- No advertising, and no advertising SDK.
- No third-party analytics profiling.
- No selling or brokering of data.
- No contact-upload to find "friends" — pairing is explicit.
The rest of the detail
The Privacy Policy sets out every category of data, the legal basis for each, who processes it, and how to delete it.