Blog ·
Why your clinical notes should never leave your machine
Ask where your current practice software keeps its records, and the answer is almost always the same: in the vendor's cloud, in a database shared with every other customer, protected by policy. Policies are real protections, drafted by real lawyers — and they share one structural weakness: every one of them can fail while leaving the data intact and exposed. SideClick starts from a different answer. Patient records live on your machine, encrypted, and the default number of external copies is zero.
A breach needs something to breach
A vendor's multi-tenant database is a concentrated target: thousands of practices' records behind one login page, one privilege-escalation bug, one phished employee. The economics of attacking it are excellent, which is why health-data breaches keep making the news at the scale of whole platforms, not single clinics. A record encrypted on one practitioner's machine offers an attacker terrible economics: enormous effort, one practice's data, still encrypted.
Local-first doesn't make attacks impossible — nothing does, and a vendor claiming otherwise is selling something. What it does is remove the catastrophic failure mode, the everyone-at-once breach, from the space of possible events. Your risk becomes bounded by your own machine and habits, which are at least yours to govern.
The AI question, answered by placement
AI drafting is genuinely useful for clinical documentation — and it is also where most products quietly ship your session content to a third-party API, with retention terms three contracts deep. SideClick's assistant runs on your own hardware. The model drafts your SOAP note without a word leaving the room, which is why the AI keeps working when the internet doesn't, and why opting in requires no new privacy conversation with clients at all.
The placement also changes the consent story. 'I use an AI assistant that runs on this computer' is a sentence a client can evaluate. 'I use an AI service, see their privacy policy' is homework you are assigning to someone who came in about their shoulder.
Fast, offline, yours
- No network round-trip inside your documentation loop — the record opens at disk speed
- The whole practice works offline: rural clinics, home visits, outages
- Exports (.cfbak, FHIR, PDF, CSV) work in every licence state, forever
- No vendor outage can cancel a clinic day, because no server is load-bearing
What about sync, backups, the portal?
Local-first does not mean isolated. SideClick practices sync across devices, keep off-site backups and run a patient portal — through a relay that carries only ciphertext, so the conveniences arrive without a readable copy accumulating anywhere. The mechanics deserve their own post, and they have one: Zero-knowledge sync, explained for clinicians.
None of this requires trusting us, which is precisely the point. Software that holds your records hostage was always the anomaly, however normal it became. Records on your machine, readable by no one else, exportable any time — that is just what owning your practice's data is supposed to mean.