For security and IT teams
Security
How The VIM Readiness Assessment and its client workspace protect your organization's information. Written for the people who review a service before their organization uses it.
Last reviewed November 1, 2026.
Where your information is kept
The site runs on Vercel. Assessments and the client workspace's records are kept in a Neon Postgres database, and files your team adds are kept in Vercel's private file storage, which is reached only through the site after its own access checks. The site's servers, its database and its file storage are all in the eastern United States.
Email goes out through Resend, payments are taken by Stripe, the bot check on our forms is Cloudflare Turnstile, and the AI features use Anthropic. Card details go straight to Stripe and never reach us.
Encryption
Every connection to the site uses HTTPS, and browsers are told to use nothing else. The site's own connection to its database is encrypted and checks the database's certificate.
The database, the file storage and our backups are encrypted at rest by our providers (AES-256).
Signing in
Staff and members of a client workspace sign in with a link sent to their email. Each link works once and expires after 15 minutes, so there is no password to steal or reuse.
A signed in session is kept on our servers. Its cookie is replaced every 15 minutes while it is used, and a replaced cookie that is used again ends the session for everyone holding it. A session ends after a few hours without use and after seven days at most, and signing out ends it on our servers, not only in the browser. Staff access is limited to a named list that is checked on every request.
Who can see what
Each client workspace is kept apart: every read and every change is checked against the person's role and their own organization, and refused otherwise. Each role sees only what it needs, and every action in the workspace is kept in an audit trail.
Reports are reached through long random addresses. Our public verification page shows only an issued report's organization, band, date and document code, and limits how many lookups one address can make.
Protecting the site
The forms that start work or send email are protected by a bot check and by limits on how often one address can use them. Database queries never mix in what a visitor typed, and the pages escape everything they display.
Prices are set on our server, never by the browser, and a payment is confirmed only when Stripe's signed notice matches the price. Files are checked by type and content before they are stored. Security headers stop the site from being shown inside other sites or loading scripts from anywhere but itself and Cloudflare's bot check.
Testing and review
Every change runs automated checks before it can go live: type checks, unit tests, tests in a real browser, and a scan for known weaknesses in the software the site is built on.
On November 1, 2026 we reviewed the whole system against 13 areas of production readiness, from sign in and access control to backups and incident response, and fixed what the review found.
Monitoring, backups and recovery
An outside service checks the site's health every five minutes. Every failure that matters is recorded, and staff are emailed about anything that needs attention.
The database is copied every day and each copy is kept for 30 days, in addition to our provider's own recovery. The restore is tested automatically on every change.
If something goes wrong
We keep a written incident response plan. If an incident affects your organization's information, we will tell you without undue delay what happened, what it means for you and what we are doing about it.
Report a security issue
If you believe you have found a weakness in this site, please tell us with the form below. Please do not look at or change other people's information, and do not disrupt the service, while you look. We aim to reply within three business days to every report that gives a way to reach you.
