Assurance
How safe are we to work with?
We list every control, say whether it is really in place, and name the ones we have not done. No outside firm has audited us yet, and we will not pretend one has.
9 of 14 controls are in place. No outside firm has audited us yet, so we do not claim it.
9
In place
2
Being built
3
Not started
Measured speed, last 24 hours
These are real timings from real requests. p95 means: 95 out of every 100 requests were at least this fast.
Reading the timings…
Keeping people out
- Only the right people see the dataIn place
Each account has a role, and the database checks that role on every single read.
How you can tell: Row-level rules on every table, plus a private role check function.
- Keys are never in the pageIn place
Secret keys live on the server only. The browser never sees them.
How you can tell: Server-only modules and a build check that blocks secrets in browser code.
- We scan our own codeIn place
A scanner looks for weak spots and we fix what it finds before we publish.
How you can tell: Pre-publish gate: the build stops when a critical problem is open.
- An outside firm attacks us on purposeNot started
A hired team tries to break in, and we fix whatever they find.
- An SOC 2 report signed by an auditorNot started
An accountancy firm watches us for months and then signs a report.
Staying switched on
- Public speed and health numbersIn place
We time every live request and publish the real numbers, not a promise.
How you can tell: /status and /assurance show measured p95 times from the last day.
- Nothing is silently lostIn place
Work that fails is retried, and anything still failing is parked where a person sees it.
How you can tell: Durable job queue with a dead-letter list and a health panel.
- Daily backups we have restoredBeing built
The database is copied every day, and we practise putting a copy back.
How you can tell: Managed daily backups run. A written restore drill is not finished yet.
Keeping secrets secret
- We list the firms that help usIn place
Anybody can see which outside firms touch data for us, and what they do.
How you can tell: Public sub-processor list in our legal pages.
Getting the numbers right
- Every cent has a written trailIn place
Money in, fees, tax and money out are all written down and must add up.
How you can tell: Double-entry ledger, plus a nightly check that the books balance.
- Fake traffic is blockedIn place
Clicks are signed, and odd patterns are quarantined before anybody is paid.
How you can tell: Signed click links, loop detection and a 14-day hold before payouts.
- Counting checked by the MRCNot started
An industry body checks that we count views and clicks the agreed way.
Respecting people's choices
- We ask before we measureIn place
We read the visitor's privacy choice and stop measuring when they say no.
How you can tell: Consent signals are checked on every measurement and bid request.
- You can ask for your data or its deletionBeing built
Open your account page and press one button: download everything we hold about you, or erase yourself.
How you can tell: Both buttons work straight away. An erase is refused while money is still moving, and bills we must keep by law stay, without your name.
What we are working towards
An SOC 2 report means an accountancy firm watches how we work for months, then signs a report about it. We are getting the 14 controls above in order first. Until a signed report exists, this page says "not started".