Security & trust
Health data, handled with the care it deserves.
DiabetesLife holds glucose readings, lab reports and messages between patients and their doctors. This page sets out, plainly, how we protect them, for patients, and for clinics evaluating the portal.
Access control
- A patient's records are private to them by default.
- A doctor sees a patient only after that patient links to them in the app, and the patient can unlink at any time to stop sharing.
- Family members the patient invites get read-only access, and the patient can remove them at any time.
- Clinic staff a doctor adds (up to 5, such as a nurse or diabetes educator) sign in with their own accounts, see only that doctor's linked patients, and cannot see the doctor's notes or messages. Readings and lab results they add are marked with their name.
- Every time a doctor, their clinic staff or a family member opens a patient's records it is written to an access record the patient can read in the app.
- Doctors show as Verified once we have checked their registration number against the medical council register.
- Row-level security in the database enforces this on every table, so the rule holds even if application code has a bug.
- Doctors propose medication changes; nothing changes in the patient's regimen until the patient confirms it.
- One email address cannot be both a doctor and a patient account.
Sign-in protection
- No passwords to leak or reuse: every sign-in uses a one-time code sent to the account's email.
- Cloudflare Turnstile screens sign-in requests to block bots and email-bombing.
- On the phone, the session is kept in the Android Keystore through secure storage, not in plain app files.
- The doctor portal signs out a login left unused for 8 hours, for clinics that share computers.
- Each doctor's login works on up to 2 devices at a time; signing in on a third signs out the oldest.
Hosting & encryption
- Data is held by Supabase, whose platform is SOC 2 Type 2 audited and encrypts data at rest.
- All traffic between the app, the portal and our servers is encrypted in transit (HTTPS/TLS), with HSTS on the portal.
- The portal refuses to be framed by other sites, blocks content sniffing and is kept out of search engines.
- Android release builds are shrunk and obfuscated.
Use of AI
- AI features (reading lab reports and meal photos, explaining results, meal plans) use Google Gemini on its paid service.
- Only the report, photo or values needed for that one request are sent, solely to return the result.
- Under Google's paid-service terms, this data is not used to train AI models.
- AI never changes a patient's medicines: only a linked doctor can propose that, and the patient must confirm it.
Privacy & India's DPDP Act
- Patients give explicit, recorded consent (with its version and time) before any health data is collected.
- Everyone can export a full copy of their data, on every plan, free or paid.
- Accounts can be deleted from the app or the portal; deletion removes personal and health data, and each erasure is logged.
- Patients can name a nominee and withdraw consent from the app. A child's account records the parent or guardian's consent.
- If a breach ever affects patients, we tell them without delay and report to the Data Protection Board within 72 hours.
- We do not sell personal data and show no advertising.
- A named Grievance Officer acknowledges concerns within 48 hours.
Service providers
We share data only with the providers that run DiabetesLife, and only what each needs. The full list, with what each one processes, is in our privacy policy.
| Provider | Used for |
|---|---|
| Supabase | Database, authentication and file storage |
| Google Gemini | AI processing of lab reports, meal photos and meal plans |
| Google Play Billing | In-app purchases on Android |
| Razorpay | Web and clinic payments (PCI DSS compliant); we never see card details |
| Resend | Email: sign-in codes, doctor, family and emergency-contact alerts |
| Cloudflare Turnstile | Bot and abuse protection on sign-in |
Certifications
DiabetesLife does not yet hold its own ISO 27001 or SOC 2 certification. We build on providers that do (see above), and we will list our own audits here as they are completed. Clinics with a security questionnaire can send it to support@diabeteslifeapp.com.
Report a security issue
Found a vulnerability? Email support@diabeteslifeapp.com with the subject “Security report”. Please give us a chance to fix it before sharing it publicly, and don’t access other people’s data while testing. We acknowledge reports within 48 hours.