Security & trust
Show the controls, not just the badge.
This page documents how Transmitly protects customer data, what is independently verifiable today, and which documents are available for procurement and security review.
Current certification status
SOC 2 is not yet complete
Transmitly does not currently hold a SOC 2 report. We are building a formal security program and evidence set; we will publish the scope and report when an independent audit is complete. We do not claim certification before it exists.
Controls
What is in place today
Tenant isolation
Every message, delivery, contact, suppression, webhook and inbox record is scoped to a workspace. API keys and sessions resolve to one organization.
Authentication
Scoped API keys, revocable key prefixes, hashed session tokens, role-based workspace access and SMTP AUTH with TLS.
Transport
TLS for API and website traffic, STARTTLS or implicit TLS for SMTP submission, and TLS for inbound SMTP where a certificate is available.
Email authentication
SPF and DKIM checks, per-domain DKIM signing, DMARC reporting and BIMI validation in the deliverability audit.
Data handling
Postgres stores control-plane metadata and hot content. Attachments, compose assets and cold message bodies live in encrypted object storage.
Retention
Plan-based content retention, cold-body expiry, partition drops and bounded operational retention for logs, events and audit rows.
Recovery
Object-storage backups with provider-side encryption, continuous WAL archiving and point-in-time recovery with tested restores.
Change and audit
Database migrations, signed webhook events, audit logs for sensitive workspace actions, and explicit approval gates for high-risk automation.
Abuse controls
Per-tenant quotas, rate limits, suppression enforcement, sender-domain ownership checks and an authenticated, non-open SMTP submission path.
Documents
Procurement and legal pack
Data Processing Addendum
Controller-to-processor terms, security commitments, subprocessors and deletion.
SCC Addendum
EU Standard Contractual Clauses and UK Addendum incorporation for restricted transfers.
Subprocessors
Current infrastructure, storage, payments and model providers with purposes and locations.
security.txt
Machine-readable security contact, disclosure policy and expiry.
Data handling
Customer content is processed to provide the service. Message bodies follow plan retention; attachments and cold bodies live in object storage; backups are encrypted and retained separately. Read the privacy policy and DPA.
Incidents and status
Service health is public on the status page. Security reports go to [email protected]. Customers with a contract can request incident updates through their security contact.
Vulnerability disclosure
We welcome good-faith reports about the security of transmitly.io, the API and the sending path. Do not access customer data, degrade service, or test against third-party mailboxes. Include reproduction steps, affected URLs or endpoints, and any relevant request/response details.
Contact [email protected]. The machine-readable policy is at /.well-known/security.txt. We will acknowledge reports and coordinate disclosure; this page does not create a legal safe-harbor commitment.
Security review requests
For security questionnaires, architecture questions, DPA execution or SCC annex completion, contact [email protected] or [email protected]. We will provide the current documents and answer scope questions directly.