Trust at MailInApp

Everything a security or procurement review usually asks for, in one place. That includes what we don't have yet, so you don't have to ask.

Last updated: November 14, 2026

Uptime, last 90 days: 98.57%

All systems operational

  • 2026-11-14: 100%
  • 2026-11-15: 99.30%
  • 2026-11-16: 91.66%
  • 2026-11-17: 99.30%
  • 2026-11-18: 100%
  • 2026-11-19: 99.65%
  • 2026-11-20: 99.65%
  • 2026-11-21: 99.65%
  • 2026-11-22: 100%

Checked from outside the app every 5 minutes. How we measure it.

What we have, and what we don't have yet

ItemStatus
Data Processing AgreementYes. Part of our Terms for every customer, no signature needed. Read it or download the PDF.
Standard Contractual Clauses (EU, UK, Switzerland)Yes. Included in the DPA by reference. The text is available on request.
Sub-processor listYes. A dated, public list.
Public status page and uptime historyYes. Live status and 90-day uptime.
Two-factor sign-inYes. An authenticator app, with backup codes.
SOC 2 reportNo. We're not certified and haven't started an audit. See our SOC 2 plans.
ISO 27001 certificateNo. We don't plan to pursue it before SOC 2.
Independent penetration testNot yet. The test is scoped. We'll publish a summary here when it's done.
Uptime commitment (SLA)Not by default. Our Terms don't include one. Enterprise customers can agree one in writing.
Choice of data regionNo. Your data is stored in the United States.

SOC 2

MailInApp is not SOC 2 certified, and no audit has started. We would rather say that plainly than leave you guessing.

Our roadmap:

  1. Now. We publish the documents a security review usually asks for: the DPA, the sub-processor list, the security measures below and our incident process. We also answer security questionnaires. Write to [email protected].
  2. Next. We'll do readiness work for a SOC 2 Type I report, then hire an independent auditor.
  3. After that. We'll get a SOC 2 Type II report, which covers how our controls work over several months.

We'll update this page with dates once an auditor is engaged. If your procurement needs a SOC 2 report by a specific date, tell us. Customer need decides when we start.

How we protect your data

  • Encryption. Data is encrypted in transit (TLS) and at rest by our cloud providers.
  • Credentials. We store API keys and connector tokens hashed. Passwords for your SMTP relay and connected mailboxes, and webhook secrets, are encrypted and masked after you enter them. We show a key or secret only once.
  • Payments. Card details go straight to Stripe (or PayPal or Shopify). We never receive or store a card number.
  • Signed links. Links in your emails carry short-lived, signed tokens, so a reader's identity is never written in plain text in a URL.
  • Your account. Two-factor sign-in, a sign-in history, and a log of changes made in your account, showing who made each one.
  • Our staff. Every action our staff take on a customer account, and every time staff open a contact's personal data, is written to an audit log.
  • Abuse protection. Every public endpoint is rate limited.
  • Dependencies. Each release must pass an automated audit of the software we depend on.

The Privacy Policy (section 10) is the full statement of these measures.

Where your data lives

Your account data, emails and contacts are stored with Google Cloud in the United States. Email is sent and received through Amazon Web Services, also in the United States. Cloudflare serves our websites and some email images from its global network. The sub-processor list names every provider and what it handles. We add a dated entry there before we start using a new one.

If something goes wrong

Our incident process has five steps:

  1. Detect. Our monitors check the app every 5 minutes and alert us to errors. Anyone can also report a security issue.
  2. Contain. We stop the problem first. We revoke or rotate any credential that might be exposed, and work with you to rotate your own SMTP or mailbox passwords when needed.
  3. Investigate. We keep logs and records as evidence, then find out what was exposed and which accounts it affected.
  4. Tell you. If an incident affects your data, we tell you without undue delay, as the DPA requires. We share what we know at that point and send updates as we learn more. We don't promise a fixed number of hours yet.
  5. Close and learn. We close an incident only when its cause is fixed and documented. Each one ends with a review of what we change so it doesn't happen again.

Outages and slowdowns show on the status page.

Contact