How to read this list
Each sub-processor is here because it is required to deliver some part of the Mailapp Services. We require contractual commitments equivalent to the EU SCCs, and we routinely audit security posture.
- Sub-processors are categorised by function so you can quickly see who touches which part of the pipeline.
- The Region column reflects where the sub-processor processes data for Mailapp. EU residency customers stay in EU-region instances where applicable.
- The Certifications column lists what we've verified during vendor due diligence — not all of a vendor's capabilities.
- Subscribe to changes by RSS (/landing/subprocessors.rss) or by emailing hello@mailapp.app.
Primary infrastructure
Core hosting, CDN, and security. Every workspace touches these.
Email and notification delivery
The actual sending. Amazon SES is our primary mail transport for every outbound email. Additional providers cover SMS and push.
Amazon SES processes the recipient address, the email envelope, and the rendered message body for the time required to relay the message and to record delivery, bounce, and complaint status. Mailapp consumes those signals via AWS SNS webhooks, writes them to its own delivery log, and applies them to the global suppression list (see Anti-Spam Policy § 5). The relationship is governed by the AWS Customer Agreement, the AWS GDPR Data Processing Addendum, and the AWS Service Terms for SES.
AI providers
Where prompts and completions for AI features are processed. None of them train on your data.
Operational tooling
Monitoring, error tracking, security analytics. These see metadata; many see no customer personal data at all.
Marketing, billing, and support
Sub-processors that touch billing contacts, prospects, or support conversations — not the data your end-recipients see.
Notifications and objections
Subscribe to changes. If you object, you can terminate the affected service for a refund.
- Subscribe by RSS (/landing/subprocessors.rss) or by emailing hello@mailapp.app.
- Notice period for material changes: 30 days.
- Objection: reply to the notification email within the notice period. We'll work in good faith to address it; if we can't, you may terminate the affected service for a prorated refund of unused prepaid Fees.
- Emergency replacement of a sub-processor (e.g., a vendor goes bankrupt, an incident requires immediate failover) may shorten the notice period; we'll explain the circumstances and replacement choice as quickly as we can.
Change history
An auditable log of additions and removals from the sub-processor list.