Account privacy
Last updated: 23 September 2026. This notice covers pre-created company owners using the deployed email-code login. Existing projects keep their preserved keys. Public registration is unavailable; new customer admission remains operator-assisted.
Who is responsible. Burlis Management GmbH, Philippstraße 27, 52349 Düren, Germany, controls Mailwerk account data. Contact hello@mailwerk.io for privacy questions or requests.
What we use and why. The approved operator supplies the owner's name, email address and existing organization/project assignment. We use email codes to prove mailbox access for that pre-created account. A code expires after five minutes, is encrypted in transient authentication storage, and is not copied into recipient properties, events, message history, logs or exports. We keep the login profile, company membership, account/session identifiers, creation/update/expiry times, browser user-agent information and short-lived security records. Content approvals also record the owner's opaque internal ID. No OAuth provider, repository access or social profile is required.
Account processing identifies the owner, grants the correct project access, answers support requests and protects the service. For company representatives, the basis is our and the company's legitimate interests under Article 6(1)(f) GDPR. Where the owner personally contracts with us, necessary account/service processing instead rests on Article 6(1)(b). Security and abuse prevention rely on the stated legitimate interests. Required business/legal records rest on the applicable obligation, Article 6(1)(c). Sign-in never creates marketing consent. These bases have different conditions; see the EDPB explanation.
Cookies and choice. Necessary host-only first-party cookies keep the owner signed in and protect the sign-in exchange. No advertising or analytics cookies are added. Without the required mailbox and session data, we cannot provide account access. Waitlist confirmation does not create an account. Account data is not used for behavioral profiling or automated decisions with legal or similarly significant effects. Contact us if an access decision is wrong.
Who receives data. Authorized operators and the providers needed to host, secure, back up and deliver the service can process relevant account data. Hosting uses Hetzner Online GmbH and Cloudflare, Inc.; encrypted PostgreSQL backups use Backblaze B2 in its verified `eu-central-003` region. Hosting/proxy providers process connection metadata, including IP addresses; IP tracking in Mailwerk authentication session records is disabled. Amazon SES in Stockholm (`eu-north-1`) sends sign-in codes through Mailwerk's dedicated unmeasured sender. The chosen mailbox provider receives the email. No third-party AI processing of recipient data is introduced.
EU storage does not mean all processing stays in the EU. AWS, Cloudflare and Backblaze have US parent companies; applicable data-processing agreements govern processing and transfers, including contractual safeguards where required. The recipient's mailbox provider has its own locations and terms. Contact us for the safeguards applicable to your data.
How long. Login profiles and memberships remain while access is needed. Sessions expire after seven days unless renewed through use; signing out ends that session. Codes expire after five minutes and have three verification attempts; expired or exhausted verification records and obsolete security counters are removed by retention. A verified account-erasure request pauses owned projects, removes the login/memberships/sessions and erases the separate transactional sign-in recipient. Account export includes that recipient's delivery evidence, never the code value or live session/token capabilities. Waitlist data is a separate purpose and is not silently used as an account profile.
Revision history retains an opaque reviewer reference while the company needs that history; necessity is reviewed at offboarding. Support and required business records are kept only for their purpose or applicable legal period. Backups expire through their retention cycle; restores must reconcile erasure before access resumes.
Your rights. You may request access, correction, erasure, restriction and, where applicable, portability; you may object to processing based on legitimate interests. Write to the contact above. We verify identity proportionately and respond within one month, explaining any lawful extension. You can complain to a supervisory authority, including LDI Nordrhein-Westfalen. EDPB rights guidance explains when each right applies.
Before an external pilot. Verify actual hosting/proxy/backup processing, log and backup retention, contracted recipients and transfer mechanisms before accepting external customer account data. The production migration established the B2 region, backup configuration and initial restores; it did not complete customer contract particulars. The current internal-owner feature does not open public customer admission.