June 16, 2026 · Perspective
Private vs cloud cancer apps: why local-first matters for medical data
A loved one's cancer details are some of the most sensitive information a family will ever hold. Most apps quietly send that data to someone else's servers. Here's what that means — and why "local-first" is worth caring about.
When you type a diagnosis, biomarkers, and treatment history into most health apps, that information doesn't stay on your phone or laptop. It travels to the company's cloud — where it's stored, processed, and, depending on the fine print, sometimes analyzed or shared. For a recipe app, who cares. For your mother's cancer profile, it's worth a pause.
"Cloud" means someone else's computer
Cloud-based apps keep your data on servers the company controls. That enables convenient sync across devices — but it also means your loved one's medical details now live somewhere you can't see, governed by a privacy policy that can change, subject to that company's security, its business model, and the risk of a breach. Once data leaves your device, you're trusting a chain of parties you'll never meet.
HIPAA probably doesn't cover the app you're using
This surprises people: HIPAA generally applies to healthcare providers, insurers, and their business associates — not to most consumer apps you download yourself. A symptom tracker or a "cancer research" app from the app store usually isn't a HIPAA-covered entity. Its handling of your data is governed mainly by its own privacy policy and general consumer law, not the protections you'd assume apply to medical information.
The safest data is the data that never leaves your device in the first place. You can't lose, leak, or monetize what you never collected centrally.
What "local-first" actually means
Local-first software keeps your data on your machine as the source of truth. The profile, the findings, the reports — they live in a database on your own computer, not on a company server. There's no account to create, nothing to sync to a third party, and no central pile of patient data to breach.
It's a deliberate trade: you give up effortless multi-device cloud sync in exchange for the strongest possible privacy posture. For deeply personal medical information, that's a trade many families are glad to make.
Why open source makes the promise checkable
"We respect your privacy" is a sentence in nearly every privacy policy, including from companies that later turned out to sell data. Open-source software is different: the code is public, so the privacy claims can be verified rather than trusted. Anyone — a developer friend, a security researcher — can confirm what the app does and doesn't send anywhere.
Questions to ask any health app
- Does my data leave my device? If so, to where, and can I turn that off?
- Do I have to create an account? (An account usually means cloud storage.)
- What does the privacy policy say about sharing, selling, or analyzing my data?
- Is the code open for inspection, or do I have to take the claims on faith?
- If the company shuts down or is acquired, what happens to my data?
Firstlight is local-first by design
No account, no cloud, no Firstlight server. Your loved one's profile and reports stay in a local, encrypted database on your own device — and because Firstlight is open source under AGPL-3.0, you can verify that for yourself. Free, private, forever.
← Back to the blog · Read: how to stay on top of new research →