JeevAyu is in private testing, and everything below is already built into the product today, not a roadmap. We're not yet formally certified (no SOC 2 or HIPAA certification), so treat this page as an honest, general description of how we protect your data, not a technical spec sheet or a compliance claim.
Encryption, account protection, and access control, working together.
Your most sensitive health details are encrypted in our database, not just protected by a password, and every connection to our servers is encrypted too.
Turn on 2FA with any authenticator app, backed by one-time backup codes if you lose your device. A correct password alone stops being enough.
Repeated failed logins, automated guessing, and stolen session tokens are all defended against automatically, without you having to do anything.
A full list of everything signed into your account, with a remote sign-out button per device, and a flag if a new one appeared since you last checked.
Managed profiles for the people you care for are separate records with their own access rules, not data lumped together under one account.
A record is only ever shared through a link you create, and you can revoke that link's access at any time. Nothing is shared automatically.
Your phone itself is part of the security model, not just our servers.
An additional lock screen every time you open the app, independent of your account password: PIN, Face/Touch ID, or both.
Your Emergency Card, Health ID, and record screens actively block screenshots and recording on Android, and black out during an active recording on iOS (Apple allows nothing stronger).
Copy your Health ID or a share link, and it wipes itself from your clipboard after a minute, unless something else gets copied over it first.
JeevAyu checks for signs of a rooted or jailbroken device at launch and warns you clearly, rather than silently trusting a phone that's been modified.
JeevAyu publishes a standard security.txt file and a public responsible disclosure policy. We also run routine vulnerability scans as part of normal development, not just before a release.
If you've found a security issue, email hello@jeevayu.com with a description, steps to reproduce it, and any affected URLs or endpoints. We read every report and will follow up.
Please don't use real patient data to demonstrate an issue (test data only), and give us a reasonable window to fix something before any public disclosure.