Where the records are kept
Your browser reads the packet and your browser stores it. It is never sent to us. The rest of this page explains how that works and what we do hold.
| On your computer only | On our servers |
|---|---|
| The uploaded PDFs and images | Your login: name, email, password hash |
| The text read off every page | Your practice: name, members and their roles |
| The timeline, tables and brief | Plan, seat count and Stripe customer number |
| The label you gave the packet | One row per packet read: a ticket number, page count, how many pages were scans or repeats, which lens |
| Your marks and notes | Your custom lens word lists |
| The activity log: who did what action on which ticket, and when |
How that is enforced
Every page on this site is served with a rule that stops the browser from loading scripts from another site or sending data to one. The scan reader, the PDF reader and the fonts all come from this site. We run no analytics or advertising scripts. The one outside service is Cloudflare’s Turnstile check on the sign-in forms, and it is absent from the pages that handle records.
You can confirm this yourself. Open your browser’s developer tools, choose the Network tab, and read a packet. You will see the app’s own files load, followed by a few small requests to us. One says that a packet of a certain number of pages was opened. One records the counts when reading finishes. The others are activity-log entries. None of them carries the file or any text from it.
On your side
The packet is stored in the browser, so the computer is what you need to protect. Use a managed workstation with disk encryption and a screen lock, as you do for your EHR. Read packets only on practice computers. Delete a packet from the list once the chart no longer needs it. Clearing the browser’s site data removes every packet at once.
Moving a packet between computers
The front desk reads the packet on one computer and the doctor wants it on another. You have two ways to move it.
Locked file. The packet is encrypted in the sender’s browser with AES-256-GCM. The key comes from a passphrase, stretched with 600,000 rounds of PBKDF2. You move the file on your own shared drive, the receiver types the passphrase, and it opens in their browser. Our servers play no part.
Practice inbox. This is the same locked file, held on our storage for up to seven days so the receiver can fetch it without a shared drive. We hold the encrypted file and never the passphrase, so we cannot read it. Under HIPAA, a company that stores patient records is a business associate even when the records are encrypted. For that reason the inbox stays switched off until a business associate agreement is signed with your practice and with our storage provider. Today it is off for every account.
HIPAA
In the standard setup no protected health information reaches Priorfolio. We therefore hold nothing of yours that we could disclose or lose in a breach. Your practice stays responsible for the workstation, as described above. If your compliance officer wants our position in writing, or wants to discuss an agreement for the inbox, ask on the Contact page.
Accounts
Passwords are stored only as hashes. A session lasts 30 days and you can end it from your account page. When someone is removed from a practice, their sessions end at once. Sign-in, invitations and checkout are rate-limited. Card payments happen on Stripe’s pages, and card numbers never touch our servers.
Service providers
Cloudflare hosts the site, the account database and email delivery. Stripe handles payments. We send neither of them patient records, because we have none to send.
Reporting a problem
Write to hello@priorfolio.com. Please leave patient information out of the message.