AltNet Relay — Privacy Policy
Last updated: 19 October 2026
This policy explains what personal data AltNet Relay handles, why, how long we keep it, who else receives it, and what your rights are under the EU General Data Protection Regulation (GDPR).
1. Who is responsible for your data
AltNet Relay is published and run by PANMOX. PANMOX is not a company: it is the name under which a private individual publishes Relay. The law requires us to name the person responsible for your data (the controller), so here it is:
PANMOX, Prague, Czech Republic
Controller: Gabriel Wenzel, the private individual who runs PANMOX
Email: [email protected] (also for privacy questions and requests)
Postal address: sent on request to that email address.
We have not appointed a Data Protection Officer, because the law does not require one for a service like ours. Privacy questions sent to the address above are answered personally.
2. The short version
- We cannot read your messages or listen to your calls. Your computer encrypts them end to end before they leave it.
- We can see some things: your email address and @name, your internet (IP) address when your computer connects to our servers, reports (with any messages the reporter chose to attach), bans, and some technical details of how messages travel (see section 3).
- We don't show adverts, sell data, track you, or use analytics, cookies or web fonts.
- Your conversations, contacts and history are kept on your computer. Unless you turn it off, a locked copy of them is also kept on our server, so that you can sign in on another computer. It is locked with your password on your computer before it is sent, and we can't open it (see section 4a).
3. How AltNet works, and why that matters for your privacy
Relay doesn't send your messages through a central company server. They travel over AltNet, a peer-to-peer network made up of the computers of the people who use it, plus a few computers we run.
- A message for someone who is offline is stored on the network as encrypted pieces, on other users' computers and on ours, until the recipient collects it. Nobody holding a piece can read it.
- To route messages, the network uses small records that are not encrypted. A computer that stores one of these records can see the Relay IDs of the sender and the recipient, when the message was sent, and a counter of how many messages that sender has sent to that recipient. It cannot see the content. Relay IDs are long codes, but anyone who knows your @name can link it to your Relay ID.
- These records and pieces have no fixed expiry date. They stay on the computers that hold them until newer data pushes them out. Neither we nor anyone else can reliably delete them from every computer.
- The computers you connect to, including other users' computers and ours, see your IP address. This is true of any peer-to-peer software.
- Your computer also stores encrypted pieces and records for other people. That is part of how the network works. This storage is limited to 256 MB in total. Above that, the pieces used least recently are removed first.
4. What data we handle, why, on what legal basis, and for how long
The "legal basis" is the reason the GDPR allows us to process the data:
- Contract (Art. 6(1)(b)): we need the data to provide the service you signed up for.
- Legitimate interests (Art. 6(1)(f)): we need it for a fair purpose of ours or of other people, and that purpose outweighs the effect on you.
- Legal obligation (Art. 6(1)(c)): the law requires it.
| What | Where it is held | Why | Legal basis | How long |
|---|---|---|---|---|
| Email address, password (stored only as a bcrypt hash), "verified" flag, account creation date | AltNet account service (shared with AltNet Studio), on our server | To create your account, sign you in, reset your password and contact you about your account | Contract | Until you delete your account |
| Email verification and password-reset codes | Account service | To check that you control the email address | Contract | Until used or expired (minutes to hours) |
| Sign-in sessions (a random token, with dates) | Account service, and a copy on your computer | To keep you signed in | Contract | Until the session expires or you sign out |
| Relay account link: your Relay ID and public key, when it was linked, your @name, the date our Relay server first saw your account, the random ID of the computer your account is in use on (and when it started), and when your locked copy was last saved and its size | Relay server | To tie your Relay identity to a verified account, so that names are unique and bans work; to keep your account in use on one computer at a time | Contract; legitimate interests (preventing abuse) | Until you delete your account. Your @name then stays reserved, so it is never given to anyone else, but our server no longer links it to you. If you are banned, see "Bans" below |
| Your @name record (name → Relay ID, signed by us) | Public on the AltNet network | So that people can find you by name | Contract | Renewed while you use Relay; it lapses about 90 days after the last renewal |
| Your profile record (Relay ID and public keys; no name) | Public on the network | So that people can encrypt messages for you | Contract | Renewed while you use Relay |
| Routing records (sender and recipient Relay IDs, time, counter) and encrypted message pieces | Other users' computers and our nodes | To deliver messages, including to people who are offline | Contract | No fixed limit (see section 3) |
| IP address and connection times, seen by our nodes (the network entry point, the relay for computers behind home routers, the Relay server) | Our server: mostly in memory, plus technical logs | To connect you to the network and keep it working and secure | Legitimate interests (running and securing the network) | Technical logs are kept for a limited time and are deleted automatically as newer logs replace them |
| Call relay data: your IP address and port, when your call used our relay, and a short code made from a scrambled form of your email address | Logs of our call relay | To connect calls that can't go directly between computers, and to trace misuse of the relay | Legitimate interests | As for technical logs |
| Call content | Never stored. It travels encrypted, directly between computers or through our relay | — | — | — |
| Reports you make to AltNet: your email, the Relay ID and @name of the person you reported, your reason and the date. If you ticked the box, also the last 10 messages of that conversation, from both sides, in readable form (our server accepts at most 10) | Relay server | To handle the report, ban people who abuse others, handle appeals, and protect the network from false reports | Legitimate interests (the safety of users, including you); legal obligation where an authority requires it | While needed to handle the report, any appeal, and any repeated abuse by the same account. We check stored reports at least once a year and delete those no longer needed |
| Reports made about you (as above, seen from the other side) | Relay server | As above | Legitimate interests | As above |
| Reporter checks: how many accounts you have reported recently, and "strikes" when your reports led to bans that we overturned | Relay server | To stop people misusing reports to get others banned | Legitimate interests | As for reports |
| Bans: the ban, the reason, the date, and whether a person or the automatic system decided | Relay server, and a public ban list on the network (Relay ID, a fixed reason and the date: never free text) | To enforce bans across the network, and to handle appeals. A banned account also can't use our call relay | Legitimate interests | For as long as the ban lasts. When a ban is lifted, it is removed from the public list. The internal record is kept as for reports |
| Account and moderation log (account links, @names, which computer an account moved to, starting fresh, turning the locked copy off, reports, bans, unbans, and who did them) | Relay server | To show how decisions were made, and to answer appeals and authorities | Legitimate interests; legal obligation | As for reports |
| Locked copy of your account (see section 4a): your Relay identity keys and your saved conversations, contacts, groups and workspaces, locked with your password | Relay server | So that you can sign in on another computer and carry on | Contract | Until you turn the copy off, choose "Start fresh", or delete your account. Our server backups may contain it for a limited time after that |
| Update checks (version 1.0.6 and later): your IP address when the app asks our server whether a new version exists. The request contains nothing else about you: no account, no version number | Our server, briefly (we keep no log of these requests) | To tell you about new versions and keep the app secure | Legitimate interests (keeping the app up to date and secure) | Not stored |
| Update downloads (on Windows, if automatic updates are on; otherwise when you download an update yourself): your IP address and the file requested | GitHub, which hosts our releases | To deliver the update | Legitimate interests | Under GitHub's own policies (see section 6) |
| Wrong-password attempts: your email address and the times of wrong passwords given when starting fresh or deleting an account | Our server's memory only, never written to disk | To stop someone with a stolen sign-in session from guessing your password: after 5 wrong passwords within an hour, we stop checking passwords for that account for the rest of that hour | Legitimate interests (security; protecting your account) | Only the last hour counts. Cleared when the right password is given, and gone when the server restarts |
| Refused sign-in sessions: a scrambled (SHA-256) form of a sign-in token that the account service refused, never the token itself | Our server's memory only | To resist floods of made-up sign-in tokens | Legitimate interests (security) | Used for 1 minute; never written to disk |
| Emails you send us (appeals, requests) | Our mailbox at Zoho | To answer you | Legitimate interests; legal obligation (rights requests) | While needed for the matter, and up to 2 years after it is closed |
Typing indicators and "Delivered" notices go directly between the people in a conversation, and only between people who have accepted each other. They are encrypted, and we don't store them.
Desktop notifications show only who wrote to you, never what they wrote. An invitation is announced by who sent it (for example "@kate invited you to a group"), not by the group's name. Notifications show plain text only.
What we do NOT have
- The content of your messages or calls, except messages that someone chose to attach to a report.
- Your contact list or your conversation history in a form we can read. They are on your computer and, locked so that we can't open them, in your copy on our server.
- Your real name, phone number, location or payment details. We never ask for them.
Data on your own computer
Relay keeps your conversations, contacts, keys, settings and sign-in session in its data folder (on Windows: %APPDATA%\AltNetRelay). It also keeps a random ID for this computer, and the key that locks your copy (made from your password, so that the copy can be refreshed without asking you again). Only your computer account can read these files, but they are not encrypted. We never receive them in readable form. The folder is kept if you uninstall Relay. Deleting your account in the app erases it. You can also delete the folder yourself. A downloaded update waits in an updates folder inside it until it is installed, and is then deleted.
If someone else used Relay on the same computer: when you sign in there, either your account is brought from another computer, or (if it has no keys yet) new keys are made for it there and the app restarts once. Either way, the Relay files of the other account that were already on that computer are not deleted. They are moved to a folder called previous inside the app's data folder, and they stay there, unencrypted, until someone deletes them. They may include another person's conversations. If you share a computer, delete that folder, or delete the whole data folder when you stop using Relay there.
4a. Signing in on another computer: the locked copy
So that you can sign in on another computer and carry on with the same account, @name, contacts, conversations, groups and workspaces, Relay keeps a locked copy of your account on our server. (App settings, such as starting with your computer, are not part of the copy.)
- What it contains: your Relay identity keys and your saved conversations, contacts, groups and workspaces. These include messages other people sent you, and, if you own a workspace, reports you received there.
- How it is locked: your computer locks it before it is sent, with AES-256-GCM encryption under a key made from your password (PBKDF2-SHA256, 600,000 rounds). We store only the locked copy, at most 8 MB, in one file per account. We never store your password, and we can't open the copy.
- A weak password is the weak point. Someone who stole a copy could try to guess the password. Use a strong password that you don't use anywhere else.
- It refreshes itself about every 20 seconds while something has changed.
- One computer at a time. Each installation of Relay has a random ID. When you sign in on a new computer, your account moves there, and the previous computer signs itself out and tells you why.
- After a password reset, the copy still opens only with the password last used to sign in on the computer that has your account. Signing in there with the new password re-locks it. Until then, another computer may tell you the copy is locked with an older password.
- Start fresh: if there is no copy to bring (it was turned off, or it is locked with an older password), you can start fresh on the new computer. Your account and @name move to new keys made there, the old copy is deleted, and earlier conversations stay with the old keys and can't be opened on the new computer. You must enter your account password to do this. We check it with the account service, so that someone who got hold of your sign-in session can't take over your @name.
- On by default. You can turn it off under Account. Turning it off deletes the copy from our server, and your account then stays on that one computer.
- Accounts from before version 1.0.5 get a copy only after you type your password once under Account.
- Deleted when you turn it off, when you start fresh (the old copy), or when you delete your account. Our server backups may still contain it for a limited time; those backups hold it in the same locked form.
4b. Updates
Relay updates itself, so that security fixes reach you quickly.
- Checking. About every six hours, and shortly after the app starts, the app asks our server whether a newer version exists. This does not need your account and sends nothing about you except your IP address, as any internet request does. We don't keep a log of these requests. You can't turn the check off, but if you turn off automatic updates (below) it only tells you that a new version exists.
- Windows: automatic installation (on by default). The app downloads the new installer from GitHub in the background and installs it when you are not using the app (the window is closed to the tray and no call is going), when you press Restart to update, or the next time the app starts. It installs for your Windows user only, with no administrator prompt, keeps your chats and settings as they are, and reopens the app the way it was.
- Linux (and Mac, once released). The app only tells you that a new version is available, and opens its download page (on GitHub) when you ask. You install it yourself.
- You can turn it off under Account → Install updates automatically. The app then only tells you about new versions. The version you have is shown at the bottom of Account.
- How we make sure an update is genuine. Every release is signed with PANMOX's release key, which is built into the app. Before anything is installed, the app checks the signature, the size and the fingerprint of the file, and checks the file again right before it runs. A downloaded update that waits to be installed at the next start is checked against the signature again at that moment: the app keeps the signed notice itself, so a file placed in the app's data folder can't make it run anything. It refuses unsigned, altered or older versions, so GitHub, or someone intercepting your connection, can't give you a fake update. Whoever holds the release key could ship an update to every user, so we keep it offline.
- GitHub sees your IP address and which file you download when an update is fetched. We don't control GitHub's own logs.
5. Automated decisions: the automatic ban
When three different people report the same account within 30 days, the account is banned automatically. No person at PANMOX decides first. Some reports don't count towards this:
- reports from accounts that our Relay server first saw less than 72 hours ago;
- reports from people who have reported more than 5 different accounts in 30 days;
- reports from people who are banned themselves;
- reports from people whose reports led to two bans that we later overturned.
Why we do this: we cannot read conversations, and we can't watch everything as it happens. Several independent reports are the strongest signal we have that someone is harming others.
What it means for you: a ban stops you from using Relay. You have the right to have a person review the decision, to give your side and to contest it. Write to [email protected]. A person will answer within 14 days, and will lift the ban if it was wrong.
6. Who receives your data
We don't sell or rent data to anyone. The following receive data, either because they run part of the service for us or because the network works that way:
| Recipient | What they receive | Where |
|---|---|---|
| Oracle (Oracle Cloud Infrastructure), which hosts our server | Everything on our server (see section 4) | EU: Frankfurt, Germany |
| Zoho (Zoho Mail), which sends verification and password-reset codes and hosts our email | Your email address and the code; emails you send us | Zoho's EU data centre |
| GitHub (GitHub, Inc., a Microsoft company), where our installers and updates are hosted | Your IP address and the file requested, when an update is downloaded, or when you open the release page or download a new version yourself | Global (US company) |
| Cloudflare, which provides DNS for panmox.org and a backup address-finding service for calls, used only if our own server doesn't answer | DNS: no data about you. Backup service: your IP address, once per lookup | Global (US company) |
| Other AltNet users' computers | Encrypted message pieces, routing records (section 3) and your IP address | Anywhere in the world |
| The people you talk to | Your messages and @name, and your network address so that messages arrive faster. During a call, also your IP address | Anywhere |
| Workspace owners (Business mode only) | If a coworker reports you inside a workspace: the report and up to 10 of your recent messages. This goes directly to the owner. We can't read it, including when it is part of the owner's locked copy | Wherever the owner is |
| Authorities | Only when the law requires it (see section 9) | — |
Transfers outside the EU: Oracle, Zoho, Cloudflare and GitHub belong to groups based outside the EU. Where one of them may access or transfer data outside the EU, the transfer relies on the EU–US Data Privacy Framework (for certified US companies) or on the European Commission's Standard Contractual Clauses in that provider's data processing terms. Peer-to-peer traffic goes wherever the other users are. That is part of using a worldwide peer-to-peer network, and we don't control it.
7. Your rights
You have the right to:
- access the data we hold about you and get a copy (Art. 15). Your locked copy can be handed over only in its locked form;
- have it corrected (Art. 16);
- have it deleted (Art. 17);
- limit how we use it (Art. 18);
- take it with you in a machine-readable form (Art. 20);
- object to processing based on legitimate interests (Art. 21). We will stop unless we have compelling reasons, for example an ongoing abuse case;
- not be subject to a decision based solely on automated processing that significantly affects you, or to have a person review it (Art. 22, see section 5).
Deleting your account: in the app (version 1.0.4 or later), go to Account → Delete account. We email you a code, then ask for your password and your @name, then ask whether you are sure.
- What is deleted:
- your AltNet account (email address, password hash and sign-in sessions), which is also your AltNet Studio sign-in;
- our Relay server's record of your account and its link to your Relay identity;
- your locked copy (see section 4a);
- your email address on any reports you made (it is replaced with an anonymous tag);
- everything Relay stored on your computer.
- What stays:
- your @name stays reserved, so that nobody can take it and receive messages meant for you. Our server no longer links it to you, and its public record on the network lapses within about 90 days;
- reports made about your account;
- our moderation log, which records past actions (including, in older entries, your email address) and is kept under the same rule as reports in section 4;
- encrypted pieces and routing records on other people's computers (see section 3).
How to use your other rights, or to delete your account without the app: write to [email protected] from your account's email address. We answer within one month, free of charge. If we can't tell that the request comes from you, we may ask you to confirm it from your account email.
Limits you should know about:
- We cannot delete encrypted pieces or routing records held on other users' computers, or messages that people have already received.
- A banned account can't be deleted from the app: write to us instead. We then delete the account, but keep a minimal record (your email address and the ban) for as long as the ban lasts, so that the same person can't simply sign up again.
- We may keep a report and its evidence while an appeal, a legal claim or an authority's request about it is open.
Complaints: you can complain to the Czech data protection authority, the Úřad pro ochranu osobních údajů (ÚOOÚ), at www.uoou.gov.cz. You can also complain to the data protection authority in the EU country where you live or work. We would be grateful if you contacted us first.
8. Do you have to give us data?
You need an email address to create an account. Without one, you can't use Relay. Everything else is optional: an @name, reports, and calls through our relay.
9. Requests from authorities
We give data to authorities only when the law requires it and the request is valid, and we give only what the request covers. We cannot hand over message content, because we don't have it in readable form: we hold only your locked copy, which we can't open. We refuse requests that are not lawful. Unless the law forbids it, we tell the person concerned.
10. Security
- Messages and calls are encrypted end to end.
- Passwords are stored only as bcrypt hashes.
- Your locked copy is encrypted on your computer with a key made from your password. Only the computer your account is in use on can replace it.
- Updates are signed, and the app checks the signature again right before installing them, including an update that was downloaded earlier (see section 4b).
- Moving your account and @name to new keys ("Start fresh") needs your account password, not just a sign-in session.
- Our servers and the network software limit connection floods: at most 128 connections that haven't finished connecting at once, at most 8 direct connections from one internet address, memory for incoming data is taken only as the data arrives, and a message that has started must arrive within 60 seconds. These limits keep Relay available; they don't use any information about you beyond the IP address of the connection.
- After 5 wrong passwords within an hour for one account, the server stops checking that account's password for the rest of the hour. Sign-in checks with the account service are rationed, and refused sign-in tokens are remembered (only in a scrambled form) for 1 minute.
- On your computer, the app's window runs only the app's own code, notifications show plain text only, and invitations from strangers are limited (see the Terms, section 4).
- Our Relay server runs in a restricted environment: it can write only to its own folder, can't see the home folders of users of the machine, and has no access to devices or the operating system's kernel settings.
- Our servers are reached over HTTPS. Only signed-in accounts that are not banned can use the call relay.
- Only the operator has access to our server.
- When we fix a security problem, we say so in the release notes, and Windows apps update themselves (see section 4b).
No system is perfectly secure. If a breach puts your rights at risk, we will tell you and the authority, as the law requires.
11. Age
You must be 16 or older to use Relay. If we learn that an account belongs to someone younger, we will close it and delete its data. Parents who believe their child has an account can write to us.
12. AltNet Studio
Your AltNet account is shared with AltNet Studio. Studio has its own terms and privacy policy, including its own age rule. This policy covers Relay.
13. Changes to this policy
When something important changes, we will publish the new version on panmox.org before the change applies. The date at the top shows the current version.