Encrypted at rest
Provider credentials are encrypted with AES-256-GCM and never returned by the API.
Security
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.
Provider credentials are encrypted with AES-256-GCM and never returned by the API.
API keys with the narrowest permission each integration needs, and test keys that never deliver.
Self-host on your Cloudflare account or server, and provider keys, mail, files and logs never leave it.
ONESEND_SECRET.ONESEND_SECRET_PREVIOUS for one restart; stored credentials and signing secrets are re-encrypted at startup. See Rotating the secret.*_FILE secret files or a platform secret store. A secret placed in the config file stops the server at startup.ONESEND_SECRET, and internal error messages are not returned to API clients.os_test_) never deliver email.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.
Report vulnerabilities privately, not in a public issue or pull request.
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.