Skip to content

Not an HMSThe revenue layer above the one you already run — orchestration for hospitals, health aggregation for employers.See the difference →

Booking page For doctors For hospitals Corporate health Health packages Labs Pharmacy Nadi Compare Free tools Referrals Claim help

Trust centre

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.

A hospital buying software that touches patient data has a list of questions. This is that list, answered, so you do not have to email us for a PDF.

NADI · DOCUMENT

● Status current

● Plain language yes

● Contact stated

✓ published, dated, binding

Data residencyWhere data lives, and what never leaves India.Sub-processorsEvery third party, what they do, and where.Security practicesAccess, encryption, review and testing.AvailabilityWhat we commit to, and how you see it.Incident responseWhat happens, and when you hear from us.Business continuityBackups, restore, and the worst case.Data processing termsThe DPA, in readable form.Retention and deletionWhat we keep and for how long.Access controlWho at Drapto can reach what, and when.Vulnerability disclosureHow to report, what we do.Compliance postureDPDP, IT Rules, ABDM, NABH — stated honestly.How the assistants use dataWhat Nadi reads, and what it never does.

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 pages Ask us something