Privacy
We can't read your messages.
Here's everything else.
Zekoro is end-to-end encrypted, so the content of what you send is never readable by us. It still has to store some things to work. This page lists all of them, plainly, including the parts that aren't flattering.
Last updated 26 September 2026
Content stays yours
Messages, images, calls and voice channels are encrypted on your device. We hold ciphertext we can't open.
No ads, no tracking
No analytics, no trackers, no third-party scripts, no selling or sharing data with anyone for anything.
Your password stays home
Your browser only sends a key derived from it. Your private key and recovery code never reach us unencrypted.
Metadata is visible
We can see who talks to whom, when, and how much. We can't see what was said.
Who runs Zekoro
Zekoro is run by one person, Federico, from Italy, who is the data controller for everything on this page. Write to [email protected] about anything here, including if you can't get into your account. Inside the app you can also message @fede.
What we store
Everything below lives in one database on our server. The right-hand column says whether we can read it.
What we can never see
- What your messages say, in DMs or servers
- Images you send
- Call and voice channel audio or video
- Your password
- Your private key or recovery code
What we can see
- Who you message and who's in which server
- When messages are sent and read, and roughly how big they are
- Whether you're online, and typing indicators while they're being sent
- Who is in a voice channel
- IP addresses in the places listed below
Who else touches your data
Cloudflare
Sits in front of the site. It handles the HTTPS connection, so it sees your IP address and the same traffic our server sees: who, when, and encrypted blobs. It can't read your messages.
Brevo
Sends our emails. If you add an email address, Brevo gets that address and the code inside each email we send you. Nothing else.
Google STUN
When a call starts, your browser asks Google's public STUN server for your public address so the call can connect directly. Google sees your IP. Turn on Hide my IP address in calls in Settings to skip this and use only our relay.
The other person in a call
Direct calls show both sides each other's IP address. The same setting routes your side through our relay so they only see the relay's address.
Why we process it
Almost everything here is needed to run the service you signed up for: your account, delivering messages, servers, calls. Under the GDPR that's performance of a contract (Art. 6(1)(b)). Rate limits, logs and abuse handling keep the service secure, which is our legitimate interest (Art. 6(1)(f)). Your email is only used for sign-in codes and password resets, never for marketing.
Where it lives, and who helps
netcup GmbH
Hosts our server in Nuremberg, Germany. The database, encrypted images and logs are all there.
Cloudflare, Inc.
Network, HTTPS and protection in front of the site. It handles traffic worldwide, so connection data can pass through servers outside the EU.
Brevo (Sendinblue SAS)
A French company that sends our emails, only if you add an email address.
Its public STUN server is asked for your public address when a call starts, unless you've turned on Hide my IP address in calls.
How long we keep things
Logs
Our web server keeps a standard access log (the address Cloudflare connected from, the page requested, the browser type) for 14 days, then deletes it. It only sees Cloudflare's addresses, not yours. The call relay keeps no logs. Cloudflare keeps its own logs under its own policy. We don't run analytics on any of it.
On your device
One cookie: your login session, marked HttpOnly and Secure. Your browser storage also holds your unlocked key while a tab is open (or longer if you turn on Stay unlocked on this device), the keys you've pinned for safety numbers, and small preferences like your theme and collapsed categories. None of it is used for tracking.
Admins
A few accounts are admins. They can see the list of accounts, ban and delete accounts, and open a read-only database viewer where every secret (password hashes, tokens, encrypted keys, recovery copies) is hidden and message content shows only as a size. Only the site owner can see email addresses. No admin can read messages, because nobody can.
Your rights
- See and take your data: Settings, Your data, Download my data gives you a file with everything we store about you.
- Fix it: edit your profile and email in Settings anytime.
- Delete it: Settings, Your data, Delete my account removes your account and everything attached to it (profile, keys, contacts, messages, passkeys, servers you own) right away.
- Object or ask for limits: write to [email protected]. Same address if you're locked out and want your account deleted.
- Complain: you can go to Italy's data protection authority, the Garante per la protezione dei dati personali, or the one where you live.
Two things to know. Clear chat only hides a conversation for you and leaves the other person's copy alone. And if you forget your password without a recovery code or a passkey that can unlock, your old messages can't be recovered by anyone, including us.
Password resets
If you have a verified email, the reset code goes there. If you don't, it's delivered as an encrypted message to @fede, who passes it to you directly. Adding an email takes @fede out of that loop.
Changes and questions
When something here changes, it's written up in changes.txt. The technical side is in structure.txt and qna.txt. Questions go to @fede in the app.