Trust
Security
What's in place, how we check it, and what still needs an outside review.
How it's built
- Credits are kept in a Postgres ledger in whole numbers, never decimals.
- Duplicate payment notices can't credit twice; two requests at once can't spend the same credit. Both were tested against the live database.
- Chat backups are encrypted in your browser with AES-256-GCM using a key that never leaves your device.
- Failed answers are never charged.
- The server never logs questions or documents, and can't read them: your browser encrypts them to an enclave it has verified.
- If that verification fails, nothing is sent and nothing is charged. There is no unencrypted fallback.
How it's checked
- Tests are written before the code they cover; over 100 automated tests run on every change.
- Changes that protect money or privacy get a code review before they go live.
- Live checks run against production after each deploy.
Still to come
- An independent security review before payment limits rise or anonymous credits go live. Until then, ZEC top-ups are capped at the £20 Starter pack.
- Reproducible builds of the browser code, so you can check that this site serves what it publishes.
- Published source for the parts you need to inspect.
Reporting a problem
A dedicated security contact is coming. Until then, please don't post vulnerabilities publicly; reach the team privately through the project's GitHub.