Draft, not yet in force. Three things are still to be filled in before this page binds anyone: the operating entity and its registered address, the contact address for questions and requests, and the governing law. Each is marked like this below.
Security and retention
Last updated 21 September 2026. How the service itself is built, since we are asking you to trust us with read access to your code. Claims here are ones you could verify by asking.
How your account is protected
- Passwords are stored as PBKDF2-SHA256 derivations with 100,000 iterations and a per-user random salt. We never see, store or email a password, and we cannot recover one for you.
- Session tokens are stored as SHA-256 hashes. A copy of our database does not let anyone replay a live session, because what is stored cannot be presented as a token.
- Sessions last twelve hours. Deactivating someone revokes every session they hold immediately, not at the next expiry.
- Invitations expire after seven days and password resets after one hour. Each is single use: consuming it destroys it.
- Repeated failed sign-ins lock the account temporarily. The response to an unknown address and to a wrong password is identical, so the form cannot be used to discover who has an account.
How one customer is kept out of another's data
Every query that touches customer data takes an organisation identifier, and the helper that applies it refuses to run when that identifier is missing or empty rather than falling back to returning everything. An empty scope denies; it never widens. This is structural: there is no code path where forgetting the scope silently returns another customer's rows.
What runs your code, and when
- A scan never executes anything. It clones the repository read-only, with any credential prompt disabled, and reads the files.
- A verification run executes your test suite, and only that. It requires an explicit flag the operator must pass, a disposable container, and your written request. It is bounded in memory and in time.
- Neither ever touches a production system of yours, and we never ask for production credentials.
What is kept, and for how long
| Data | Where | Retention |
|---|---|---|
| Report requests from the public form | Cloudflare KV | 365 days, expired by the store itself rather than by a job we could forget to run |
| Accounts, engagements, reports, findings, invoices | Cloudflare D1 | Life of the account; invoices longer where tax law requires |
| Audit records | Cloudflare D1, append only | Life of the account |
| Session records | Cloudflare D1, hashed | 12 hours |
| Your repository checkout | Temporary disk on the runner | Discarded when the run ends |
| Rate-limit counters | Cloudflare KV, salted hash of the IP | 1 hour |
Backups
Backups are taken as a structured export of the database. Two things are deliberately left out of every backup: password derivations are redacted, and live sessions are skipped entirely. A restored copy therefore cannot be used to sign in as anyone - everyone sets a password again. A restore refuses a backup whose row counts do not match its own manifest rather than applying half of it.
How the site is served
Everything is served over HTTPS with HSTS. The content security policy allows scripts only from this origin and from Cloudflare Turnstile, and forbids framing entirely. No page assigns HTML from a value that came from a server response; every element is constructed as a node, so a value can never become markup.
What we do not claim
- We hold no certification. There is no SOC 2 report and no ISO 27001 certificate, and we will not imply otherwise to win work.
- The static report proves the presence of the patterns it finds, never the absence of others.
- Dependency vulnerabilities are not looked up as part of a scan; that needs a network call to a vulnerability database and is outside this pass.
Telling us about a problem
If you find a weakness in this service, write to [contact address, to be set]. We will confirm receipt within two working days and tell you what we intend to do. We will not threaten you, and we will credit you if you want the credit.