Legal

Subprocessors

Every provider MailKite engages to run the Service, what each one can see, where the data is stored, and the transfer mechanism we rely on. Incorporated into our Data Processing Addendum.

Last updated: 20 November 2026

A subprocessor is a company we engage to process personal data on our customers' behalf while providing the Service. We keep this list short on purpose: every entry is infrastructure we run on, not a data-sharing arrangement. We do not sell personal data, and none of these providers is permitted to use it for advertising.

We announce a material change to this list to the account contact email at least 14 days before it takes effect. A customer may object on reasonable data-protection grounds within that window by emailing support [at] mailkite [dot] dev.

Provider Purpose Data Location Transfer mechanism DPF
Cloudflare, Inc. Compute for the API and edges, the primary database (D1), object storage (R2), and the email sending and receiving infrastructure. All data the Service processes: email content and metadata, account records, API and webhook traffic. United States (primary database and object storage); global edge for transient processing. EU SCCs (Module 2 and Module 3) with the UK International Data Transfer Addendum. Certified: EU-U.S. DPF, UK Extension, Swiss-U.S. DPF.
Stripe, LLC Payment processing, subscription billing and invoicing. Account identifiers, billing name and address, tax IDs, and payment metadata. Card numbers are entered into Stripe's hosted fields and never reach MailKite. United States and other countries where Stripe operates. EU SCCs (Module 2 and Module 3) with the UK International Data Transfer Addendum. Certified: EU-U.S. DPF, UK Extension, Swiss-U.S. DPF.
Anthropic, PBC Powers the optional inbox-agent and assistant features. Invoked only when a customer or their agent uses an AI feature, and never as part of ordinary send or receive. The message content and instructions submitted to the AI feature, and the account context needed to answer. United States. EU SCCs (Module 2 and Module 3), UK International Data Transfer Addendum, Swiss Addendum. Not relied on: Anthropic's DPA rests on the SCCs and the UK and Swiss addenda.
Chatic Powers the optional chat assistant on mailkite.dev and the public agent endpoint. Not part of the email pipeline. Chat messages, the pages involved, and questions asked by an assistant on a visitor's behalf. No customer email. United States (runs on Cloudflare Workers AI). EU SCCs (Module 2) in our agreement with Chatic. Not relied on: SCCs only.
Google LLC Optional sign-in with Google, and optional Google Contacts sync for the address book. Sign-in identity (email address, name), and the name, email address and company of contacts the customer chooses to import. Read-only. United States and other countries where Google operates. EU SCCs (Module 2 and Module 3) with the UK International Data Transfer Addendum. Certified: EU-U.S. DPF, UK Extension, Swiss-U.S. DPF.
Domain registrars Registration of a domain a customer buys through MailKite. Not involved in sending, receiving or storage. Registrant contact details the customer provides, plus the domain name. Varies by registry and registrar. EU SCCs (Module 2) in the registrar's terms, or an equivalent adequacy basis. Depends on the registrar engaged for the TLD; SCCs apply regardless.

Where the data lands. The primary database and the object storage holding email content are in the United States. Cloudflare's edge may process a request transiently in the region it arrives in, but the stored copy does not leave the United States. We do not currently offer an EU-only deployment; if that is a hard requirement, contact us before you buy, because we would rather say no than promise residency we cannot provide.

Transfers. Where personal data moves out of the EEA, the UK or Switzerland, the transfer is governed by the EU Standard Contractual Clauses (Module 2 controller to processor, and Module 3 processor to sub-processor where we act as processor for you), together with the UK International Data Transfer Addendum. Where a provider is certified under the Data Privacy Framework, we also rely on that certification, as noted in the table. The SCCs are in force either way, so a certification lapsing does not leave a transfer without a mechanism.

Our own providers' providers. Each subprocessor may in turn use its own subprocessors under its published terms; those are listed in the policy linked from its name above, and they are covered by the same Module 3 obligations we are under.

See also our Data Processing Addendum, Privacy Policy, Security, and Terms of Service.