This page describes the security posture of trustyourinbox. We lean on hardened, independently audited vendors, encrypt sensitive data at rest and in transit, and keep the attack surface small. We update this page as the posture matures.
- At rest: customer data is stored in Neon Postgres (AES-256 at rest by Neon's default) and Cloudflare R2 (AES-256 by Cloudflare's default). Application secrets (API keys, signing tokens) are stored as Cloudflare Worker secrets, encrypted and only injected into the Worker runtime at request time.
- In transit: TLS 1.2+ everywhere. Cloudflare's edge handles TLS termination for the public site and dashboard. All vendor APIs we call (Anthropic, Resend, Clerk, Neon, Stripe) require TLS.
- End-user authentication: handled by Clerk (industry-standard provider, SOC 2 Type II compliant). You sign in with a password, an emailed code, or Google or GitHub; when Clerk sees a new device it asks for an emailed code before the session starts. Passwords are bcrypt-hashed; sessions are JWT short-lived.
- Multi-tenant isolation: every query in the dashboard is scoped to the requesting user's
workspace_id. There is no cross-tenant data access path. This is enforced at the query layer, not just the route layer. - Production access: direct access to production infrastructure is restricted to authorized personnel under least-privilege. No third-party support engineers, no shared accounts. Credentials are rotated on any suspected compromise.
We use these vendors. Each has its own published security posture:
- Cloudflare: hosting, Workers, R2, DNS, Email Routing. Cloudflare's compliance documentation (SOC 2 Type II, ISO 27001, ISO 27701, PCI DSS, FedRAMP, GDPR).
- Neon: Postgres database hosting. SOC 2 Type II.
- Clerk: authentication. SOC 2 Type II, GDPR + CCPA compliant.
- Anthropic: Claude API for the in-app help assistant and the acceptable-use check on newly added domains. SOC 2 Type II. We operate under a Zero Data Retention (ZDR) agreement: our API inputs and outputs are not logged or stored on Anthropic's side, and are never used for training.
- Resend: outbound transactional email.
- Stripe: payment processing. PCI DSS Level 1. We do not handle card details ourselves; Stripe Checkout handles them.
See our Privacy Policy for what we collect and how long we keep it. The headline numbers: account data while active, with backups aging out 7 days after deletion; support tickets up to 24 months after they close; parsed DMARC reports 14 months; raw DMARC and TLS reports kept in R2 with no set deletion date; forwarded bounces for Delivery Diagnosis deleted once analyzed, 7 days at most.
Our Postgres database is backed up by Neon's standard snapshot policy. Formal Recovery Time and Recovery Point Objectives (RTO / RPO) are on our roadmap.
If we discover a security incident affecting customer data, we will:
- Contain the incident immediately and revoke compromised credentials.
- Notify affected customers via email within 72 hours of discovery, or sooner if required by applicable law.
- Publish a post-incident summary on this page describing what happened, what was affected, and what we changed to prevent recurrence.
- Cooperate with any required regulatory or law enforcement reporting.
Email security@trustyourinbox.com. Include:
- A description of the issue and steps to reproduce it.
- Any relevant URLs / API calls / screenshots.
- Your name (so we can credit you, if you'd like).
We run a responsible-disclosure program with discretionary cash rewards, safe harbor for good-faith research, and public credit if you want it. The full scope, rules, and what to expect are on our Bug Bounty page. We respond within 2 business days, and we won't pursue legal action against good-faith researchers who follow the policy.
Test only on an account you sign up for yourself. We do not provide test accounts, credentials, plan upgrades, trial extensions or seeded data for research, and paid-plan features are in scope only on a plan you pay for. An email asking for an account gets no account.
- SOC 2 / ISO 27001: not yet certified. We follow SOC-2-aligned practices (least-privilege access, vendor compliance review, encryption at rest and in transit, audit log of all data-modifying actions). Formal certification is on our roadmap.
- GDPR / UK GDPR: we comply with the rights described in our Privacy Policy. Our Data Processing Agreement applies to every customer automatically (no signature required), with Standard Contractual Clauses for international transfers, and we publish our subprocessor list.
- HIPAA: not in scope. Don't use trustyourinbox to monitor domains that send PHI in DMARC report metadata (DMARC aggregate reports don't contain message content, but if your sending domain is itself subject to HIPAA, you should run your own diligence on whether the metadata flow meets your obligations).
- PCI DSS: out of scope (we never handle card data).
See also Privacy Policy · Terms of Service · Acceptable Use Policy · Data Processing Agreement · Subprocessors.