What our servers store
Transparency reports usually count requests. Ours starts a step earlier, with what the chat server and the shop hold, and what the chat server never receives. We built the system so the first list stays short.
The premise
Data that is never collected can't leak
A privacy policy is a promise, and it holds only as long as the people behind it keep it. Aphotic is built to need fewer promises: the messenger never records who you are, or when you signed up or were last online, so a copy of its database holds nothing of the kind. While the server runs, its memory also keeps a few notes under your ID that expire on their own. They are listed below, and Redis, the in-memory store that holds them, never writes them to disk.
Everything below can be checked against the rest of this site and against how the app behaves.
The full inventory
Everything the chat server stores
Everything on it falls into one of these two columns, and there is no third.
What it stores
- An ID derived from your keysA string your phone works out from its own public keys. Nothing connects it to a person, a phone number or a payment.
- Public keysThe keys other people use to encrypt messages to you. On their own they decrypt nothing.
- Waiting messages, encryptedScrambled blocks waiting to be collected, each at most 7 days old. If the server restarts and loses them, the sender's app sends most direct messages again, and each new copy can wait another 7 days. Direct messages have no sender written on them.
- Used-up license tokensProof that some valid license was redeemed at some point. The way they're signed makes it impossible to say which one.
- Arrival times of the messages still waitingA message waiting in the queue shows when it reached the server. The time it was sent is sealed inside it, together with the text. The arrival time goes when the message is picked up, or after 7 days.
- Community data and group invite linksFor each Community, a roster listing each member's ID and home relay, the Community's name as scrambled text, and a log of its key changes. The key changes are encrypted, but each one that admits a member carries that member's ID and public keys in the clear, with the time their phone prepared the join to within five minutes, and the log is kept as long as the Community exists. A Community that turns on saved history keeps its older messages as well. A group of up to 20 keeps its roster, name and roles on its members' phones only. For each invite link an admin makes, the server holds one row: a hash of the link's token, a hash of a secret kept by that admin, a padded blob the server cannot read, and an expiry rounded up to the hour. The row stays until the link is reset or revoked, that admin leaves the group, or the expiry passes. Nothing in the row that the server can read names a group or a person.
- Short-lived notes under your ID, in memory onlyWhile your app is in use, the server's memory notes that your ID has signed in (for up to 15 minutes, so it doesn't look the sign-in up on every request) and that it holds a license (until the end of the hour). It also keeps counters and markers that limit how often an ID can do certain things, such as join a Community, change its keys there or fetch posting tokens; the longest-lived of them lasts a day. Redis, which holds all of these notes, never writes them to disk, and each expires on its own.
- A count of missed messagesIf messages wait the full 7 days without being collected, the server deletes them and keeps a count of how many, so your app can tell you when it comes back. The count names no sender and carries no content. It lives in memory only and goes once your app has fetched it, or after 30 days.
- Our log of moderation stepsTo act on a report, we can disable a community, take an invite link down or delete a file. A disabled community is switched off: nobody can read or post in it, join it, invite anyone to it, or upload or open its files, and its invite links stop working. Members can still leave. Its encrypted messages, saved history, key-change log, roster and files are deleted on the same schedule as any other community's, and a report never keeps a message, a file or a membership on the server any longer. If we restore a community, only what hasn't expired by then comes back; we can also delete it at once. A group invite link we take down leaves the hash of its token behind for at least a year, so it can't be put back up. A log records each step and its time: the community, the file or a hash of the link, the report it answers, our reason, a note and counts, never a list of members. The log is kept with no end date.
What it never has
- A name, phone number or email addressNever asked for. There is no field anywhere to put one in.
- An IP addressTor ends the connection before it reaches our server, so the address never arrives and can't be written down.
- The sender of a direct or group messageSealed sender leaves it off the envelope, and group messages go out under a pseudonym separate from the one your direct messages use. A post or an attachment in a Community carries a proof that it comes from a current member, without saying which one. Fetching the day's posting tokens, changing a Community's keys and managing a Community (members, roles, settings, invite links) do show the server your ID. An invite link for a group of up to 20 is made and opened without it. While a message is on its way, the server can try to pair its send with its delivery by timing.
- Who sent a photo or voice note, or who it was forA stored file sits beside the hash of a download token and nothing else. The token travels inside the encrypted message, so the server learns neither who uploaded the file nor who may fetch it.
- What anyone saidScrambled data only. The keys that open it live on your phone and nowhere else.
- A record of when you signed up or were last onlineThe chat database has no columns for either, so there is nothing to look up. The in-memory notes in the other column expire on their own, and Redis never writes them to disk. The times the server does keep belong to messages, invite links and our own moderation steps, with one exception tied to a person: when someone joins a Community, the key change that admits them carries their ID and the time their phone prepared the join, to within five minutes, for as long as the Community exists.
The shop
The one database with money in it
The shop has an ordinary web address, because a shop has to be findable. An order holds the plan, the price in euros, the amount of crypto, the transaction ID of the payment, and an internal reference to the license it created. The key itself isn't in the order. Crypto checkout never asks for a name, an email address or a postal address, so the order has none of them. The invoice is built from that same row and carries no buyer identity either.
Orders are dated, because an invoice has to be: when it was placed, when it was paid, when the key went out. Those dates describe a purchase, and they are kept as long as tax law says. Nothing in the row, and nothing on the invoice, says who made it.
Three other kinds of record exist only if you create one. A message through the contact form keeps its text and a reply address if you give one. A withdrawal declaration keeps the orders or the last block of the license key you name, a name and an email address if you give them, a coin and address if you ask for a refund, our notes, and the transaction ID of any refund. It is deleted 3 full calendar years after the year it arrived, or 10 after the year of a refund.
A report you send us from the app or the website keeps your explanation, any messages you quote with their sender and time, where the content is (such as a community, an invite link's token or a user's ID), and a name or contact only if you add one. Those are erased 180 days after the report is decided; its category, the decision and its dates stay.
The link between an order and a chat identity is not in the database, and it cannot be rebuilt from what is, because of the way license tokens are signed. Somebody with complete read access to both databases still couldn't build it.
The record
Requests received so far
None. Zero is today's number, and this page is where it will change if it ever does.
All of our servers are our own and stand in data centres in the EU. The chat server, the payment node and this website are separate machines. The chat server also runs the license service, so the relay inventory above and the shop database sit on the same machine. The call relay that carries voice calls keeps no accounts and no logs; while a call runs, it knows two IP addresses and how much audio passes between them.
- requests for user data, ever
- 0
- identities on file that name a person
- 0
- longest one copy of a direct message waits in the queue
- 7 days
Check the claims yourself
The security page explains the mechanism behind every line on this one.