Encryption Basics for Personal Health Data: What Actually Protects You
Encryption is the difference between a stolen database being a real breach and being a directory of unreadable garbage. For personal health data, understanding what kind of encryption protects what — and where the gaps usually are — is more useful than the security-marketing bullet points on any provider's website. The mechanics are simpler than they sound.
The three places data lives, and the three protections
- State: In transit · Where: Being sent between your phone and the server · Protection: TLS (the padlock in the browser)
- State: At rest · Where: Sitting on the server's storage · Protection: Server-side encryption — AES-256 typically
- State: In use · Where: Being processed by the server temporarily · Protection: Runtime memory; harder to encrypt but scoped access controls
A well-run health app has strong protection at each layer. A poorly-run one may skip one or more — the commonest gap is at-rest encryption of file attachments, which are stored on cheaper object storage that sometimes is not encrypted by default.
What TLS actually does
When you log into a health app, the connection between your phone and the server is encrypted end-to-end for that hop. This prevents:
- Someone on the same Wi-Fi network reading your data as it travels.
- An intermediate router or ISP intercepting the content.
- A man-in-the-middle attack that inserts itself between you and the server.
This is table stakes — every legitimate service today uses TLS 1.2 or 1.3. If a service does not (the URL starts with http:// rather than https://), do not use it for health data.
What at-rest encryption does
Once your data reaches the server and is stored, at-rest encryption ensures that even if someone gains access to the raw storage — a stolen backup drive, a compromised employee — the data is unreadable without the encryption key. Standard practice is AES-256, and modern cloud providers (AWS, Google Cloud, Azure, Cloudflare R2) provide this by default.
The nuance: whose key encrypts the data matters. Provider-managed keys mean the provider can decrypt if they choose (or are compelled to). Customer-managed keys mean only the customer can. For most consumer health apps, provider-managed is the default and reasonable trade-off.
End-to-end encryption — what it means, and what it does not
End-to-end encryption in the strict sense means only you can decrypt your data — even the provider cannot. Some health apps advertise this; the trade-off is real:
- Pro: even a full provider breach cannot expose your data.
- Con: if you lose your password/key, your data is lost. No recovery.
- Con: server-side features (search, alerts, AI extraction) become harder or impossible.
Most consumer health apps do not offer true end-to-end encryption; they offer strong at-rest encryption with role-based access controls. This is a reasonable balance for most users, provided the app has good breach detection and rapid disclosure.
Where encryption does not help
Encryption protects data from unauthorised third parties. It does not protect against:
- A weak password on your account. Somebody who guesses or phishes your password gets in as you; encryption is irrelevant.
- A device where you are logged in and someone else picks it up. Screen lock and biometric app locks matter more than server encryption here.
- A screenshot or download you took and stored somewhere else.
- Data shared via link to somebody who then downloads it.
What to actually check when choosing a health record app
- HTTPS (TLS) always. Non-negotiable.
- At-rest encryption of both database AND file attachments.
- Two-factor authentication support.
- Session timeout on inactivity.
- App-level PIN or biometric lock.
- Clear breach notification policy.
- Compliance with India's DPDP framework.
A checklist like this is enough for most users. The alternative — reading every security whitepaper — is not the right use of time when a good baseline provider handles the technical details for you.
References
Free for 90 days, no card needed. After that, keeping the record costs ₹349 for the year.
General information, not medical advice. Always talk to a qualified doctor about your own care. Where this and your doctor disagree, your doctor is right.