Data residency

Epostix hosts customer email content and audience data on EU infrastructure. The published sub-processor list names Hetzner facilities in Germany and Finland.

Stored message content

Outbound and inbound message bodies are encrypted before storage and decrypted when read through the service. Message metadata, including sender, recipient, subject and delivery events, is stored separately from the body.

Inbound webhooks carry metadata and a message ID. Fetch the body through the authenticated inbound API when you need it.

Delivery and external services

Delivering an email sends its content to the recipient's provider, which may operate outside the EU. A webhook also sends its payload to the endpoint you configure.

Billing and network services have their own processing locations. The sub-processor list explains the roles of Stripe and Cloudflare, the data they handle and the applicable transfer safeguards. EU hosting of message content does not mean every kind of account or network data stays in one region.

Policies and deletion

The Data Processing Agreement sets out processing instructions, retention and deletion terms. The Privacy Policy covers account, billing and website data. Contact legal@epostix.com if you need a countersigned DPA.

Use the documented deletion operation for each resource. The developer API exposes inbound message deletion; it does not expose a delete operation for sent outbound messages. Do not treat removing a record from a view as confirmation that all retained data or backups have been erased.