Security and privacy
This page summarises how sending works and the main measures in place. The Privacy Policy, the DPA, the Subprocessors page and the Terms of Service describe their scope and conditions.
Where the data lives
The primary infrastructure, which includes the application, database and queues, is hosted on Hetzner servers in Germany. Backups are encrypted and kept in Germany.
We use Amazon SES, in the Frankfurt region, to deliver email. Traffic to our sites goes through the Cloudflare network for DNS, protection and delivery. The use of other providers and any international transfers are described in the Privacy Policy and on the Subprocessors page.
Attachments, available for sending through the API, are kept temporarily to handle the sending and then deleted according to the times described in the Privacy Policy.
Customer data kept separate
We use PostgreSQL Row-Level Security policies to limit access to each customer's data. Their operation is checked by automated tests.
The Amazon SES account used for sending is shared among mailronix customers. The account's reputation and limits can therefore be affected by other customers' traffic, as described in the Terms of Service.
Access and keys
API keys have permissions for a single function, such as sending, reading and managing contacts. They cannot create other keys or change the account settings.
Sensitive actions, such as creating a webhook endpoint or deleting the account, require the password to be verified again. Passwords are stored as a hash.
Events sent to your webhooks are signed with HMAC through the Mailronix-Signature header, so that you can verify their authenticity and integrity.
Email tracking and site statistics
Email opens are not tracked. Click tracking is optional and requires the brand to turn it on and the recipient to consent. Revoking consent stops new tracking. The statistics of this site are separate and are loaded according to the choice made in the privacy preferences.
Export and deletion
From the console you can export the data available in the account archive, including contacts, campaigns, sending logs, audit and subscription information.
You can request deletion of the account from the console, with a 30-day cooling-off period or by choosing to start the procedure immediately. The removal of operational data, the expiry of backups and the retention of logs and data subject to legal obligations follow the times and conditions described in the Privacy Policy.
Where to read the details
For full information see the Privacy Policy, DPA, Subprocessors and Terms of Service. For questions use the Contact page.