DRAFT - npubmail is in public beta; this document is being finalised. # npubmail: Privacy Policy (DRAFT) *Draft for legal review. Placeholders in `[to be completed]`.* ## 1. Controller and contact [to be completed], [to be completed], [to be completed]. Data protection officer: [to be completed]. ## 2. Our approach: we hold as little as possible - No account data: your identity is a public key. No name, email or phone number. - No payment identity, no balances: Lightning only, paid per action; we see that an invoice was paid, not who paid it, and we never hold your money. - Stored mail is encrypted to your key. We cannot read it. - Short retention: 7 days by default. ## 3. What we process, why, and for how long | Data | Purpose | Legal basis | Kept | |---|---|---|---| | Your public key, mailbox name, aliases, settings | Run your mailbox | Art. 6(1)(b) GDPR (contract) | Until you delete the mailbox, or after [to be completed] days of inactivity | | Incoming mail (headers, body, attachments) | Deliver mail to you. While it is processed, we check sender authenticity (SPF/DKIM), extract codes and links, and flag suspected prompt injection; then it is encrypted to your key | Art. 6(1)(b); for third-party senders' data Art. 6(1)(f) (legitimate interest: delivering mail addressed to the mailbox) | Encrypted, 7 days (or your paid retention period) | | Outgoing mail | Deliver it to the recipient; retry for up to about 2 days on temporary failures | Art. 6(1)(b) | Signed copy only until delivered or given up (max. ~2 days) | | Send records | Enforce quotas and bounce limits | Art. 6(1)(f) (protecting the Service and its reputation) | Count and time only, no addresses or subjects; 7 days | | Correspondent list | Allow replies to people who wrote to you | Art. 6(1)(b) | Salted hashes only, never addresses; 90 days after last contact | | Bounce records | Bounce limit | Art. 6(1)(f) | Hashed recipient; 7 days | | Server logs (IP address of API clients and sending mail servers, time, request path) | Security, abuse defence, troubleshooting | Art. 6(1)(f) | [to be completed] days | | Payment requests (invoice id, amount, purpose, hash of the paid request, key) | Unlock the paid action once | Art. 6(1)(b) | 7 days. Accounting records (amount, time, no key) are kept in the wallet as required by tax law ([to be completed] years) | We do not use your data for advertising, profiling or AI training. We do not sell data. ## 4. Recipients - Hosting provider: [to be completed] (processor, Art. 28 GDPR). - Receiving mail servers of the people you mail, as part of delivery. - Authorities, where we are legally obliged to (e.g. under the Telecommunications Act, TKG). We can only hand over what we have: see section 2. ## 5. Transfers outside the EU Servers are in [to be completed]. Mail you send to recipients outside the EU is transferred at your instruction (Art. 49(1)(b) GDPR / your role as controller). ## 6. Your rights Access, rectification, erasure, restriction, data portability, objection (Art. 15–21 GDPR), and the right to complain to a supervisory authority, e.g. [to be completed]. **Identification:** because we hold no identity, we can only act on a request that proves control of the key, i.e. a request signed with it. The API gives you direct access to all your data (`GET /v1/messages`, `/v1/mailbox`, `/v1/aliases`) and deletes everything with `DELETE /v1/mailbox`. **Third parties** (people who mailed a npubmail address): stored mail is encrypted to the mailbox owner's key, so we cannot search it for your data. Write to [to be completed] and we will do what is technically possible, e.g. delete a mailbox involved in abuse. ## 7. Security TLS for the API and, where the other side supports it, for mail transport. Stored mail encrypted with keys we do not hold (secp256k1 ECDH + XChaCha20-Poly1305). Mailbox creation requires proof of work; every API request is signed and protected against replay. ## 8. Changes We update this policy when processing changes. The current version is always at [to be completed].