We built it so we can't see your patients.
Most vendors promise to protect PHI. Verq's architecture never receives it. This page is written to be forwarded.
How it works
Verq captures the note from the WebPT chart.
Every identifier — names, dates, MRNs, contact details — is stripped and replaced before anything is transmitted. This de-identification wall is the core of the product (patent pending).
Analysis runs on de-identified clinical text only. Findings return to the browser, where they're re-attached to the note in the panel. PHI never made the trip.
What this means for the practice
- nothing to breacha breach of Verq's servers cannot expose your patients — the data isn't there
- a simple baaclick-through because the risk surface is genuinely small, not because we're casual about it
- no admin consoleno clinic-level data store; findings exist in the clinician's panel, period
- documentation onlyVerq never sees claims, fee schedules, or remittances
- nothing stored locallynothing on clinician machines beyond the extension; notes live where they always did — in WebPT
The boring, important details
encryption in transit (tls 1.2+) and at rest · least-privilege access · no training on your data · no sale of data, aggregate or otherwise · subprocessor list available · security contact: security@verq.ai
For owners and compliance officers: download the one-page security summary (PDF) — for whoever has to say “yes, this is okay to install.”