# Consent and legal

Mailwerk records why a message may be sent and why it was skipped. The customer
usually controls recipient processing; Mailwerk processes that data on the
customer's instructions. Mailwerk separately controls its own login, contract,
support and security data. These roles depend on the actual purpose.

This document describes the implemented controls and the pilot operating
contract. It is not a claim of universal GDPR or US compliance.

## 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](mailto: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](https://www.edpb.europa.eu/sme/be-compliant/process-personal-data-lawfully_en).

**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](https://www.ldi.nrw.de/kontakt).
[EDPB rights guidance](https://www.edpb.europa.eu/sme/be-compliant/respect-individuals-rights_en)
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.

## Mailwerk's own early-access waitlist

Burlis Management GmbH is the controller for this purpose. The optional unchecked
checkbox asks only for information about Mailwerk availability and early access,
not other portfolio marketing or account registration. The basis is consent,
Article 6(1)(a) GDPR. The exact notice is:

> Email me about Mailwerk early access. Burlis Management GmbH. Unsubscribe any time.

The server fixes `mailwerk` / `early_access`, notice version and signup source.
It validates affirmative consent and admits requests persistently before creating
a contact. Request, confirmation, notice and withdrawal evidence use the existing
ledger. Confirmation GET is read-only; only the existing POST consumes the token.
The acknowledgment does not disclose whether an address exists, is confirmed or
suppressed, and does not claim delivery or subscription.

After confirmation the recipient can immediately leave the waitlist without
sign-in; the confirmation email also permits cancellation. Withdrawal stops future
marketing and does not affect the lawfulness of earlier consent-based processing.
Consent may also be withdrawn through the contact above. No open/click tracking is
added to the confirmation or sign-in email. Public collection is live with the dedicated sender and notices; the
[deployment record](hosting-coolify.md#deployment-state) records the proof.

Unconfirmed waitlist-only signup data is erased after 30 days. The distinct auth
recipient survives only for its separate account purpose. Confirmed subscriptions
remain until withdrawal or waitlist closure, with an operator necessity review after
12 months of inactivity. Necessary minimized suppression and ambiguous-attempt
records have their separate protection/replay purposes. No address is sold or used
for a broader marketing purpose. Required information about providers, transfers
and rights appears in the [public notice](https://mailwerk.io/legal/privacy).

Interest totals count distinct people currently confirmed, valid pending people
and withdrawals; 30-day changes are identified separately. There is no visitor
tracking, behavioral profile or conversion percentage without a visitor denominator.

## Double opt-in, and nothing else

`consentRequest` stores the purposes, exact notice, version, source and request
time, then sends an unmeasured confirmation. The link lasts seven days. Opening
it with GET is read-only; POST consumes it and confirms the listed purposes.
At most three new confirmation requests per contact and 100 per project are
accepted each hour. Projects default to 10,000 contact rows, including erasure
tombstones; the operator sets the admitted limit.
A retry can return a visible limit error; Mailwerk never silently sends it later.

Only confirmation creates new consent. An operator migration may preserve
previously confirmed evidence; a provider's subscribed flag is insufficient.
Changing an address withdraws the old mailbox's permission and invalidates its
pending links. Changing profile properties does not change consent.

Double opt-in is Mailwerk policy. German advertising law generally requires
express permission for email marketing, with a conditional existing-customer
exception; it does not mandate one universal proof method. Mailwerk does not
implement that exception as an alternative sending path. [UWG §7](https://www.gesetze-im-internet.de/uwg_2004/__7.html)

## What is stored as evidence

| Field                                  | Purpose                                                     |
| -------------------------------------- | ----------------------------------------------------------- |
| Purposes                               | What the person was asked to receive                        |
| Notice text and version                | The exact wording shown                                     |
| Source                                 | The signup surface, without recipient data or query strings |
| Request, expiry and confirmation times | When permission was requested and established               |

Store the notice verbatim and change its version when its meaning changes.
Historical copy is not rewritten during template updates or storage migration.
Imported evidence retains its original text, source and timestamps.

The consent ledger derives current state by timestamp and explicit event
sequence, so tied timestamps retain their original order. It is append-only
for ordinary consent operations; a verified erasure removes identifying text
and sources while retaining minimal action/timing evidence.

## Purposes

Projects declare marketing and transactional purposes. Marketing requires
current confirmed consent for the template's purpose. Transactional content
must actually serve its stated service purpose: setting an API field does not
turn advertising into a service message. Consent to one purpose cannot be used
for another.

## Withdrawal

The footer GET link and RFC 8058 POST both withdraw every marketing purpose in
that project immediately, without login or a confirmation step. Pending
confirmation links are invalidated and scheduled lifecycle work stops.
`consentUpdate` can narrow an existing choice; widening requires a new request.

An old unsubscribe link remains usable after contact erasure. Its opaque mapping
returns the same successful result without exposing the former contact. It
cannot subscribe a replacement contact or affect another project.

Provider requests already handed off cannot be recalled. Send eligibility is
checked immediately before that handoff; withdrawal prevents subsequent attempts.
During database unavailability, the route returns a truthful failure instead of
claiming a persisted opt-out. The operator must reconcile an outage before
resuming affected sends.

For applicable US commercial email, opt-out mechanisms must remain available
for at least 30 days after sending and requests must be honored within ten
business days. Mailwerk's immediate withdrawal policy is stricter. Accurate
sender/subject information, an address, opt-out and applicable advertisement
identification are separate requirements. [FTC CAN-SPAM guidance](https://www.ftc.gov/business-guidance/resources/can-spam-act-compliance-guide-business)

## The footer contract

The shared shell supplies sender identity/imprint and privacy links. Marketing
also carries consent date/source, a visible unsubscribe link and RFC 8058
headers. Use plain wording such as “Subscribed to PRODUCT on DATE via SOURCE.”
The project's registered identity/address must be accurate. Templates cannot
replace the shell to remove these fields.

## Suppression

A keyed email digest records a hard bounce, complaint or manual suppression.
A hard bounce blocks all classes and is never downgraded. Complaint/manual
entries block marketing. No operation clears suppression to resubscribe someone.
SES account complaint records remain in place. Marketing's default and measured
configuration sets retain account-level `BOUNCE`/`COMPLAINT` suppression, including
for addresses whose complaint arose in another project. A declared nontracking
`transactionalConfigurationSet` uses account-level `BOUNCE` suppression so a prior
marketing complaint does not block a requested sign-in or confirmation. Until
configured, existing projects retain their existing route. Customer operations
never disclose another project's suppression membership.

Digests, encrypted values and opaque linked identifiers remain pseudonymous
personal data where Mailwerk can link them. Their retention requires a defined
purpose, restricted access and a periodic necessity review.

## Erasure

`contacts.export` returns this recipient's readable address/profile, full
request/consent history, inbound events, message/feedback history, enrollments,
campaign claims and project suppression metadata. It excludes token capabilities,
credentials and unrelated customers. `contacts.get` plus `consent.get` is not a
complete access export. Exports are returned directly, not stored in a new
server-side download repository.

`deleteContact(externalId)` performs one transaction:

- Clear the address, profile, message digest/failure detail, linked feedback
  detail, inbound payloads, identifying consent text/version/source and
  suppression source. Replace caller-controlled identifiers with keyed
  tombstones and end active/claimed enrollments.
- Invalidate every confirmation token, retain opaque unsubscribe mappings and
  preserve suppression. Retain minimal message/campaign claims and hashed
  idempotency references so erasure cannot authorize a duplicate send.
- Record erasure and withdraw existing consent. A repeated deletion returns
  `{erased: false}`. A deliberate later upsert creates a different recipient
  with no inherited consent; existing suppression still applies.

`contacts.delete` with `fenceMissing: true` also records an address-free erasure
fence when creation has not arrived. `contacts.upsert` with `restoreErased: false`
refuses a delayed create against that fence. Keep the product-side reference
until erasure succeeds; use a fresh opaque ID for a deliberate new account.

The same address in another project is untouched. A retained tombstone is not
an anonymous record or a blanket legal exemption. Record the specific need and
review period for suppression, ambiguity and residual evidence. Contact erasure
does not erase a customer's shared template or legal content: customer-authored
templates must contain reusable copy, not recipient records. Inspect an export
for third-party data before releasing it.

## Retention and recovery

| Data                                                 | Implemented behavior / operating requirement                                                                                                                                                                                                                                                                                    |
| ---------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Pending DOI                                          | Seven-day validity; delete unused request and its requested-event content after a further seven days                                                                                                                                                                                                                            |
| Message, feedback and activity history               | Remove identifying history after 24 × 30 days; retain only a minimized claim/reservation with hashed idempotency references to prevent replay                                                                                                                                                                                   |
| Unknown provider outcome                             | Keep the claim; minimize recipient data on erasure; reconcile without blind retry                                                                                                                                                                                                                                               |
| Inactive transactional contacts                      | Optional `policy.inactiveContactRetentionDays` (30 for Sledge) erases address/profile and identifying history at the next successful daily cleanup after the limit (normally within 31 days for Sledge), when there is no confirmed consent or active lifecycle; minimal replay/suppression evidence keeps its separate purpose |
| Active recipient and consent evidence                | Keep only while needed for the customer's documented purpose; erase on a verified applicable request                                                                                                                                                                                                                            |
| Inbound payload and enrollment/campaign associations | Included in export and erasure; customer offboarding must cover them, not just contacts                                                                                                                                                                                                                                         |
| Suppression / opaque opt-out mappings                | Retained to prevent sending and honor old opt-outs; document necessity and review at offboarding                                                                                                                                                                                                                                |
| Login/session/OTP data                               | Separate account export/offboarding includes the transactional auth recipient; daily removal of expired/exhausted encrypted verification, sessions, legacy invitations and rate-window records; no code/token values in exports                                                                                                 |
| Mailwerk waitlist-only data                          | Erase abandoned unconfirmed signup data after 30 days; keep confirmed subscriptions for the stated purpose with a 12-month inactivity review; source admission digests clear after one day                                                                                                                                      |
| Operational logs                                     | No recipient addresses or token URLs; verify actual proxy/provider log retention before pilot activation                                                                                                                                                                                                                        |
| Backups                                              | pgBackRest uses fourteen-day chain-aware history; hidden B2 versions expire after one day in the PostgreSQL prefix. History must accumulate and expiry age naturally. Include retained base backups and scratch copies when checking the thirty-day operating maximum; retained legacy archives need their approved expiry      |

Erasure does not rewrite existing backups. A restored database starts isolated
from customer access and sends. Reconcile subsequent erasure, withdrawal,
suppression, grants and provider attempts before reopening it. Old credentials
and uncertain messages remain invalidated or held. An old backup cannot prove
what happened after it was taken. See [operations](operations.md).

## Customer onboarding and rights handling

Operator-assisted requests are sufficient for the pilot. Confirm the requesting
controller's authority, record the request date and applicable response deadline,
resolve the correct organization/project/contact, execute the scoped operation,
and verify the result. Send exports only through an authenticated route approved
for that customer. Retain a receipt with scope, time and counts, without copying
the export into logs, tickets or agent transcripts.

Mailwerk's service operator is Burlis Management GmbH, Philippstraße 27,
52349 Düren, Germany; the published contact is hello@mailwerk.io. These details
come from the existing imprint. The customer contract must name its actual
controller and authorized contacts rather than inventing them.

Before external recipient data is accepted, complete the actual processing
schedule and Article 28 agreement: instructions, data/subject categories,
duration, confidentiality, security, subprocessors, rights/incident assistance,
return/deletion and audit arrangements. Suitable existing clauses may be used;
fill their particulars and record the accepted version. Keep business terms/AUP
compact. There is no blanket outside-counsel or certification gate.

Maintain one processing/security/retention register covering recipient and
account data. Screen actual DPIA/DPO triggers and jurisdictional duties; a small
team is not automatically exempt from routine processing records. Advice is
needed only for a specifically unresolved material question. [EDPB small-business
guide](https://www.edpb.europa.eu/sme/be-compliant/be-compliant_en),
[BDSG §38](https://www.gesetze-im-internet.de/bdsg_2018/__38.html)

For recipient incidents, notify the customer controller without undue delay
and provide facts as they become known. Separately assess Mailwerk's duties as
controller for its own account data; do not wait 72 hours before telling a
customer. Record affected projects, containment, missing facts, rights risks and
follow-up decisions. Use the customer's agreed incident contact.

Actual hosting location, B2 region/retention, provider contracts and international
access must be verified before making specific transfer claims. SES uses
`eu-north-1`. EU storage alone does not establish that all processing stays in
the EU; recipient mailboxes and provider access have their own locations.

## Every tenant publishes the paragraph before its first marketing send

A live privacy notice is Mailwerk policy and is enforced by `policy.liveAt`.
Transactional and confirmation mail remain unmeasured. New external pilots use
no open/click tracking; existing internal measurement settings remain unchanged.

Where an existing internal project measures, it uses an unmeasured set for
transactional/confirmation mail and a separate measured set only for marketing
whose confirmed purpose and notice version cover that measurement. Mailwerk
removes recipient open/click history on measurement withdrawal and discards
late measurements without current permission. A policy
update cannot widen old consent. Historical notices remain intact. Provider
collection from already delivered pixels is a separate provider capability and
must not be claimed stopped merely because Mailwerk rejects or clears an event.

## The paragraph: EN and DE

Adapt these short service descriptions to the customer's actual controller,
legal basis, rights contact and verified processing/retention details. They are
not a replacement for those particulars. Add a measurement paragraph only when
that project actually measures and has the relevant permission.

### English

> We use Mailwerk, operated by Burlis Management GmbH, to manage email delivery,
> subscription choices and delivery feedback. Amazon SES delivers messages from
> its Stockholm region. We store your email address, account reference and the
> information needed for these messages. Marketing starts only after you confirm
> your subscription. You can stop marketing emails using the unsubscribe link or
> your mailbox's unsubscribe button, without signing in. We keep delivery history
> for up to 24 months. On erasure, we remove your address and profile and retain
> limited suppression and delivery evidence to prevent further or duplicate
> sending. Protected backups expire under the stated backup retention schedule.

### Deutsch

> Wir nutzen Mailwerk, einen Dienst der Burlis Management GmbH, für den
> E-Mail-Versand, Ihre Abonnementauswahl und Zustellrückmeldungen. Amazon SES
> versendet die Nachrichten aus der Region Stockholm. Wir speichern Ihre
> E-Mail-Adresse, Ihre Kontokennung und die für diese Nachrichten nötigen Daten.
> Marketing-E-Mails beginnen erst nach Ihrer Bestätigung. Über den Abmeldelink
> oder die Abmeldefunktion Ihres E-Mail-Programms können Sie sie ohne Anmeldung
> stoppen. Zustellnachweise speichern wir bis zu 24 Monate. Bei einer Löschung
> entfernen wir Adresse und Profildaten; begrenzte Sperr- und Versandnachweise
> bleiben erhalten, um weitere oder doppelte Sendungen zu verhindern. Geschützte
> Sicherungen laufen nach der angegebenen Aufbewahrungsfrist aus.

## Opt-in copy that passes

“Product news by email?” followed by a short purpose description and two equal
choices: **Yes, sign me up** / **Not now**. Remember refusal without blocking
normal use. No extra checkbox, Continue step, bundled terms acceptance or
privacy-notice agreement. Link the privacy notice and show required purpose and
controller information. Confirmation: “Subscription confirmed.” Withdrawal:
“Marketing emails stopped.” Keep legal detail where it helps the decision.
