Not an HMSThe revenue layer above the one you already run — orchestration for hospitals, health aggregation for employers.See the difference →
Sign inGo to my accountStart freeGo to my account
Booking page For doctors For hospitals Corporate health Health packages Labs Pharmacy Nadi Compare Free tools Referrals Claim help

Home · Trust

Data residency

Data-flow diagram: patient records, claims, backups and the Drapto application inside the hospital boundary; only claim submissions you initiate cross to the internet
The boundary drawn as it actually is: on the self-hosted deployment, patient records, claims and backups live on your hardware, and nothing crosses your wall without your action.
  • All primary data is stored in India.
  • All processing, including support access, happens in India.
  • Backups are stored in India and are not replicated outside it.
  • No data is transferred outside India for analytics, training or support.

What this means in practice

If a hospital asks whether a patient record can be read from outside India, the answer is no, and the sub-processor list is how you verify it rather than taking our word.

NADI · DOCUMENT
● Status current
● Plain language yes
● Contact stated
✓ published, dated, binding
If this ever changes

It would be a material change, announced with notice, not a quiet edit to this page. The page carries a last-reviewed date for that reason.

Read the rest of it.

Every one of these pages says what we do, what we do not, and who to write to when it matters.

All trust pagesAsk us something