Skip to content

Security

What protects an approval made in DueReason, from the moment it's requested to the record that proves it happened. Every claim on this page is a control that ships in the product today, not a policy promise.

How approvals are protected

Grants bound to the payload
An approval issues a grant naming the action, the approver and the hash of the exact payload approved. It's signed with Ed25519, expires, and can only be used once. The system carrying out the action verifies the signature itself, against a public key published per organization -- no call back to DueReason is needed to trust it.
Append-only and hash-chained
Every decision is written to an append-only ledger where each entry carries the hash of the one before it, so changing history breaks the chain. A scheduled job re-verifies the chain on its own and raises an alert the moment it doesn't match.
Receipts anyone can verify
Each decision gets a signed receipt, publicly checkable at /verify. Receipt-signing keys keep a published history, so a receipt signed by a key since rotated out still verifies.

Accounts and API access

Two-factor login
Two-factor login is available to every account, and an organization can require it for all of its members.
Protected sign-in
Sign in with a password or with Google. Sign-up, sign-in and password reset are checked by Cloudflare Turnstile, a privacy-preserving, cookieless bot check.
Scoped API keys
An API key is scoped to only the actions it needs and can carry an expiry date you choose when you create it.
Secrets at rest
Webhook signing secrets and the Slack or Teams webhook URLs you connect are encrypted at rest; we cannot read them back in plain text.

Evidence and data handling

Evidence is scanned before it's stored
Every uploaded evidence file is scanned for malware before it's stored. If the scanner doesn't answer in time, the upload is rejected -- it never gets waved through.
Evidence hashed on the ledger
The sha256 hash of each evidence file is written to the ledger alongside the decision, so a stored file can always be checked against what was actually approved.
Notifications carry no payload by default
Slack, Teams, email and push notifications carry no payload, reasons or evidence unless an organization admin opts a channel into showing them. A link in a notification never approves or rejects anything by itself -- it opens a page you have to sign in to and submit.
A locked-down public site
Every page is served with a nonce-based Content-Security-Policy. The only analytics on our public pages is cookieless (Umami) -- no third-party trackers, no advertising pixels.

Where data lives

DueReason runs on servers in Germany (Contabo), including the hourly backups and the point-in-time database archive. Evidence files, and an encrypted copy of the database backups, also go to Backblaze in the Netherlands (Amsterdam). You can export your organization's data or your own account's data at any time, delete an organization outright, and set retention periods that purge evidence automatically. The full list of who processes data, where and under what safeguard is on the subprocessors page.

Read the subprocessors page

Self-hosting

Prefer to run DueReason yourself? It's also available self-hosted, licensed with an offline-verified key -- no phone-home, ever.

Read the self-hosting guide

Reporting a vulnerability

Found a security problem in DueReason? We want to hear about it before anyone else does.

Read our security.txt