We built Mobile Health Vault from the ground up with security first. Every technical decision — from database schema design to API authentication — was made to protect your most sensitive data.
Three principles guide every security decision we make.
No data collection beyond what's necessary. No advertising. No sharing with third parties. Your health records are never used to train AI models.
Multiple independent security layers — if one fails, the others hold. No single point of failure in our authentication or data access architecture.
Complete audit trails. Every access to your data is logged. You can see who accessed what and when. Export or delete all your data at any time.
What's actually built into the platform today — not a roadmap, and not a claim we can't back up.
Patients sign in with an OTP to their mobile number by default (password sign-in is also available). Every session runs on a signed, time-limited token — currently 24 hours — with automatic rotation on a 30-day cycle, and every token is invalidated the moment you log out.
The mobile app refuses to start a production build if its API endpoint isn't HTTPS — a hard-coded startup check, not just a setting. iOS builds also disable arbitrary cleartext loads via App Transport Security. In production, the backend only accepts cross-origin requests from an explicit allowlist of known origins, not from anywhere.
Government ID numbers (like Aadhaar) are encrypted before they're ever written to the database — the encryption key is kept separate from the application itself, and the system refuses to store one of these fields unencrypted if that key isn't available. Vault PINs are never stored or compared in plaintext either: they go through a deliberately slow, industry-standard one-way hashing process, so a stolen database backup doesn't hand over usable PINs.
Every patient's records are kept in a completely separate, isolated data partition — our strongest isolation model. Hospital, lab, and pharmacy organisation data is kept apart as well, with access strictly scoped and enforced by organisation.
The Secure Vault within the app requires biometric authentication (Face ID or fingerprint) or a PIN before any document is displayed — biometric unlock retrieves a securely stored credential and calls the same verification the PIN screen uses, so it's a real gate, not a UI-only check. The PIN screen locks out after 5 incorrect attempts, for 10 minutes.
Granular role-based access: patient, family member, doctor, lab_staff, pod_admin. Shared records have expiry dates. Doctors see only what patients explicitly share. Provider staff see only their institution's records.
Sensitive actions across the platform record who did it, their role, and their IP address, to a separate audit service isolated from the primary application data.
Request a complete export of all your health records in standard formats (PDF, FHIR JSON, DICOM). Delivered within 48 hours.
Permanently delete your account and all associated data at any time. Deletion is irreversible and completes within 30 days per our data retention policy.
See a complete log of every time your records were accessed, shared, or modified — by you, family members, or healthcare providers.
Found a security vulnerability? We appreciate responsible disclosure. Our security team reviews all reports within 48 hours and provides updates throughout our remediation process.
📧 tech@mobilehealthvault.comPlease do not publicly disclose vulnerabilities before we've had a chance to address them. We commit to responding within 48 hours.