Security

Dokaz is a backup-verification service: customers trust it to tell the truth about whether their data can be restored, and to produce evidence that holds up under scrutiny. We treat the integrity and confidentiality of that process as the core of the product.

How drills are isolated

Each drill of your backup runs in a single-use sandbox on its own private network, separate from the Dokaz application and database. The sandbox receives a short-lived link to that one backup file — never your database credentials — restores it into a throwaway Postgres server, runs your assertions, and is destroyed when the drill finishes. Dokaz never connects to your production database.

Encryption and evidence integrity

Traffic is served over TLS with HSTS enforced. Evidence is sealed at rest, and every signed report carries an ed25519 signature you can verify offline with the open-source dokaz-verify tool — so you can confirm a report is authentic without trusting us.

Data minimisation

We pull backup bytes only transiently, for the duration of a drill. Schema snapshots record structure — names, types, counts — never your row data. Customers who enrol a customer-cloud runner keep the backup bytes inside their own network entirely; only the signed verdict returns to Dokaz.

Reporting a vulnerability

Email security@dokaz.net with a description, reproduction steps, and how you would like to be credited. Please do not open a public issue or disclose the problem publicly before we have had a chance to fix it.

For good-faith reports we aim to acknowledge within 24 hours, triage within 72 hours, and share a fix plan within 7 days. We offer safe harbour for research that follows this policy: only access data that is yours, do not degrade the service for others, and give us reasonable time to fix an issue before disclosing it.

Security questions: security@dokaz.net.