Security overview

Effective 2026-10-26. This is a short, honest summary. Where something is still being built, we say so and give a date.

What is in place today

Customer separation. Each clinic's data is walled off from every other clinic's inside the database.
Roles. People get only the access their job needs. Every change is written to an audit trail with who and when.
Sign-in. Passwords are stored only as salted hashes. Administrators must use an authenticator app code as a second step.
Bank links. Plaid bank links are read-only and are set up by the clinic owner. We never see the bank password. Bank access keys are kept out of our code and database. Connections to Plaid use HTTPS.
No real data in development. Development and testing use made-up data only. Our logs hold IDs, never names or record contents.
Change control. Every code change is reviewed in a pull request and runs automated checks. Package updates and known-vulnerability scans run automatically.

Application-level encryption of Plaid access tokens: in progress, due 2026-10-31.
Verified disk encryption and tested backups on the production server: due 2026-11-30.
Vulnerability scans become blocking in our build: 2026-11-15.
We do not run a penetration-testing program yet. We will decide on an outside test by 2027-03-31.

We tell affected clinics and Plaid within 72 hours of confirming that their data was exposed.

Write to Adam Silver, Founder and security owner: adam@silverpeak-consulting.com. Please do not include health or bank details in the first message.