Security
The Venue Record holds safety records for buildings: procedures, certificates, check logs and the names of the people who read them. Here is what keeps them safe, in plain words. If you think you have found a weakness, email [security contact email] and we will reply within two working days.
Your records are walled off from everyone else's
Every table in the database checks, row by row, that the person asking belongs to the organisation that owns the record. That check is in the database itself, not only in the app, and it is tested automatically every time the code changes: a test signs in as one organisation and tries to read, change and delete another's records, and fails the build if any of it works.
Nothing is overwritten
Confirmed documents, sign-offs, check logs, approvals and the audit log can be added to, never changed or deleted, and the database enforces it. If a procedure is updated, the old version stays with the name of the person who confirmed it. That is what makes the record worth showing to an inspector, and it means a mistake or a bad actor can't quietly rewrite history.
No passwords to steal
You sign in with a link or a code sent to your email; there is no password to reuse, guess or leak. The people you send a procedure to need no account at all: each gets a private link that works for one person and one version, expires, and is stored only as a one-way fingerprint, so even we can't read it back. Contractor upload links can be withdrawn at any time.
We watch for trouble
- Links that don't exist being tried, and too many tries from one place, are blocked and recorded.
- Sign-in emails are limited per connection and per address.
- Every day the service checks for patterns that suggest someone is probing or taking data out, such as bursts of downloads or share links, and alerts us.
- When someone new is given access to your organisation, its owners are emailed. If you didn't expect it, you'll know the same day.
- Errors are reported to us automatically, with private links and personal details removed before they leave the service.
Where it lives
Records are held by Supabase in a data centre in the [Supabase region], encrypted in transit and at rest. The app runs on Vercel. Emails are sent by Postmark. AI features (reading a certificate, drafting a procedure) use Anthropic's API, which does not train on what we send it. The full list of the companies we use and what each handles is in the privacy policy.
You can take it all with you
You can download everything for a building as one evidence pack at any time, and it stays readable if you stop paying. The record is yours.
What we ask of you
Keep your email account secure, because that is the key to your sign-in: turn on two-factor authentication with your email provider. Remove people from your organisation when they leave. And withdraw a share link once it has done its job.