We designed the Service so we see as little as possible.
Account data (you provide):
Display name, username
Optional avatar image, optional status text
End-to-end encrypted content:
Messages, attachments, and keys are encrypted on your device before reaching
our servers. We cannot read them and do not have access to your encryption keys.
Technical / metadata:
Public key bundle (so others can address messages to you)
Server-side timestamps of message relay (for delivery + rate-limiting)
Standard server logs (IP, user agent) kept only as long as needed to operate
the Service securely
Invites and requests:
“Request a key” submissions: the alias and contact info you type, and your
IP address (for spam protection)
Issued keys and which accounts they unlock
Safety reports:
If you report abuse, we store the reporter identity, reported identity, selected
reason, optional details, timestamp and IP address needed to review the report.
We do not collect: message content, contacts, location, analytics,
advertising data, or any third-party tracking data.
3. Lawful basis (GDPR Art. 6)
Service provision and authentication: Art. 6(1)(b) contract
Message content end-to-end encrypted on your device using authenticated symmetric encryption
Private keys stored locally on your device, never sent to us in plaintext
Account sign-in never sends your password: your device runs it through PBKDF2-SHA-256 and sends only a derived verifier, which the server compares in constant time. Your password and master key never leave your device
Your private keys are held on our servers only as a blob encrypted on your device with a key derived from your password and master key — we cannot read it, and cannot reset your password or master key for you
Digital signatures (ECDSA P-256) authenticate users’ key bundles and messages between devices — a separate mechanism from signing in
9. Cookies and similar technologies
The Service does not use tracking cookies or third-party analytics. It uses:
A service worker (offline support, faster loading)
Local browser storage (IndexedDB) for your encrypted keys and message history
These are strictly necessary for the Service to function and are not used for tracking.