Security

Security is built into every layer — because we read private messages.

Zero message retention

Your message content is analyzed in memory in the moment and is never written to our database, disk, cache, or logs. Only encrypted, auto-expiring triage results (urgency, category, summary) are retained — and no human, including our staff, can read them.

Encryption

In transit: HTTPS/TLS everywhere, HSTS in production.
At rest: sensitive values are protected with AES-256-GCM envelope encryption; key material is managed in a dedicated key vault, separate from the database.
Passwords: stored as Argon2id hashes — never in plaintext.

Access & account protection

Optional two-factor authentication (TOTP) with one-time recovery codes.
Short-lived, single-active sessions with idle and absolute timeouts.
Login rate-limiting and throttling to resist brute-force attempts.
Strict per-user isolation — no user can access another user’s data.

Application hardening

Strict Content-Security-Policy with no untrusted third-party scripts.
Secure headers (X-Content-Type-Options, X-Frame-Options, Referrer-Policy, Permissions-Policy).
Bot, scanner, and abuse detection with automatic and manual IP blocking.
Audit logging of sensitive actions and structured error logging.
Secrets are stored outside source code and never exposed to the browser.

Responsible disclosure

Found a vulnerability? Please email support@message-triage.com. We appreciate responsible disclosure and will work with you to resolve valid issues quickly.