Trust

Security

Last updated 23 August 2026. Prepared for counsel review — not legal advice.

Security is an architectural requirement, not a later add-on. The practices below are what the product actually does. We maintain SOC 2-aligned practices with documented controls and audit readiness. We are not SOC 2 certified. We do not claim guaranteed security, full compliance, or that the system is unhackable.

Isolation

Every resource belongs to a project under an organization. API keys and dashboard sessions resolve that project; queries are scoped to it. Sending-access keys can send and read their project; they cannot mint keys or manage domains.

Authentication

Encryption

TLS in transit at the edge. DKIM private keys and connected-account OAuth tokens are encrypted at rest with AES-256-GCM when the instance key is set. Password hashes are scrypt. Email bodies in Postgres are not field-encrypted.

Sending controls

Abuse

Signup, login, and password-reset are rate-limited per IP and per email. Plan send caps are hard stops. Shared inbox domains have a platform kill switch. We do not currently publish a bug-bounty program.

Operations

Process liveness is GET /livez. Readiness (Postgres + Redis) is GET /readyz, also summarized on Status. Application mail is sent from a mail server we operate, not a third-party reseller.

Report a vulnerability

Email hello@usermails.com with enough detail to reproduce. Do not test against customer data or send live mail to third parties as a proof.