Security

How your keys and data are protected

OneSend holds API keys for your sending providers and, when you self-host the workspace, your team's mail, calendars and files. This page explains how they are stored, who can read them, and how to report a problem.

Encrypted at rest

Provider credentials are encrypted with AES-256-GCM and never returned by the API.

Scoped keys

API keys with the narrowest permission each integration needs, and test keys that never deliver.

Your own infrastructure

Self-host on your Cloudflare account or server, and provider keys, mail, files and logs never leave it.

How provider keys are stored

  • Provider API keys, SMTP passwords and DNS host tokens are encrypted at rest with AES-256-GCM, with the server secret ONESEND_SECRET.
  • The API never returns a stored credential. After you save a key, the dashboard shows only that one is set.
  • The secret can be rotated: set the new value and keep the old one in ONESEND_SECRET_PREVIOUS for one restart; stored credentials and signing secrets are re-encrypted at startup. See Rotating the secret.
  • A database backup cannot decrypt provider keys without the secret, so back up the two separately and keep the secret in a secret store.

Secrets stay out of code and files

  • The database URL, the server secret and other secrets are read only from environment variables, *_FILE secret files or a platform secret store. A secret placed in the config file stops the server at startup.
  • In production the server refuses to start without ONESEND_SECRET, and internal error messages are not returned to API clients.
  • Logs redact credentials, including at debug level.

Access control

  • API keys have scopes: Full access, Sending only, Read only and Admin. Test keys (os_test_) never deliver email.
  • Workspace roles with a permission matrix, two-factor authentication, session management and an audit log. See Team and account security.
  • Mail apps sign in with per-device app passwords. The account password is never accepted over IMAP, POP3 or SMTP.
  • Webhooks are signed with HMAC-SHA256, and each endpoint has its own secret that can be rotated. See verifying signatures.

Mailbox, calendar and Drive access

  • Each mailbox is shared with the whole workspace, with chosen members, or personal. A personal mailbox is read only by its owner: admins can change its settings or delete it, and cannot read its mail. Access is checked on the server, not only hidden in the dashboard.
  • Calendars and drives use the same access model. Personal mail and personal calendars are left out of the workspace data export.
  • A calendar subscription link is secret and read-only, and only a hash of it is stored. It stops working when the member who made it can no longer read the calendar or leaves the workspace.
  • Stored mail can be encrypted at rest with a key per workspace. See Mail encryption.

Spam filter

  • The filter runs inside your installation, or on the Mac in OneSend for Mac. No message, address or score is sent to an outside service for checking.
  • It learns from Report spam and Not spam in each mailbox. The model keeps keyed hashes of words with their counts, never the words, so a database copy cannot be matched against a word list without the server secret. Its size is capped.
  • The model is workspace data: it is exported and deleted with the workspace.
  • Files are shared with members as viewer or editor. A public link exists only when someone makes one, and it can be revoked at any time.
  • A public link can have a password, stored as a scrypt hash, and an expiry date.
  • The server looks a link up by a hash of its token. The token itself is stored encrypted, so the people who manage the link can copy it again.
  • Wrong passwords lock a link: 10 from one address in 15 minutes lock that address out, and 100 in a row from anywhere lock the link for everyone, for one minute at first and up to an hour.

Booking pages

  • A booking page shows open times only, never the events in your calendars.
  • The visitor's address is kept as a keyed hash for abuse limits, never as the address itself, and each workspace sends a capped number of booking emails a day.

Network safeguards

  • Webhook, attachment and provider URLs that point to private, loopback or link-local addresses are blocked by default to prevent server-side request forgery.
  • SMTP ingress supports STARTTLS. The hardening checklist covers TLS, proxies, sign-up settings and key scopes for self-hosted installs.

Hosted cloud

The hosted cloud (waitlist open) runs the same code as the self-hosted version. Its hosting, backups and data processing terms are published before it opens.

Reporting a vulnerability

Report vulnerabilities privately, not in a public issue or pull request.

  • Email: security@onesend.email (placeholder: not monitored yet; a monitored address will be published here before launch).

Include the affected component and version, a description of the impact, and steps to reproduce. Do not include real customer data or live credentials. Response times, supported versions and scope are in the security policy.

We will not take legal action against good-faith research that follows the policy, avoids privacy violations and service disruption, and does not access or change other users' data.