Security

What this page covers

Security is how Outdraft decides who you are, what you may do, and how mail and account data are protected while you work. It describes the product as it ships today — a collaborative mail workspace — not a compliance catalogue or a privacy-mail promise the product doesn't make.

For who an account is, see Accounts. For where auth and data live in the stack, see Stack.

• Signed-in sessions

  When you use the workspace, Outdraft resolves your account session before mail, projects, or settings actions run. Sensitive steps — including completing two-factor authentication when it’s enabled — have to clear that session path first.

• System paths

  Outbound delivery, inbound handling, and background mail jobs authenticate as system work at the API or worker edge. They are not run with your browser session. That keeps background mail moving without pretending to be a signed-in person.

• Password

  Your primary sign-in factor. Outdraft never stores or displays your password in plaintext — authentication is handled through Supabase Auth, which keeps credentials hashed.

• Backup Email

  An outside address for password and authenticator resets and important security notices. It is not your day-to-day Outdraft inbox.

• Authenticator (optional)

  You can require a time-based code from an authenticator app after the password. Until that second step succeeds, the product stays closed — even if the password alone was correct.

Two-factor authentication is opt-in. You turn it on in Settings, confirm it with a code from your authenticator app, and from then on every sign-in needs that second factor. Outdraft enrolls one authenticator at a time and does not issue printable recovery codes today — store that secret in a password manager or a second device you control so you can still sign in if you lose the first app.

Authorization after sign-in

Signing in answers who you are. What you can open or send also depends on where the mail lives and what role you hold there.

Personal, team, and organization mail stay on separate scopes. Membership and roles in organizations (and teams under them) decide who can invite, manage, or act inside those spaces. Nests use a smaller model: the owner controls the nest and who belongs; members can open mail that has been shared into it. Sharing mail into an organization, team, or nest is an authorized action that expands who may read that copy — it does not change who originally sent it.

In broad terms, owners are responsible for the space itself, managers can invite and administer within an organization, and members work inside what they’ve been granted — including whether they may send as the organization when that permission is enabled. Exact controls live in Members and Manage access in the product; this page is the trust model, not a full role matrix.

The browser does not write mail or membership rows on its own — it calls APIs that enforce session and system rules first.

• In transit

  Traffic between your browser and Outdraft, and the paths that carry mail to and from the wider network, use TLS. Connections are encrypted on the wire as a platform default.

• At rest

  Account data, messages, and files sit in managed datastore and storage that encrypt data at rest. That protection comes from the infrastructure Outdraft runs on — not from a separate end-to-end mail cipher in the app.

• In the product UI

  Mail HTML is sanitized before it is rendered, so messages can’t freely execute script in the workspace. That is content safety in the client, not a substitute for encryption.

Outdraft is not end-to-end encrypted mail. The service must process messages to deliver them, store them in your workspace, and support shared inboxes, search, nests, and organization workflows. If you need a product where the operator cannot process message content at all, that is a different class of mail.

What you control

Use a strong unique password and keep your Backup Email current so recovery stays possible. We recommend turning on two-factor authentication for accounts that hold mail you care about. If you enable it, treat the authenticator app like a key — and prefer a backup factor on another device or vault when you can.

Profile, password, Backup Email, two-factor authentication, and account status live in Settings. Organization membership and roles are managed inside Projects for spaces you own or join. Nest membership is managed on the nest itself.

Operating the service

Running Outdraft means trusted operators and infrastructure providers can access systems required to keep the product available, deliver mail, and fix failures — under the same duty to protect customer data. That is shared responsibility for a hosted workspace, not a claim that nobody can ever touch production systems.

If you believe you've found a security issue, contact us through Contact.

• Getting startedSign in, find the workspace, and know where mail, projects, and settings live.