Privacy Policy

1. Data we do NOT collect

Creating an account and using Morok requires no personal data whatsoever:

• Phone number — never requested, never stored
• Email — never requested
• Name, surname, date of birth — never requested
• Access to your phone contacts — never requested
• Location — never collected
• Advertising identifiers, trackers, behavioural analytics — none

2. What technically exists on the server

To deliver messages, the server temporarily handles a minimum of technical data:

• Encrypted messages — the server sees nothing but meaningless bytes. Only the recipient can decrypt them. Once delivered and read, they are erased from the server.
• Account public key — needed to deliver messages to you. It is not linked to any personal data.
• Username (if you chose one) — a public handle others can find you by. Anonymous accounts may have none at all.
• Connection metadata (IP) — processed briefly to route traffic and protect against abuse; not retained in logs for any length of time.
• Recipient and delivery — the server sees which account a message is for and when it was delivered. Who sent it is encrypted inside the message. To hide your IP address from the server too, use Morok's .onion address over Tor or run your own relay.
• Push token (only if you enable notifications) — a device identifier issued by Google or Apple, without which notifications cannot be delivered.

3. End-to-end encryption

Every message is encrypted on your device before it is sent (Ed25519/X25519, XChaCha20-Poly1305). Keys never leave your device in readable form. The server has no technical means of reading the content — not even on demand, because it holds no keys.

4. Your account is your 24 words

Instead of a login and password, Morok uses a 24-word secret phrase generated on your device. Only you hold it. We keep no copy and cannot restore access if you lose it — that is the price of real privacy.

5. Disappearing messages

Messages have a lifespan and are erased automatically on both sides, and on the server, once it expires. The server keeps no conversation history.

6. Push notifications

If you enable push notifications, delivery goes through Google (FCM) on Android or Apple (APNs) on iOS. Only a generic text is passed, never the message content — the messages themselves stay encrypted. For this the server keeps your device's push token, issued by Google or Apple. If you would rather not involve their services, turn notifications off.

7. @morok.email mail

Mail between @morok.email addresses is end-to-end encrypted on the sender's device — the server receives an encrypted container it cannot read. Mail from outside (Gmail, Outlook and so on) arrives over ordinary SMTP, so the server sees its content at the moment it is received and then immediately encrypts it to the recipient's key. Outgoing mail to other providers travels over SMTP with TLS; there is no end-to-end encryption between different mail systems. To deliver mail, the server sees addresses, times and SMTP service data. Your mail archive lives on your device, and the server removes each message from its queue once delivered.

8. Local data on your device

Contacts, local nicknames, your block list and settings are stored on your device only and are never sent to the server.

9. Sharing with third parties

We do not sell, share or trade your data with advertisers, data brokers or any third party. A business model built on user data simply does not exist at Morok.

10. Children

Morok is not intended for anyone under 13 and does not knowingly collect their data.

11. Changes to this policy

We may update this policy. Material changes will be reflected on this page along with a new update date.

12. Contact

Privacy questions: answer@morok.email.