We can't lose what we never receive.
Practice KPIs runs on your practice's PC. Your reports are read, checked and stored there. We built it so patient data has nowhere else to go, and this page lists every field that does leave.
How data flows
Everything happens inside one Windows user account on one PC. The app doesn't connect to eClinicalWorks, and nobody from Clinihealth logs in to it.
What stays on your PC
- The report files you export from eBO, and everything read from them.
- The app's data store for each practice, inside your Windows profile (
%LOCALAPPDATA%\Practice KPIs). - Every page, chart, table and download the app makes.
- The app's own logs. They hold counts and timings, never patient rows.
What leaves your PC
When it's online, the app sends one small licence check to our server, and fetches its licence and update notices. The check is built from a fixed list of nine fields; anything else is dropped before it's sent, and an automated test plants made-up patient names in a practice to prove none of them can reach the message. If you connect an account to activate a practice or share access, the app also sends your email, your access code, the practice names you add and the emails of people you give access to.
install_id | A random number made when the app is installed. It identifies the install, not a person. |
|---|---|
app_version | Which version you're running, so we know who has an update. |
download_code | The short code from your download, which links the install to the person who downloaded it. |
terms_version, terms_accepted_at | Which version of the terms was accepted, and when. |
licence_id | Your licence, so the app knows which practices are paid for. |
practices | The practice names you typed into the app. Nothing else about the practice. |
store_mb | The total size of the data stores, in megabytes. Sizes only, no file names. |
addons | Which optional add-ons are switched on. |
What we never receive
When you write to support, please don't attach report files or screenshots with patient details. We never need them to help you.
HIPAA in plain words
HIPAA applies to how a practice and its business associates handle protected health information. No government body certifies software as "HIPAA compliant", so we don't use that phrase.
What we can say is how Practice KPIs is built: patient information stays on your PC, under the safeguards your practice already applies to that computer, and it is never sent to Clinihealth. If your compliance policy asks for a business associate agreement or a security questionnaire, write to us and we'll work through it with you.
Protecting the PC
Because the data lives in your Windows profile, the protections you already use cover it:
- Your Windows sign-in. Other Windows users on the same PC can't open your profile's data without administrator rights.
- Disk encryption. Turn on BitLocker (or your practice's equivalent) so a lost laptop doesn't expose anything.
- Backups. Include your profile in the practice's normal backup.
- Removal. Uninstalling the app and deleting
%LOCALAPPDATA%\Practice KPIsremoves everything it stored.
Installs and updates
- The installer runs for your Windows user only and doesn't need administrator rights.
- Licences and update notices are signed with our private key and checked inside the app before they're trusted.
- Every download has a published SHA-256 checksum on the release notes, so you or your IT person can check the file.
- If a licence lapses, the app goes read-only after 14 days' grace. You're never locked out of your own data.
Services we use
| Cloudflare | Hosts this website and our domain. Sees normal web traffic, no patient data. |
|---|---|
| Fly.io | Runs our licence and download server. Holds the fields listed above and your account details. |
| Stripe | Sends our invoices and takes payment by card or bank transfer. We never see your card or bank details. |
| Resend | Sends our emails, such as download and sign-in codes. |
| Google Workspace | Our email, for [email protected]. |
Reporting a problem
If you think you've found a security issue, email [email protected] with "Security" in the subject. Describe what you saw without including patient information. We'll reply within one business day and keep you posted until it's fixed. Our security.txt has the same details.
Last reviewed Oct 18, 2026