Built secure from the ground up
Health data is among the most sensitive data that exists. We treat it that way — with multiple layers of protection and a minimal attack surface.
Device-level encryption
Your health database uses AES-256 encryption. The key is generated randomly on your device and is never sent to us — meaning even we cannot access your data. It is stored in the iOS Keychain or Android Keystore, where it can be read only while your device is unlocked.
Local-first architecture
The app makes no outbound network requests during normal operation. No health data leaves your device unless you explicitly trigger an export or email-report action.
Caregiver Dashboard stays local
Caregiver Pro’s dashboard reads directly from your device’s encrypted database. Viewing every profile in one place never involves a server round-trip or a second device.
No third-party SDKs with data access
We do not include advertising SDKs, third-party analytics that access health content, or social login SDKs that could exfiltrate your session data.
Minimal permissions
Medical Companion requests two permissions: local notifications for dose reminders, and Face ID or Touch ID if you turn on the optional app lock. No contacts, no microphone, no camera, no photo library, no location. There is no Apple Health integration — Medical Companion neither reads from nor writes to HealthKit.
Secure FHIR export
FHIR R4 export bundles are generated entirely on-device and shared directly via the iOS share sheet. They are never routed through our servers.
Responsible disclosure
If you discover a security vulnerability in Medical Companion, we ask that you report it to us privately before public disclosure. We will acknowledge your report within 48 hours, investigate thoroughly, and keep you informed of our progress.
Contact security team