MailKite
Get started
Legal

Privacy Policy

Your webhook is the system of record — we're the pipe. This explains what we collect, how long we keep it, and the per-domain controls you have over the email we process.

Effective date: 2026-06-27

Who we are

MailKite ("MailKite", "we", "us") provides a developer email platform: we receive inbound email for your domains and deliver it to your webhook, and we send outbound email through our API. This policy explains what we collect, why, how long we keep it, and the choices you have.

Questions or requests? Email support@mailkite.dev.

Information we collect

We collect three kinds of data:

  • Account data — your email address, password hash (or Google sign-in identifier), and the API keys and webhook signing secrets we generate for you.
  • Contacts you add — your address book: contacts you create, import (CSV/vCard), or sync from a connected provider such as Google (see "Connecting Google Contacts").
  • Email content we process — messages sent to your verified domains (sender, recipients, subject, body, headers, attachments) and messages you send through our API. How long we retain this is your choice (see "Email retention and your controls").
  • Usage and billing data — domains, message counts and metering, plan, and the Stripe customer/subscription identifiers tied to your account. Card details are handled by Stripe; we never see or store full card numbers.
  • Site and product telemetry — a session cookie to keep you signed in, and aggregate analytics about which calls-to-action are clicked. We don't run third-party advertising trackers.

How we use it

We use your data only to run the service:

  • Deliver the product — parse and route inbound mail to your webhook, send your outbound mail, and authenticate your API requests.
  • Billing — meter usage and charge your plan and any domain registrations through Stripe.
  • Support, security, and abuse prevention — diagnose delivery issues, protect the platform, and enforce our Terms (including anti-spam).
  • Service communication — operational notices about your account, billing, or incidents.

We do not sell your data, and we do not use the contents of your email to build advertising profiles.

Email retention and your controls

By default we keep a parsed copy of each message only long enough for you to replay or debug a delivery, then it auto-expires — 3 days on Free, 30 on Pro, 90 on Scale, and 365 on Business. Inbound attachments are deleted after 7 days. Your webhook is the system of record; MailKite is the pipe.

You can tighten this per domain:

  • Zero-retention passthrough — we deliver the webhook but persist nothing: no body, no attachments, no delivery record. Your webhook holds the only copy.
  • At-rest encryption — paste your own public key and we encrypt retained message bodies to it before storing them, so we cannot read them. Only you hold the private key.

See the Retention & encryption docs for how to enable each.

Connecting Google Contacts

Connecting Google is optional and entirely under your control. If you click "Sync" next to Google on your Contacts page, we ask Google for read-only access so we can build your MailKite address book. We request only these scopes:

  • https://www.googleapis.com/auth/contacts.readonly — to read your saved Google Contacts.
  • https://www.googleapis.com/auth/contacts.other.readonly — to read your Google "Other contacts" (people you have emailed but not saved), so your address book is complete.

From those contacts we import only each person's name and email address (and, when present, their company) into your own MailKite address book. We use this solely to (a) show you your contacts and (b) suggest recipients when you compose an email. We never use it for advertising, never sell or share it, and never use it to train AI/ML models. Your Google OAuth tokens are encrypted at rest (AES-GCM) and used only to sync your contacts.

You can disconnect Google at any time from your Contacts page, after which we stop syncing, and you can delete imported contacts individually or by deleting your account.

MailKite's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Subprocessors

We rely on a small set of infrastructure providers to deliver the service. Each processes data only to perform its function:

  • Cloudflare — compute, storage (D1, R2), and email send/receive infrastructure.
  • Stripe — payment processing and subscription billing.
  • Anthropic — powers optional inbox-agent and assistant features; only invoked when you use AI, and never when you bring your own key in a way that bypasses us.
  • Domain registrar(s) — when you register a domain through us, the registrant details you provide are shared with the registrar to complete registration.
  • Google — if you choose "Sign in with Google" (to authenticate you) or connect Google Contacts (to sync your address book, read-only). See "Connecting Google Contacts".

Email authentication and security

Outbound mail is signed with DKIM and aligned to SPF and DMARC on your domain using the DNS records set at onboarding, so your mail authenticates as you. Webhook deliveries are signed with HMAC-SHA256 (the x-mailkite-signature header) so you can verify they came from us. Access to the API and webhooks is over TLS.

Cookies

We use a first-party session cookie (scoped to mailkite.dev) to keep you signed in across the dashboard, docs, and site. We use minimal first-party analytics to understand which links are used. We do not use third-party advertising cookies.

Your rights

You can access, export, correct, or delete your account data. Deleting a domain removes it and its routes; deleting your account removes your account data and stops processing. Depending on where you live, you may have additional rights under laws such as the GDPR or CCPA — email support@mailkite.dev to exercise them and we'll respond within a reasonable time.

For email we process on your behalf, you are the controller and MailKite is the processor; we act on your instructions.

Data retention and location

We keep account and billing records for as long as your account is active and as required for legal, tax, and accounting purposes. Email content follows the retention rules above. Data is processed on our providers' global infrastructure; contact us about region requirements for enterprise needs.

Children

MailKite is a developer tool not directed to children, and is not intended for anyone under 16.

Changes to this policy

We may update this policy from time to time. Material changes will be announced to your account contact email. The version in effect when you use the service governs that use.

Contact

Privacy questions or requests: support@mailkite.dev.

See also our Terms of Service and SLA.