Privacy Policy
Last updated: 18.11.2026
English translation provided for convenience. In case of any discrepancy, the German version prevails (switch to “DE” above to read it).
1. Controller
The controller responsible for data processing within the meaning of the General Data Protection Regulation (GDPR) is:
West German Encrypted Hosting – Inhaber Alessandro Lindner
c/o Smarvo 251, Südstraße 31, 47475 Kamp-Lintfort
Email: aphotice2ee@proton.me
2. Overview and data minimisation
Aphotic consists of this website with its store, a licensing service, the messenger’s chat server (relay) and a call relay for voice calls. We operate all of our servers in data centres in the European Union. You need no user account to buy with Monero or Bitcoin, and we do not ask for a name, email address, postal address or phone number. The app does not read your address book. We use no analytics, tracking or advertising services.
The app encrypts message content end to end on your device; we cannot read it. The following sections describe which data is nevertheless created, where it is held and when it is deleted.
3. Website
3.1 Access routes and IP addresses
- Over Tor (.onion): by virtue of the Tor protocol, your IP address does not become known to us.
- Over the public internet (https): when you retrieve pages or the app file, our web server processes your IP address, because no connection can be established without it. The processing lasts only as long as the connection. The web server writes neither an access log nor an error log of individual requests and does not store the IP address. Its other operational messages rotate across three files of 10 MB each.
The web server forwards requests to the store, the contact form, the report form and the operator portal to our licensing service over Tor. Before doing so it removes every header that can carry your IP address (X-Forwarded-For, X-Forwarded-Host, X-Forwarded-Proto, X-Real-IP, Forwarded, True-Client-IP), the browser identifier (User-Agent), the language setting (Accept-Language) and the previously visited page (Referer). The licensing service receives only the request itself: path, body and host name. The website loads no content from third-party servers.
3.2 No cookies; browser storage
The website sets no cookies. It places only the following entries in your browser’s storage.
In local storage (localStorage), until you clear it in your browser:
aphotic_lang: your language choice, only when you switch the language explicitly;aphotic_notice_dismissed: that you closed the privacy notice;aphotic_tor_notice_dismissed: that you closed the Tor notice.
In session storage (sessionStorage), which is cleared when you close the tab:
order_<order ID>: the access code of your order;bulk_orders: the order IDs of a bulk order;withdrawal_<receipt number>: the code of your withdrawal declaration, so the status check works in this tab without typing it again;operator_key: your operator license key, in the operator portal only.
These entries are strictly necessary to provide the service you requested (§ 25 (2) no. 2 TDDDG).
3.3 Order ID in the address bar
During checkout the order ID appears in the address of the checkout page, so it can remain in your browser history. A recovery link also contains the access code. Anyone who has that link can retrieve your license key for as long as the access code is stored (section 10). You manage your browser history yourself.
3.4 Contact form
If you send us a message through the contact form (/contact, over either access route), we store your message (at most 4,000 characters) and, if you enter one, a reply address in the licensing service’s database. We do not store your IP address or the time. We read the message in our admin area and delete it once your request has been dealt with. There is no automatic deletion period.
3.5 Contact by email
If you write to aphotice2ee@proton.me, our email provider Proton AG (Switzerland) processes your message together with your sender address.
3.6 Operator portal
Relay operators sign in to the operator portal (/operator) with their operator license key. For each relay we store the onion address, the display name, the visibility (listed publicly or findable by search only), whether the relay accepts messages from other relays, the associated operator license, and the time it was created and last changed. We publish the onion address and display name in the signed relay directory.
4. Store and license management
The following data is held in our licensing service’s database.
- Orders: order ID, selected plan, payment method, amount in EUR, amount in cryptocurrency and the exchange rate used, the payment address generated for the order, the wallet software’s internal payment identifier, the transaction ID (txid) of the payment, the amount received, the number of blockchain confirmations, the status, the times the order was created, expired, paid and delivered, the access code, a reference to the license created, and your consent to the early start of performance with the language of the page and the version of the terms and the withdrawal policy you had before you.
- Withdrawal declarations: if you withdraw through the withdrawal function (/store/vertrag-widerrufen/), we store the receipt number, the time of receipt, the language, your name and an email address for the copy (both only if you give them), the order IDs you name, only the last block of a license key, a reference to the order and license and whether the entry could be matched to your order. If you give them, we also store the cryptocurrency and the receiving address for the refund; further the processing status, our notes, txid, amount and time of a refund, a checksum of the declaration and every later change with old and new value. Of your code we store only a hash. We do not store your IP address or browser data. We send an email copy from our mailbox at Proton AG (section 3.5).
- Reports: if you report illegal content or a breach of our terms in the app or through the website’s report form (/report/), we store the category, your explanation, the details of where the content is (such as relay, community, message or attachment ID, the token of an invite link without its key, or the user ID and home relay of a reported contact), quotes you include with sender ID, display name and send time where present, your name and a contact address (both only if you give them), the time of receipt, our processing steps with their times and notes, and our decision. Of the code you use to check the status of your report we store only a hash. We do not store your IP address, browser data or user ID; the app sends reports over a separate Tor connection without your user ID. Section 5.10 describes what we do on the chat server in response to a report.
- Payment events: created, payment seen in the mempool, partial payment (amount received and amount expected), failed (with reason), license generated, expired; each with a timestamp.
- Licenses: the license key (stored in readable form so you can retrieve it again, and additionally as a hash), term, the times it was created, activated and expires, number of devices, license type (user or relay operator) and, where applicable, a reference to the license it was merged into.
- Device activations: on activation the app sends a device identifier (“device_id”). The app generates it from 16 random bytes; it has no relation to your device’s hardware. We store the device_id with the time of activation and, when licenses are merged, the device_id with the time. The identifier is used to enforce the agreed number of devices per license. The same app installation always uses the same device_id, so licenses activated from the same installation can be linked to one another within the licensing database.
- Token issuance: how many anonymous tokens a license received per hour.
- Change log: changes we make to a license in the admin area, with old and new values; for a removed device, the first 8 characters of its device_id. At most 200 entries per license.
- Wallet label: the wallet software labels each receiving address
order_<order ID>. - Invoices: we generate them from the order each time they are retrieved (seller, order ID, plan, amounts, exchange rate, payment method, receiving address, txid, confirmations, dates). They contain no information about your person.
- Logs: the licensing service’s logs contain no IP addresses, license keys or device identifiers, but they do contain order and license IDs with timestamps (such as “license delivered”, “activated”, “tokens issued”), the receipt number of each withdrawal received with the number of contracts it names, and the priority and category of each report received.
With the order ID and access code you can retrieve your license key, license status, invoice and contract confirmation through the website until the access code is deleted (section 10).
The chat server receives neither license keys nor device identifiers. There the app proves its entitlement with blind-signed tokens; the licensing service cannot tell which token it signed. Whoever operates both services could, however, compare the times at which tokens are issued and redeemed.
5. Messenger
5.1 User ID and identity
The app generates your keys on your device. Your user ID is derived from your public keys (a UUID computed from a SHA-256 hash) and is therefore the same on every relay. It is pseudonymous and linked to no person, phone number or email address. The server stores for your identity:
- user ID, public identity key, public signing key, public sealed sender key with its signature, and the ratchet version in use;
- a SHA-256 hash of your access token;
- your public prekeys, including ones no longer in use.
The server stores no time of registration or of last activity; the database has no column for either.
5.2 Messages and attachments
- Direct messages wait in encrypted form in a queue until the recipient’s device collects them, for at most 7 days. An hourly sweep removes expired messages.
- For each user the server counts expired messages that were never collected and keeps that count for 30 days, so the app can show how many messages expired.
- Attachments are stored as encrypted files. For an attachment from a direct or group chat the server stores neither the sender nor the recipients, only a hash of the download token that travels encrypted inside the message; such attachments are uploaded and fetched without a user ID. For an attachment from a community it stores only the community. The server deletes files and metadata after 7 days (hourly sweep), even when an attachment has been reported (section 5.10).
The server cannot read content in any case.
5.3 Sealed sender and its limits
The app sends direct and group messages with sealed sender: the envelope names no sender, and group messages go out under a pseudonym separate from the one direct messages use. The server does see your user ID
- for messages in communities;
- when you manage a community: creating, joining or leaving it, admitting or removing members, or changing roles, settings or invite links;
- when attachments are uploaded to or fetched from a community (only the community is stored with them, not the user ID).
When you create or manage a group, the changes go to its members inside the encrypted messages; the server does not see your user ID. The app also creates and opens a group’s invite links without your user ID (section 5.4).
In addition, the server can infer from the timing of sending and delivery that two users are in contact with each other, and sometimes which member of a group sent a message.
5.4 Groups and communities
For communities the server stores:
- community ID, the founder’s user ID, encrypted name and encrypted description, permissions, invite token with expiry and usage limit;
- the members’ user IDs with role, status and capabilities, and the address of each member’s home relay;
- MLS handshake material (KeyPackages, Welcome messages, tree snapshots) until it is used or superseded.
Community messages are held in a shared stream and deleted after 7 days. The founder of a community can switch on saved history: an encrypted archive of up to the newest 100,000 records, kept until the founder switches it off or the community is deleted. The same applies to a community we have suspended after a report (section 5.10).
For each community the server keeps a handshake log: every encrypted MLS commit message with the time the server received it. These messages contain user IDs and public keys of members. The log is kept for as long as the community exists.
For groups the server stores no member list, roles, name or settings; these are held only on the members’ devices. It handles group messages and their attachments as described in section 5.2. For each invite link to a group, the home relay of the administrator who created it holds one entry: a hash of the link token, a hash of a secret code with which only that administrator’s device can change or delete the entry, an encrypted data block of uniform size that the server cannot read, and the expiry time, rounded up to the next full hour. The server cannot tell from the entry which group or person it concerns; it is created and fetched without a user ID. It is deleted as soon as the administrator’s app removes it (for example because the link was revoked or replaced) or shortly after its expiry time is reached.
5.5 Short-lived technical data
The server holds the following in memory only, never written to disk:
- a session cache, 15 minutes;
- proof of your license entitlement, until the end of the current hour;
- rate-limit counters, at most 1 hour;
- during a device transfer through the server, your encrypted vault, 10 minutes.
IP addresses do not exist on the chat server, because it can only be reached over Tor. It keeps no log of individual requests. Some log lines contain internal identifiers (message, upload or group ID). During calls our call relay processes your IP address (section 5.9).
5.6 Delete account
Under “Settings” → “Delete account” in the app, the server immediately deletes your identity, your prekeys, your memberships of communities, the waiting messages addressed to you, the count of expired messages and the proof of your license entitlement. The app also tries to delete your guest identities on other relays (section 5.7) and the entries of the invite links you created for groups (section 5.4), and shows you anything it could not delete.
Communities you founded are dissolved in the process, including their saved history and handshake log, even if we have suspended them after a report. Their members lose these communities. Groups are held only on their members’ devices; the server can neither dissolve them nor remove you from them. Leave a group first if you want its members to know.
The following remain until their respective period expires:
- messages you have already sent that are still waiting in other users’ queues (at most 7 days);
- attachments and their metadata (at most 7 days);
- your records in community streams (at most 7 days);
- entries of group invite links whose relay the app could not reach (at most 365 days and 1 hour);
- your records in the saved history and handshake logs of communities founded by someone else (until the history is switched off or the community is deleted);
- rate-limit counters (at most 1 hour).
Order and license data in the licensing service (section 4) is not affected.
5.7 Relays run by other operators
In the app you choose a home relay: our central relay or one run by another operator. If your home relay is run by another operator, the data listed in sections 5.1 to 5.5 is held by that operator. The app delivers messages and attachments for a contact with a different home relay to that contact’s relay. If you join a community hosted on another relay, the app registers a guest identity there with the same user ID, your public keys, a token hash and a few prekeys. The app fetches the entry of a group invite link held on another relay there without signing in.
The operator of such a relay processes this data as an independent controller. Conversely, our central relay stores guest identities of users of other relays. Relays run by other operators retrieve no personal data from us. The app loads the message of the day, app updates and the relay directory from our central server over Tor without identifying you.
5.8 Data on your device
Contacts, message history and private keys are held in an encrypted vault on your device. They leave the device only if you export an encrypted backup file, transfer your data directly to another device, or use the “chats only” transfer through the server. In that case the server relays your encrypted vault and holds it for at most 10 minutes.
5.9 Calls
The audio of calls does not run over Tor, because Tor does not carry UDP traffic. Before the app places or accepts a call, it asks you every time whether you allow this. Both devices then connect over the public internet to our call relay, which forwards the encrypted audio between them; your conversation partner sees only the call relay’s address. For the duration of the call, the call relay processes the IP addresses of both devices, the start and end of the connection and the amount of data transferred. It writes no log and does not store this data. It cannot decrypt the conversation itself.
The chat server issues the access credentials for the call relay without your user ID. They consist of an expiry time and a random value and are valid for 10 minutes, so the call relay does not learn who is calling. The app sends the call setup and its keys as encrypted messages over Tor.
5.10 Measures taken after reports
In response to a report (section 4) we can suspend a community on our relay, revoke an invite link or delete an attachment. The content stays encrypted; we cannot read it.
The server no longer serves a suspended community: it stops delivering its messages, attachments and member list, accepts no new messages or attachments, and allows no joins or invitations; its invite links are revoked. Members can still leave, and the founder can dissolve the community. The server deletes its data by the same rules as for any other community: stream, saved history, handshake log with the MLS handshake material, memberships and attachments (sections 5.2, 5.4, 5.6 and 10). A report or a suspension extends none of these periods. Data that only the community’s next key change would otherwise remove is deleted when the community is suspended: pending join requests, the handshake material of joins not yet completed, and the memberships of members who have left. A member who leaves during the suspension has their membership deleted at once. If we lift the suspension, only what has not been deleted by then remains. We can also delete a suspended community at once.
For a group invite link we have revoked, a block entry with the hash of the link token remains stored for one year from the revocation, so the link cannot be created again.
We record each of these measures in a log: the kind of measure and its time, the community, the attachment or a hash of the link token concerned, the reason, the reference to the report, a note, and counts such as the number of members. The log contains no user IDs. There is no automatic deletion period.
6. Payment processing
You pay in Monero or Bitcoin to an address generated for your order. We check Bitcoin payments on our own full node and Monero payments with our own wallet. No payment service provider is involved. Bitcoin transactions are permanently visible on the public blockchain; anyone who knows the payment address or txid can trace the transaction there.
To convert prices, our server fetches exchange rates from CoinGecko, Kraken and CoinPaprika over Tor. It sends only the names of the cryptocurrencies and no personal data.
7. App
The app contains no analytics and no crash reporting, uses no push notifications (it raises notifications on the device), and reads neither an advertising ID nor your address book.
8. Recipients and processors
- Data-centre operator in the EU: the chat server and licensing service, the payment node, the web server and the call relay are virtual servers that we operate in data centres of a hosting provider in the European Union. The provider is our processor under Art. 28 GDPR.
- Proton AG, Switzerland: our email provider (section 3.5). Switzerland is covered by an adequacy decision of the European Commission (Art. 45 GDPR).
- 1984 Hosting, Iceland (EEA): operates the name servers for the domain aphotic.me.
- Let’s Encrypt: issues the website’s TLS certificates. We hold the account for this without an email address; Let’s Encrypt receives no visitor data.
- Exchange-rate sources (CoinGecko, Kraken, CoinPaprika) receive no personal data (section 6).
- Blockchains: Bitcoin transactions are public (section 6).
- Operators of other relays process the data your app sends to their relay as independent controllers (section 5.7). Where such a relay is located is decided by its operator. If a report (section 4) concerns such a relay, we forward it to its operator.
- Law enforcement authorities: details from a report that points to a criminal offence threatening the life or safety of persons (Art. 18 of Regulation (EU) 2022/2065, Digital Services Act, DSA).
We use no analytics or advertising service providers. The only transfer of personal data we make to a country outside the EEA is to Proton AG in Switzerland.
9. Legal bases
- Art. 6 (1) (b) GDPR (contract): order, payment, license, device activations, retrieval with the access code, invoice and wallet label; the operator portal and relay directory; the messenger with identity, messages, attachments, groups, communities, saved history, handshake log, guest identities, device transfer, calls and the short-lived data in section 5.5; contact requests concerning a contract or its conclusion.
- Art. 6 (1) (c) GDPR (legal obligation): retention of orders that received a payment under § 147 AO and § 14b UStG; receiving, acknowledging and handling withdrawal declarations (§§ 356a, 357 BGB), and Art. 6 (1) (b) GDPR as well where a declaration concerns the contract; receiving and handling reports, the measures taken on them and notifications to authorities (Arts. 16 to 18 DSA).
- Art. 6 (1) (f) GDPR (legitimate interest): transient processing of the IP address and the web server’s operational messages (secure and functioning operation); contact form and email (answering your request); token-issuance counts and rate limiting (protection against abuse); change log and the logs of the licensing service and chat server (traceability and operational security); retention of licenses after expiry until the limitation period ends (establishment, exercise or defence of legal claims); retention of decided reports and the log of our measures (keeping the service free of illegal content; establishment, exercise or defence of legal claims).
- § 25 (2) no. 2 TDDDG: entries in your browser’s storage (section 3.2).
10. Storage period
Website
- IP address when accessed over the public internet: not stored, processed only for the duration of the connection.
- Web server operational messages: rotate across three files of 10 MB each.
- localStorage entries: until you clear them in your browser. sessionStorage entries: until you close the tab.
- Contact form: until your request has been dealt with; there is no automatic deletion period.
- Emails: until your request has been dealt with.
- Relay entries in the operator portal: until the operator or we delete the entry.
Store and license management
- Access code and payment events: deleted 90 days after the order was created, once it has been delivered, has expired or has failed. After that, retrieval through the website is no longer possible.
- Orders that received no payment (expired or failed, no amount received, no txid, no license): deleted entirely 90 days after creation.
- Orders that received a payment: they keep the payment address, payment identifier and txid as tax records and are deleted once 10 full calendar years have passed since the end of the year of payment (§ 147 (4) AO).
- Licenses: deleted once 3 full calendar years have passed since the end of the year in which they expired (§§ 195, 199 BGB). Device activations, merge records, token-issuance counts and the change log are deleted with them, and a retained order loses its reference to the license. Licenses that were never activated have no expiry date yet and remain stored.
- Token-issuance counts: 7 days.
- Change log: at most 200 entries per license, deleted with the license.
- Invoices: not stored separately; generated from the order each time they are retrieved.
- Withdrawal declarations without a refund: deleted once 3 full calendar years have passed since the end of the year of receipt (§§ 195, 199 BGB). With a refund: deleted once 10 full calendar years have passed since the end of the year of the refund, like the order it reverses.
- Reports: kept in full while they are open. 180 days after our decision we delete the explanation, quotes, location details, your name, your contact address, our notes and the details of our measures. The category, priority, status, our decision, the kind and time of our processing steps, any notification to authorities and the hash of your code remain stored with no automatic deletion period.
- Licensing service logs: rotate at 50 MB and are deleted when the container is recreated.
Messenger
- Identity, public keys and prekeys: until you delete your account.
- Direct messages: until collected, at most 7 days. Count of expired messages: 30 days.
- Attachments and their metadata: 7 days.
- Memberships of communities: until you leave, are removed, the community is dissolved or you delete your account. MLS handshake material: until it is used or superseded.
- Entries of group invite links: until the administrator’s app removes them, otherwise until their expiry time, which is at most 365 days and 1 hour ahead each time the link is created or renewed.
- Community streams: 7 days.
- Saved history of a community: at most the newest 100,000 records, until the founder switches it off or the community is deleted.
- Handshake log: for as long as the community exists.
- Suspended communities: the same periods as for any other community; a report or a suspension does not extend them. Block entries of group invite links we have revoked: one year from the revocation. Log of our measures: no automatic deletion period (section 5.10).
- Calls: IP addresses, start and end of the connection and data volume only for the duration of the call; the call relay does not store them.
- Session cache 15 minutes; proof of license entitlement until the end of the current hour; rate limiting at most 1 hour; vault during a device transfer through the server 10 minutes.
- Chat server logs: rotate at 50 MB and are deleted when the container is recreated.
11. Obligation to provide data
You are under no statutory obligation to provide us with personal data. We need the order data to complete the purchase; without it we cannot deliver a license. Your public keys and the user ID derived from them are technically required to use the messenger. The reply address in the contact form is optional; without it we cannot answer you.
12. No automated decision-making
No automated decision-making, including profiling, within the meaning of Art. 22 GDPR takes place.
13. Your rights
You have the right of access (Art. 15 GDPR), rectification (Art. 16), erasure (Art. 17), restriction of processing (Art. 18), data portability (Art. 20) and objection (Art. 21, see below).
Because we keep no accounts, we can only attribute data to you if you give us details that let us find it and check that you are entitled to it, such as the order ID and access code. Messenger data is linked only to your user ID; you can delete it yourself in the app (section 5.6).
You have the right to lodge a complaint with a data protection supervisory authority (Art. 77 GDPR), in particular in the member state of your habitual residence, your place of work or the place of the alleged infringement. The authority competent for us is:
Landesbeauftragte für Datenschutz und Informationsfreiheit Nordrhein-Westfalen (LDI NRW)
Kavalleriestraße 2–4, 40213 Düsseldorf, Germany
14. Right to object (Art. 21 GDPR)
Where we process data on the basis of Art. 6 (1) (f) GDPR (section 9), you have the right to object to that processing at any time on grounds relating to your particular situation. We will then no longer process the data unless we can demonstrate compelling legitimate grounds for the processing which override your interests, rights and freedoms, or the processing serves the establishment, exercise or defence of legal claims.
You can send your objection informally to aphotice2ee@proton.me.