Security overview
Last updated
Mail Otter's design starts from one decision: every customer gets its own workspace with its own databases. Most of what follows comes from that.
1. Isolation between customers
Each brand on Mail Otter runs in its own isolated workspace, reached at its own address such as yourbrand.mailotter.io. A workspace has separate databases for profiles, events and analytics, and its own namespace for scheduled journey steps. Customer data never shares tables with another customer's, so a mistake in one workspace's query or configuration can't expose another's contacts.
2. Access
- Each workspace has its own sign-in credentials, separate from every other workspace.
- API write keys are issued per workspace and can be rotated on request.
- Mail Otter staff access production systems only to run and support the service, and only the people who need that access have it.
- Support staff access a customer's workspace only when the customer asks for help or to investigate abuse or a security issue.
3. Data in transit
The dashboards, the API and the WooCommerce plugin connect over HTTPS. Email is sent to mailbox providers over TLS wherever the receiving server supports it.
4. The WooCommerce plugin
- Events are queued on the store and sent in the background, so a slow network never holds up a page or checkout.
- Cart links in emails are cryptographically signed, so they can't be altered to load someone else's cart.
- The cookie that recognises a returning shopper is signed, so it can't be forged to impersonate another customer.
- The public subscribe endpoint is rate-limited per IP address to slow down abuse.
5. Sending safety
- Sending domains are authenticated with SPF, DKIM and DMARC during onboarding.
- Unsubscribes, hard bounces and spam complaints are suppressed automatically.
6. Backups and recovery
Workspace data is backed up regularly and backups are kept separate from the systems they protect. We test restores. When a workspace is closed, its databases are deleted within 30 days and backups age out on their normal cycle.
7. Incidents
We have a documented process for investigating and containing security incidents. If an incident affects personal data we hold for a customer, we notify that customer without undue delay and within 48 hours, as set out in our Data Processing Addendum.
8. Providers
We use a short list of established providers for hosting, email, SMS and payments. They're described on our Subprocessors page.
9. Reporting a vulnerability
If you think you've found a security problem in Mail Otter, email [email protected] with “Security” in the subject. Please give us a reasonable chance to fix it before telling anyone else, and don't access or change data that isn't yours. We'll acknowledge your report and keep you updated.
10. Security questionnaires
Customers and prospective customers can request answers to security questionnaires and a countersigned Data Processing Addendum by emailing [email protected].