Security

Last updated: 26 October 2026

We hold patient health information on behalf of dental practices. This page says exactly how it is protected — and, at the end, what we do not have, because a security page that only lists strengths isn't worth reading.

Where your data lives

Our database runs in a Canadian region (ca-central-1). Patient information is stored in Canada. The application is served from Vercel's Montreal edge (yul1) and its server functions are pinned to that same Montreal region; patient information is stored only in the Canadian database.

This is a deliberate constraint, not a default. Ontario practices operate under PHIPA, and keeping the data in the country removes a whole category of question before it is asked.

Who can see what

Each practice sees only its own records. Every read of patient information is scoped to the requesting user's practice at the point the data is fetched — not hidden in the interface, but never retrieved in the first place. A record belonging to another practice returns "not found"; the system does not confirm that it exists.

Multi-location groups are separated the same way unless the group asks otherwise.

Inside Verifly, access is by named individual account with a role that limits what it can reach. Everyone with access signs a confidentiality undertaking and is trained before being granted it. Access is removed the same day a person's role ends.

Accounts and sessions

  • Passwords are stored as scrypt hashes. We cannot read your password. If you lose it, we can only issue a temporary one, which must be changed at first sign-in.
  • Session cookies are signed and version-stamped. Changing a password, resetting one, or deactivating an account invalidates every session already issued for it — so a lost laptop is a one-click problem, not an open door.
  • Sessions end after 12 hours without activity, and after 30 days at most, after which the person simply signs in again.
  • Sign-in is rate limited against brute-force attempts.
  • Accounts are per person. We ask practices not to share logins, because the record of who did what is what protects everyone if a question is ever raised.

Carrier portal credentials

Where a practice asks us to use their carrier portal, those credentials are:

  • encrypted at rest with AES-256-GCM, using a key held only in the runtime environment — never in our source code, never in the database;
  • still the practice's property, deleted immediately on request or when the agreement ends;
  • used only for that practice's own verifications.

We stop after two failed sign-in attempts and call the practice, rather than risk locking them out of their own carrier account.

Encryption

All traffic is encrypted in transit with TLS. Data is encrypted at rest by our database provider. Sensitive fields — portal credentials — carry a second layer of application-level encryption on top of that.

The audit record

Every material action on a verification writes a record: what happened, who did it, and when. Under PHIPA a practice must be able to answer the question "who touched this patient's information?" — this is how that question gets an answer instead of a shrug.

Patient information is kept out of application logs and out of error messages.

Artificial intelligence

No patient information is ever entered into an AI service. Not into a prompt, not into a pasted log, not into a screenshot. We use AI tools to build and maintain our software; they never see patient data. This is a written rule in our engineering standards, it binds our contractors, and it is a term of every agreement we sign with a practice.

We say this explicitly because the industry default is drifting the other way.

Verification accuracy is a security property too

Every breakdown we deliver records the date of the call, the name of the carrier representative we spoke to, and the carrier's reference number. If a result is ever disputed, it can be traced to its source. We would rather be provably wrong about one call than plausibly right about all of them.

If something goes wrong

We notify the affected practice of any actual or suspected breach at the first reasonable opportunity, and within 24 hours of becoming aware of it — with what happened, when, what information was involved, and what we have done to contain it.

We preserve the evidence. Nothing gets deleted or tidied while an incident is being investigated. The practice, as the custodian, decides on notification to patients and to the Information and Privacy Commissioner, and we cooperate fully with both.

How we build

  • Every change runs through automated typechecking, linting, a build and a test suite before it can be deployed.
  • Changes are reviewed, including by an independent automated reviewer whose job is to find what the author missed.
  • No secret has a fallback value: if a credential is missing, the system fails closed rather than running in a weaker mode.
  • Development and testing run against fictional data. Production credentials are not handed to development tooling.

What we do not have

  • We are not SOC 2 audited. We hold no SOC 2 Type I or Type II report today. We operate most of the controls such an audit would examine, and we will pursue the audit when a customer's procurement genuinely requires it. We will not imply we have one before then.
  • We hold no HIPAA certification. HIPAA is a US framework; our obligations are PHIPA and PIPEDA. If we ever serve US practices, HIPAA obligations would arrive by contract and we would say so.
  • We are not ISO 27001 certified.
  • We are a small company. That means decisions are made by people who understand the whole system — and it means we do not have a 24/7 security operations centre. We would rather you know that than find out.

Reporting a vulnerability

If you find a security problem, tell us at hello@verifly.ca. We will acknowledge it within two business days and keep you informed while we fix it. We will not pursue anyone who reports a genuine issue in good faith and gives us a reasonable chance to fix it before disclosing it.


Questions: hello@verifly.ca · Privacy Policy