Section 8(5) · Rule 6
Security practices
The DPDP Act requires reasonable security safeguards to prevent personal data breaches. This page lists the safeguards in place today and the ones still being set up.
Last updated: 28 October 2026
Our safeguards
| Safeguard | What it means | Status |
|---|---|---|
| Encryption in transit | Traffic between your device and our servers uses TLS. Messages are not end-to-end encrypted: our servers process them to deliver the service. | In place |
| Encryption at rest | Our database and file-storage providers encrypt stored data. Two-factor secrets are additionally encrypted by our application. | In place |
| Access control in the database | Row-level security policies limit database access to the people entitled to each record. A doctor reaches a patient’s records only through an active care relationship or a consent grant. | In place |
| Two-factor sign-in | Required and enforced by our servers for every doctor, lab, pharmacy, hospital and administrative account, with a lockout after five wrong codes. Patients can switch it on. | In place |
| Account protection | Strict rate limits on sign-in and session routes, idle sign-out, a check of new passwords against known breached passwords (only a partial hash leaves our server), and a content security policy on the website. | In place |
| Identifier protection | Aadhaar numbers are no longer collected, and profile responses never include two-factor material. Removing Aadhaar numbers stored by earlier versions is awaiting approval. | In progress |
| Audit trail | Changes to clinical, consent and administrative records, and sensitive access such as emergency and owner access, are recorded in append-only audit tables. Most of these tables are linked by a hash chain, so a later change becomes detectable. Extending this to every audit table is being rolled out. | In progress |
| Log retention | Security and audit logs are kept for at least one year; our logging is configured for 400 days and is being rolled out. | In progress |
| Emergency access | Break-glass access to records in an emergency is recorded and cannot be edited afterwards. | In place |
| Backups | Point-in-time recovery for the database, a daily backup of stored files to a separate, versioned and locked store, and a tested restore with recovery targets are being set up. | In progress |
| Independent testing | An independent penetration test is planned after our next release. | In progress |
| Staff training and access review | Privacy training for staff and a quarterly review of who has access are being set up. | In progress |
What you can do
Use a strong, unique password, switch on two-factor sign-in, and sign out on shared devices. If you think someone else has used your account, contact us through the grievance page.
If a breach happens, see breach notification for what we will do.