Archive copy of version free-beta-1. Fixed address of this version:
/en/legal-archive/free-beta-1/privacy-free/. The text remains available here unchanged. If a newer version is in force, this is an earlier version; the version in force is at Privacy information.
1. The essentials
- Test phase. The Free plan is being trialled. There is no availability commitment, no commitment to restore your data from a backup and no third-party review. Do not store sensitive or business-critical content (section 3).
- What we collect at registration: the address you choose and a verification record for your password. The password itself does not leave your device. We do not ask for a name, phone number, second address or payment data.
- Your stored mail is encrypted on the server with a key of your account. This is the "Compatible" mode. It is neither end-to-end encryption nor "zero access": the server sees plaintext when delivering, when sending and during a mail session (section 6).
- Two exceptions to this encryption: Drafts and send jobs of the webmail are also kept in an operating journal protected by a server key that is the same for all accounts; completed entries are meant to lose the message and the attachments after 24 hours (what remains is the checksum, size, kind of operation and time), and the journal is meant to be deleted when your account is deleted. A message in the mail server queue lies unencrypted on the disk until it is delivered (section 4.2).
- Mail initially goes only between Free accounts. Addresses @privymail.eu cannot be reached from outside, and the service does not send mail to external addresses. Sending in the webmail and with an email client (IMAP and SMTP, with an app password) is intended. We do not promise that it is possible when this information is published.
- No advertising, no analytics, no third-party content. We set exactly two technically necessary cookies and use no tracking or analytics service (section 10).
- Access and deletion you request by e-mail; there is no button for them yet. We handle requests by hand, within one month. There is no bulk export. (sections 8 and 9)
2. Who is responsible?
(Art. 13(1)(a) and (b) GDPR)
| Operator of the website | patchletter UG (haftungsbeschränkt), Meisterweg 16, 45896 Gelsenkirchen, Germany; Amtsgericht Gelsenkirchen, HRB 20118; represented by the managing director Kolja Sagorski. The details come from the legal notice (Impressum) and are confirmed by the operator for the website only. |
| Controller and contracting party of the Free service | patchletter UG (haftungsbeschränkt), address and representation as above. |
| Contact for privacy questions and requests | legal@patchletter.com; general hello@patchletter.com, telephone +49 209 73085753; post to the address above. |
| Data protection officer | We have not appointed a data protection officer. For questions on data protection, use the contact above. |
3. What "test phase" means
The Free plan goes live for first users before all reviews and operating structures exist. The test phase has no fixed end; we announce its end with at least 14 days' notice. Before registration we show the key points in a box. Honestly, that means:
- The encryption of stored messages has not been reviewed by an external party (no external cryptography review). There has been no external penetration test. A data protection impact assessment under Art. 35 GDPR does not exist.
- The virtual machine on which the server runs is backed up in encrypted form; the backup storage is in Düsseldorf (Germany). Restoration is not promised and has not been demonstrated by a restoration test; it can lose data up to the time of the last backup. If the server or its disk fails, accounts and messages can be lost, and it is possible that nobody can sign in any more. Deleted content can remain in backups; we do not yet state how long backups are kept (section 8). At a software change we first create an intermediate copy of the account database on the same server, which stays until we delete it; it does not protect against a failure of the server (section 4.3). Data can be lost.
- There is no availability commitment and no round-the-clock on-call. The server installs software updates automatically and may restart at night for that; further restarts are possible.
- Mail goes only between Free accounts. Before external delivery is enabled we will update this privacy information.
- The number of accounts is limited for now. When the limit is reached, registration closes and reports that no places are free at the moment.
- If you lose your password and your recovery codes, access and mail cannot be restored. We have no master key for stored mailboxes.
4. Which data do we process? From where, where, how long?
(Art. 13(1)(c) and (e), (2)(a) and (e); Art. 14(2)(f) GDPR)
All data come from you or arise from your use. Exception: data of other people in messages that other Free users send you (sender address, content). Not processed as of today: name, phone number, date of birth, a second address, payment data, location data, and device or browser identifiers in the account database. Messages can contain any personal data, including particularly sensitive details such as health information. We process contents only technically, to store and deliver them, and we do not read them. The Free plan is not meant for such content during the test phase.
4.1 Account and sign-in
| Data | When and how | Where, how protected | Duration |
|---|---|---|---|
| Account address (chosen by you), account identifier (UUID), account status, creation time | registration | account database (PostgreSQL) on the server | until the account is deleted (section 8) |
| Sign-in verification record (OPAQUE, 192 bytes) instead of a password | registration, password change | account database; contains neither the password nor an ordinary hash | until the account is deleted; on a password change the old record is deleted |
| Encrypted copies of your mailbox key: one each for the password, for every app password and for each of the ten recovery codes | registration, new app passwords, new codes | account database; the codes and app passwords themselves are not stored, nor is a hash of them | until revoked or used up (the row is deleted), otherwise until the account is deleted |
| Per app password: label (at most 64 characters, from you), creation time, last use (date only) | creating and using | account database | until revoked |
| Second factor (optional): TOTP secret (encrypted) or passkey (public part only, identifier, counter and the flag whether the passkey is backed up across devices); label; date of setup and of last use | when you set it up | account database | until removed or the account is deleted |
| Session: hash of the session token, session identifier, kind of second factor, start (date only), three deadlines with a time of day (from them the sign-in time and the last use of the running session can be derived for as long as the row exists) | sign-in in the browser | account database; cookie in the browser (section 10) | at most 7 days, 24 hours idle, at most 10 sessions per account; expired sessions are removed by a run every 5 minutes |
| Free plan profile: rights (1,000,000,000 bytes of storage; IMAP, SMTP, CalDAV and CardDAV as rights in the profile; CalDAV and CardDAV are part of the plan but are not enabled in the first go-live), initial measurement of used bytes with time | completion of registration | account database | until the account is deleted |
| Setup record (account identifier, address) while setup is running | registration | account database | until completion; if the outcome is unclear it remains until the operator reviews it |
| Intermediate states of registration and sign-in; solved challenge | during the steps | memory; in the database only the signature of the redeemed challenge, without personal reference | memory 2 to 10 minutes; signature at most 5 minutes |
| Welcome message (sender noreply@ of the domain) | registration | your mailbox | like mailbox contents |
Proof of agreement: version label of the confirmed set of texts (for example free-beta-1) and time of confirmation | registration | account database (two columns on the account); no IP, no browser identifier, no history | until the account is deleted |
| Block entry of a deleted address: a keyed check value (HMAC-SHA-256, 32 bytes) of the address; no address in plain text, no account identifier, no time. It is created only for an account that was active, not for an abandoned registration | deletion of an account (section 8), so that the address is never issued again | account database; without the key of the service it can neither be reversed nor matched to an address | without limit; we do not remove it. It remains personal data (pseudonymised) for as long as we hold the key and can check an address |
The dashboard only reads these existing details and shows them to you. It stores nothing additional and keeps no sign-in history and no event log.
4.2 Mailbox, webmail, sending
| Data | When and how | Where, how protected | Duration |
|---|---|---|---|
| Messages (headers, text, attachments), folders, drafts, sent items, trash | receiving, storing, sending | mail server (Dovecot) on the server, encrypted with a key of your account ("Compatible", section 6); header and search index only in memory or in a RAM file system, never on the disk | until you delete them or the account is deleted; up to about 1,000,000,000 bytes, not exact to the single byte |
| Metadata that are thereby not fully hidden: number and size of messages, folder structure, identifiers, flags, times, usage patterns; in the index cache also headers such as subject, sender and recipient, as long as the mail server runs | on storing and retrieving | file system of the server; index cache in memory, readable by administrators | like messages; the index cache until the mail server or the server restarts |
| Webmail journal: drafts and send jobs including the complete message and attachments, state | saving a draft, sending | one database file per account on the server; the records (request, response, state) are encrypted with AES-256-GCM, with a server key that is the same for all accounts and sits on the same server; account identifier, address, channel and kind of operation are stored unencrypted in the file | Intended: completed entries are trimmed after 24 hours (message and attachments are dropped; checksum, size, kind of operation and time remain); until then the contents remain even if you delete the message in the mailbox; a limit per account applies to the size and number of entries; when the account is deleted the journal is deleted; the journal does not count towards your mailbox space. |
| App password in the webmail | when you choose "Connect" in the webmail | memory of the webmail service; not in the URL or browser storage | until disconnect, 5 minutes idle, or at most 15 minutes |
| Message in the mail server queue | sending to a Free account | file system of the server, unencrypted | until delivery; if delivery cannot succeed, until the default period of the mail server software of five days runs out |
| Sending counters: account identifier, opaque transaction identifier (hash), number of recipients, message size, time; last time stamp per account | on sending | account database; no addresses, no content, no IP | admissions count for 24 hours; expired rows are removed only on a further send admission of the same account, otherwise until the account is deleted; the time stamp until the account is deleted |
| Storage use | continuously | mail server (quota); initial measurement in the database | until the account is deleted |
Headers: The template of the mail server sets smtpd_hide_client_session = yes; the effect has not been checked in operation.
Free limits (for orientation): immediate sending; initially at most 10 recipients per 24 hours, after seven full days 50; at most 10 recipients and 10,000,000 bytes per message.
4.3 Protection, technology, logs
| Data | When and how | Where, how protected | Duration |
|---|---|---|---|
| IP address of the peer, shortened to a prefix (IPv4 /24, IPv6 /56), together with the address, for limits on registrations, challenges and failed attempts | with every request to these functions | memory of the account service only, not in the database; gone on restart. | time windows of 15 minutes to 1 hour; the service clears expired counters every minute, at most 61 minutes in total |
| Logs of the account service and of the database: account identifier, fixed event texts, counters; no address, no IP, no secrets, no contents; the database reports errors only in the short form without details | continuously | system journal of the server | at most 7 days (journal); a few early start-up messages of the database without user data are in a file on the server that the system rotates weekly and keeps for up to ten weeks |
| IP address and HTTP request when the interface is retrieved | on every request | web server (Caddy): processes them to deliver the response; no access logs. On an error (for example when the service behind it does not answer) the web server may write an error message containing your IP address to the system journal | only for the duration of the request; error messages in the system journal at most 7 days |
| Logs of the mail server: time, account address, IP, sender and recipient address, queue identifier, Message-ID, size, result; never message text or subject | on sign-in, delivery, sending | system journal of the server | at most 7 days |
| Block lists for failed sign-ins (fail2ban): IP, rule, time | on repeated failed sign-ins | for the mail ports and for the operator's SSH access | 7 days |
| Backup copies and intermediate copy | backups: encrypted backup of the virtual machine. Intermediate copy: at a software change by the operator | the backup covers the virtual machine and thus all data on the server; the backup storage is in Düsseldorf (Germany). Restoration is not promised (section 3). The intermediate copy is a dump of the whole account database (all accounts, access data, proofs of agreement, block entries, encrypted key copies) on the same server, readable only by administrators of the server | backups: we do not yet state the period (section 8). Intermediate copy: until we delete it after the change; we do not promise a fixed period |
| Details of abuse cases (report, measure, affected account) | in a suspected or actual abuse case | operator records; today there is no abuse database and no fixed procedure | at most 90 days |
| Messages to us (e-mail, telephone, post) | when you write to us | mailbox of patchletter UG at an e-mail service provider with which a data processing agreement exists (section 7) | until the request is closed, then deletion within 12 months, statutory retention duties reserved |
5. For what purpose and on which legal basis?
(Art. 13(1)(c) and (d) GDPR)
| Purpose | Data | Legal basis |
|---|---|---|
| Provide account, sign-in, mailbox, webmail, sending and receiving between Free accounts | account, sign-in, mailbox, journal and counter data | Art. 6(1)(b) GDPR (use of the free service under the terms of use). |
| Protect the service and accounts: challenge, limits, sending limits, account budget, security logs | IP prefix (memory), counters, logs | Art. 6(1)(f) GDPR. Legitimate interest: secure, abuse-free operation. Also Art. 32 GDPR. |
| Operation, troubleshooting, way back at a software change | logs, intermediate copy of the account database | Art. 6(1)(f) GDPR. Legitimate interest: run the service stably, find faults and be able to undo a software change. Where needed for performance of the contract, (b) |
| Session in the browser | session cookie, sign-in ticket cookie | § 25(2) no. 2 TDDDG (strictly necessary); processing under Art. 6(1)(b) GDPR |
| Prove which terms you confirmed | version label, time | Art. 6(1)(b) or (f) GDPR. Legitimate interest (if (f)): be able to show which terms were agreed and defend against claims. |
| Block a deleted address permanently | block entry (check value of the address) | Art. 6(1)(f) GDPR. Legitimate interest: protect the post and identity of former holders against a new registration of the same address. The balancing against your right to erasure is in section 8 |
| Handle your requests and rights | contact data, content of the request | Art. 6(1)(b), (c) or (f) GDPR, depending on the occasion. Legitimate interest ((f)): answer and document requests properly |
| Meet legal obligations (for example orders from authorities, notifications) | depending on the case | Art. 6(1)(c) GDPR |
| Consent | none | We do not base the Free service on consent. Agreeing to the terms of use is not consent within the meaning of the GDPR. |
Legitimate interests (Art. 6(1)(f) GDPR) are named per purpose in the table; your right to object is in section 9.
6. Who can technically access your data?
An honest answer for the "Compatible" mode (the default).
- Stored messages are encrypted with a key of your account. The private key exists only "wrapped", once each for your password, every app password and every recovery code. We have no master key.
- Compatible is neither end-to-end encryption nor "zero access". The server sees plaintext (a) when delivering and sending, (b) during a mail session through webmail or a mail program, because Dovecot then holds the unlocked key in memory, (c) on account changes such as new app passwords, where your device sends the server an unlock secret derived from the password (memory only, not stored).
- The same limit applies to anyone with administrator access to the running server. The server runs without disk encryption.
- Transport: browsers connect only over HTTPS. TLS is intended for mail programs, at least TLS 1.2.
| Who | What is technically possible | Rule or protection |
|---|---|---|
| Operator (administrators with root access) | inspect memory and index cache (key, plaintext and headers while running), queue, database, service secrets including the key of the webmail journal | Rule: contents are not read; operation and troubleshooting work with counters and status. The abuse rules (draft) promise not to search stored messages for violations. Not technically enforced. No four-eyes principle. Only the operator has access to the server, with an SSH key; sign-ins are in the system journal (at most 7 days). |
| AI-assisted tools in development | We develop and operate the service with AI-assisted tools; the model provider is a US company (Anthropic). Such a tool works with administrator rights on the production server where your data are kept. | We use it for set-up, maintenance and troubleshooting on behalf of the operator; the operator can withdraw the access at any time. Our working rules forbid putting secrets and message contents into logs and outputs, and the tool does not read message contents as a matter of course; technically, access to them is not excluded. The tool's commands and their outputs are sent to the provider in the USA for processing. |
| Hypervisor and data centre | The server is a virtual machine (KVM) on a Proxmox server that the operator runs itself; the hypervisor belongs to the operator. Technical access to memory and disk is possible at the level of the virtual machine. The Proxmox server stands in a data centre; we have not checked what access its operator has to the hardware. | Data centre in Helsinki (Finland). We will name the data centre operator and state the data processing agreement once confirmed (section 7). |
| Other Free users | only messages you send them, with your sender address. Whoever uses the registration can, after solving a challenge, query whether an address is taken. | challenge, limits |
| Authorities and courts | only where we are legally obliged | We forward requests to a lawyer for review. |
Metadata (sender, recipient, time, size, folder) are visible to the server at every protection level. In this stage there is no automatic content scanning (spam or virus filter), and the service queries no block lists or information services of third parties.
7. Recipients, processors, third countries
(Art. 13(1)(e) and (f) GDPR)
| Recipient | Purpose | Data | State |
|---|---|---|---|
| Data centre operator of the server | server and storage | all data on the server, protected as in section 6 | Data centre in Helsinki (Finland). We will name the operator and the data processing agreement once confirmed. |
| Operator of the backup storage | encrypted backups of the virtual machine | all data of the virtual machine, backed up in encrypted form | Storage in Düsseldorf (Germany). We will name the operator and the data processing agreement once confirmed. |
| DNS operator of the domain privymail.eu: INWX GmbH, Berlin | name resolution | no user data; the operator sees queries of the asking resolvers | Data processing agreement concluded. |
| Other Free users | delivery of your messages | sender address, message | not applicable |
| E-mail service provider for the mailboxes of patchletter.com | when you write to us | your message to us | Data processing agreement concluded. |
| AI-assisted tools | development | commands and outputs of the tool with administrator rights; user data are not excluded (section 6) | |
| Host of the source code (USA) | code and documentation of the project | no user data; reports contain only counters and hashes | Code and documentation are kept there in a private repository. |
| Authorities, courts | only where legally obliged | depending on the order | not applicable |
Not involved: advertising and analytics services, third-party CAPTCHA services, payment service providers (Free is free of charge), VPN providers (not part of this plan in the first go-live), spam or reputation services of third parties in this stage.
Third countries. We do not intend to transfer user data to countries outside the EU and the EEA. Two third-country links do exist, however: the AI-assisted tools in development come from a company based in the USA, and the source code is kept with a host in the USA (sections 6 and 7). The source code contains no user data. The tool with administrator rights on the production server can, however, see user data there, and its commands and outputs go to the provider in the USA for processing (section 6). When external delivery of mail is enabled (later), messages can go to servers outside the EU; we will inform you beforehand.
Data of third parties (Art. 14). Messages contain data of other people, for example senders. We process them only to provide the service for you and do not inform these people individually.
8. How long do we store data? Deletion
(Art. 13(2)(a) GDPR)
The periods are in the tables in section 4. In short:
| Data | Duration |
|---|---|
| Sessions | at most 7 days, 24 hours idle |
| Intermediate states, challenges | minutes |
| Counters for limits (IP prefix) | at most 61 minutes (time window of up to 1 hour plus the clean-up run every minute), memory only |
| Logs of the account service, of the database and system journal | at most 7 days; a few early start-up messages of the database without user data up to ten weeks (section 4.3) |
| Logs of the mail server | at most 7 days |
| Details of abuse cases | at most 90 days |
| Account, sign-in and plan data, proof of agreement | until the account is deleted |
| Block entry of a deleted address (check value) | without limit (section 4.1) |
| Mailbox contents | until you delete them or the account is deleted |
| Index cache (headers) in memory | until the mail server or the server restarts |
| Webmail journal | Intended: message and attachments are dropped 24 hours after the operation is completed; the rest remains until the account is deleted, then the journal is deleted |
| Backups | The virtual machine is backed up in encrypted form. We do not yet state how long backups are kept; deleted content can remain in them until they expire. At a software change an intermediate copy of the account database is additionally created, which we delete after the change; we do not promise a fixed period (section 4.3). |
Deletion today. There is no button for deleting an account. You delete individual messages, app passwords, sessions and second factors yourself. We delete a whole account by hand on your request within 30 days with our operator tool. There is no cooling-off period; you can withdraw your request until it is carried out. After deletion the address is not issued again. For this we keep a block entry, that is, a keyed check value of the address without plain text, without account identifier and without time, without limit (section 4.1). Its purpose is to protect the post and identity of former holders; the legal basis is Art. 6(1)(f) GDPR. You can object to this storage under section 9; we examine an objection case by case. In doing so we remove the account and access data from the database and delete the mailbox together with the key copies; the block entry remains as the only remnant in the database. Deletion removes the rows from the database. Physical remnants (for example address and account identifier) may remain on the disk of the server until the database service overwrites the space at a later clean-up or with new data; we do not promise a fixed period for that. The webmail journal is meant to be deleted together with the account. Logs disappear only when their periods expire. Deleted content may still be contained in backups of the virtual machine; we do not yet state for how long (section 8). An intermediate copy of the account database (section 4.3) may likewise still contain the account until it is deleted. There is no automatic deletion of unused accounts. Orphaned registrations whose key never reached the mail server are discarded by the clean-up run (every 5 minutes) as soon as they are older than 15 minutes.
9. Your rights
(Art. 13(2)(b) to (d) GDPR)
You have the right of access (Art. 15), rectification (Art. 16), erasure (Art. 17), restriction (Art. 18), data portability (Art. 20) and objection to processing based on legitimate interests (Art. 21). There is no consent in the Free service that you could withdraw (Art. 7(3)).
- How to exercise your rights: by e-mail to legal@patchletter.com (alternatively hello@patchletter.com) or by post to the address in section 2. We reply without undue delay and at the latest within one month (Art. 12(3) GDPR). Exercising your rights is free of charge. Please do not write passwords, codes or mail contents into the request.
- Proof: So that nobody can obtain someone else's data by deception, we reply only to the address of your account and require proof from the signed-in account. We handle requests by hand, within one month. Accounts without access: Without password and recovery code we cannot release or delete anything.
- Export and data portability (Art. 20): There is no bulk export, and we cannot decrypt and hand over your mailbox without your password or a recovery code. You download individual messages in the webmail as a file. Retrieving all messages with a mail program via IMAP is intended; we do not promise that it is possible when this information is published (section 1). We answer requests for data portability by referring to this retrieval, within one month.
- Complaint: You can lodge a complaint with any data protection supervisory authority (Art. 77 GDPR), in particular at the place of your residence or of the alleged infringement. Competent for us: the State Commissioner for Data Protection and Freedom of Information of North Rhine-Westphalia (Landesbeauftragte für Datenschutz und Informationsfreiheit Nordrhein-Westfalen), Kavalleriestraße 2-4, 40213 Düsseldorf, Germany, postal address Postfach 20 04 44, 40102 Düsseldorf.
Your right to object
You have the right, on grounds relating to your particular situation, to object at any time to processing of your personal data that we base on legitimate interests (Art. 6(1)(f) GDPR) (Art. 21(1) GDPR). We then no longer process the data unless we can demonstrate compelling legitimate grounds for the processing that override your interests, rights and freedoms, or the processing serves the establishment, exercise or defence of legal claims. We do not process your data for direct marketing. Send your objection to the address in section 2.
10. Further information
- Do you have to provide data? For an account, address and password are necessary; without them we cannot set up an account. For webmail and mail programs you need an app password. A second factor and labels are optional. (Art. 13(2)(e) GDPR)
- Cookies: Only two technically necessary cookies on
account.privymail.eu:__Host-privymail-session(session, at most 7 days) and__Host-privymail-login(sign-in step, at most 10 minutes). Both areSecure,HttpOnlyandSameSite=Strict. There is no local browser storage, no service worker, no fonts or scripts from third parties and no tracking or analytics service; you choose the language through the address (/de/, /en/). The webmail does not load external content from messages. - Automated decisions, profiling: We do not build profiles and do not take any decision based solely on automated processing with legal or similarly significant effect (Art. 22 GDPR). Limits do take effect automatically: blocking sign-in attempts for a time window, temporary refusal of mail above the Free limits (SMTP 451), temporary refusal of requests in webmail when an account makes too many at once or too quickly one after another (a technical protection of the other accounts, not a measure against you), closing registration when the account budget is reached. There is no automatic account suspension.
- Minimum age: You must be at least 16 years old. If you are not yet 18, clause 4.2 of the terms of use also applies (consent of your parents or legal guardians).
- Commitments: We do not use your data for advertising and do not sell it.
- Changes: We adapt this privacy information when processing or the legal position changes, in particular before external delivery of mail and at the end of the test phase. The current version carries version and date. We announce material changes on the website and, as far as possible, by a message to your mailbox.
- Further texts: The Terms of use and the Acceptable use policy belong to the same set of texts (version free-beta-1).
- Version: free-beta-1 dated 21 October 2026, revised on 8 November 2026 (details on the location of the server and on backups, sections 1, 3, 4.3, 6, 7 and 8).