Security architecture

Protection in layers.
Clarity at every step.

Security is a chain of boundaries across transport, identity, sessions, recovery, application secrets, and mailbox operations.

Defense model

No single control carries the whole security claim.

Protect the connection

HTTPS and supported mail protocols use authenticated TLS. Certificate verification remains enabled in runtime code.

transport

Protect the account

Passwords, MFA readiness, passkeys, bounded recovery, CSRF, and session rotation answer different threats.

identity

Minimize stored secrets

Reset tokens and backup codes are stored as hashes. Recoverable secrets require authenticated encryption.

data

Account defense

Strong sign-in without a fragile recovery shortcut.

Each layer answers a different risk: passwords establish a secret, authenticators add proof, passkeys resist phishing, and recovery methods must be verified before use.

PasskeysAuthenticatorHashed backup codesRevocable sessions

ACCOUNT / SECURITY STATE

Layered protectionControls remain independently inspectable

READY

Primary sign-inprotected
Recovery methodsverified only
Active sessionsrevocable
Security activityauditable

Control matrix

A technical view of the trust boundaries.

Protection is attached to a specific asset, mechanism, and visible outcome.

BoundaryPrimary controlVisible resultScope

TransportAuthenticated TLSConnection statusnetwork

SessionRotation + CSRFRevocable devicesapplication

RecoveryExpiring hashed tokensVerified methodsidentity

SecretsHash or authenticated encryptionNo raw token storagedata

MailboxProvider capability stateApplied / pending / failedservice

Honest boundaries

Encryption is not one switch.

Transport, stored application secrets, mailbox storage, and end-to-end message encryption are separate layers. Claims must match the deployed architecture.

NETWORK

In transit

TLS protects supported network connections against passive interception.

STORAGE

At rest

Protection depends on database, application encryption, and mail-server deployment.

CONTENT

Message content

End-to-end encryption is claimed only where sender and recipient cryptography is implemented.

Database-backed plans

Choose limits with the same level of clarity.

Each active public plan is joined to one current price while earlier Stripe Price mappings remain in history.

View pricing