Skip to content

Security & data protection, in plain language

Health data is the most personal data there is. This page explains, without legal jargon, how Curelane is built to protect yours: where it lives, who can see it, and the rules we hold ourselves to. We’re preparing our private beta; this is the architecture we’re building on, and where we stand today is at the bottom of the page.

Last updated: October 2026
Your data is yours

You own every record in your vault. Export it or permanently delete it anytime, with nothing locking you in and no questions asked.

Consent before anything

Nothing is viewed, shared, or fetched without your explicit permission. Every consent is logged and revocable.

Minimum data, always

We collect only what the product needs to work. Nothing for advertising, and we never sell data.

Subscriptions, not surveillance

Our business model is paid plans. You are the customer, never the product.

Your records stay in India

  • Curelane’s servers, databases, and file storage run in Indian data centres.
  • Your identifiable health data is not transferred or processed outside India.
  • The AI layer only ever works on data with your identity removed (see the next section).

AI that never knows who you are

  • Before any AI reads a report, a redaction step on our own servers strips personal identifiers such as names, phone numbers, and IDs. The model sees your numbers, never your identity.
  • Our assistant is built on open medical AI models: an open architecture we can inspect and control, with a path to infrastructure we fully host ourselves as we grow.
  • Your identifiable health data is never used to train AI models, ours or anyone else’s.
  • The assistant explains and informs. It does not diagnose or replace your doctor.

Encryption at every layer

  • All traffic is encrypted in transit (TLS/HTTPS) and all records are encrypted at rest.
  • Sensitive fields are individually encrypted inside the database itself, so no single key can unlock everything.
  • Decryption needs permission, field by field: an application bug, or an AI workflow, cannot read data it hasn’t been explicitly granted. Encryption is the guardrail, not just a policy.
  • Every decryption is logged, creating an audit trail of each access to your data.
  • Your Aadhaar number and OTP are used once for ABHA verification, encrypted in memory, and never stored or logged.

Designed for ABDM’s consent framework

  • ABHA linking, and record fetching when it launches, will follow the ABDM consent framework: you approve what is shared, with whom, and for how long.
  • Every share is logged and revocable, and revocation takes effect immediately.
  • We align with the ABDM Health Data Management Policy and India’s DPDP Act, 2023.

Your rights under the DPDP Act

  • Access: see and export everything we hold about you.
  • Correction: fix anything that’s wrong.
  • Erasure: delete your account and data permanently.
  • Withdrawal: take back any consent as easily as you gave it.
  • Grievance: write to us (below); if unresolved, you may escalate to the Data Protection Board of India.

Who can see your data, including us

  • By default, nobody at Curelane can see whose records they are. Sensitive fields only decrypt for actions you’ve permitted, and every decryption is logged.
  • Our care team checks what the AI reads, such as the values in a lab report, with your name and other identifiers removed. They see the numbers, never who they belong to.
  • When the care team needs to step in, for an alert, a teleconsult or a nurse visit, they see your identifiable records only with your consent and only for that care, following ABHA and ABDM consent guidelines. Every such access is logged, and you can see it.
  • Support staff work with metadata (file names, dates, error logs), never the contents of your reports.
  • Your account will be protected with OTP sign in and a second verification factor.
  • If a security incident ever affects you, we’ll tell you promptly and plainly, as the DPDP Act requires.

Where we are today: Curelane is preparing for private beta. On the road to production we’ll complete ABDM sandbox validation, NHA functional certification, and a “Safe-to-Host” security audit by a CERT-In empanelled auditor.

Security & privacy contact

Found a vulnerability, or have a privacy request or grievance? Write to us at admin@curelane.in

Be first in the lane.

We invite in small batches, and the first spots go to families looking after their parents. Early members have a real say in what we build.

Who are you joining for?

We use these details only for your beta invite and, if you’re joining for your parents, to set up their care. Privacy Policy