Built for records that can't leak.
Rehab and behavioral health centers hold some of the most protected data in healthcare. Confirmity is built around that: every person sees only what their seat allows, every action is logged, and nothing leaves without a person deciding it should.
Viewing as Michael
VercelBAA
NeonBAA
Sample record. Seats change every few seconds.
A BAA with you, and with our vendors.
We process PHI as your business associate. That relationship is written down before any client data reaches Confirmity.
Your center
Signed before PHI
We sign a business associate agreement with your center. Until it is signed, you work in Confirmity with sample data only.
What our BAA covers →Our vendors
Hosting and database under signed BAAs
The app runs on Vercel and the database runs on Neon, both under signed BAAs.
Everyone else
No BAA, no PHI
A vendor without a BAA never receives PHI or Part 2 records. Optional tools that lack one are limited to non-PHI data in code, not just in policy.
Full subprocessor list →Everyone sees only what they need.
Access follows the seat, not the person's title. The server decides who you are and what you can see; the browser cannot ask for more.
Sample staff and roles, shown for illustration.
Sign-in
Sessions that end
Idle sessions end after 15 minutes by default, and no session lasts longer than 12 hours. Your admin can set the idle limit anywhere from 5 to 60 minutes.
Juan
AngieOne person, one seat
No shared logins
Every person signs in as themselves, so every action in the audit log points to a real name.
Sample Recovery CenterSampleTenants
Your center stays separate
Each center is its own tenant. Requests are scoped on the server, so one center can never read another's records.
Substance use records get stricter rules. So does Confirmity.
Records are marked. Part 2 records are tagged as their own data class, separate from ordinary PHI.
Consent is checked. Before a Part 2 record is shared, Confirmity looks for the client's consent that covers it.
No consent, no share. If consent is missing, the share stops and the item goes to a person on your team.
Every action, written down for good.
The audit log is append-only: entries are added and never edited or removed. Settings changes and session expiry write their audit entry in the same step as the change itself. Passwords and session tokens never go in the log.
Added, never editedStaff and agents in one logNo passwords or tokens
The crew drafts. Your people decide.
Confirmity's agents read payer rules and prepare work. They cannot finish the job alone.
Can't send
Nothing goes outside on its own
Agents cannot send a claim, an email or a record outside Confirmity. A person on your team approves anything that leaves.
Can't sign
No signatures, no attestations
Agents cannot sign, attest or submit on behalf of a clinician or your center.
Always on the record
Every draft is logged
What an agent prepared, and who approved or rejected it, goes in the same append-only audit log as your staff's actions.
Encryption and hosting
Hosted under BAA, over HTTPS
Traffic to Confirmity uses HTTPS. The app is hosted on Vercel and data is stored in a Neon Postgres database. Both run under signed BAAs.
Maya T.Sample
Arjun K.Sample
Diane L.Sample
Sam P.SampleDemos and pilots
Sample data until you say so
Every demo and walkthrough uses made-up clients. You never need to share patient data to see Confirmity work.
Found something? Tell us.
Email hello@confirmity.app with "Security report" in the subject. Include what you found and how to reproduce it. Please don't include patient data, and don't access or change data that isn't yours while testing.
A person reads every report. We will confirm we received it, and if PHI was involved we notify affected customers as our BAA requires.
Business associate agreementSubprocessorsPrivacy policyTerms of service
Ask for our BAA.
We'll send our subprocessor list and security policies to your compliance lead before the first call, and talk through a BAA.
We reply within one business day · No patient data needed