Your patients' records stay in India. Here is exactly where, and what that does and does not cover.
Saaro Health is hosted in India, in hosting region. Databases, report files, backups and the WhatsApp messaging layer are all in-country. The one thing that crosses a border is the WhatsApp message itself, and we say so.
- Hosted in India
- Backups in India
- Owned messaging layer
No single law orders every clinic to keep data in India. Several point the same way.
The DPDP Act 2023 does not impose a blanket localisation rule. It allows transfer of personal data outside India except to countries the central government restricts by notification, and it lets sectoral regulators set stricter rules. That is the baseline, and it is looser than many clinic owners assume.
Around that baseline sit stronger expectations. Health data has long been treated as sensitive personal data under the IT Act rules. The Ayushman Bharat Digital Mission's architecture assumes that records are held by Indian providers on Indian infrastructure and shared through an Indian gateway. Draft health-data policies over the years have consistently leaned towards in-country storage. And a patient asked where their prescription history lives generally expects the answer to be 'here'.
So the practical standard for a clinic is not 'is localisation mandatory today' but 'can I say with confidence where the data is, who can reach it, and what, if anything, leaves the country'. This page answers those three questions for Saaro Health.
Every category of data, and where it is stored.
Product means Lumotis controls the location. Clinic means the location depends on a choice you make. Both means we control it and you can verify it.
- Saaro handles it
Patient records, visits and prescriptions
Stored in the primary database in hosting region, India. Encrypted at rest. No replica exists outside India.
- Saaro handles it
Reports, images and uploaded documents
Stored in object storage in hosting region, India, encrypted at rest, and referenced from the patient record.
- Saaro handles it
Backups
Encrypted backups are kept in a separate location within India. Backup copies are never placed in a region outside the country.
- Saaro handles it
WhatsApp messaging infrastructure
SaroConnect, Lumotis's own WhatsApp Business Solution Provider infrastructure, runs in India. Message templates, delivery logs and conversation state are stored in-country.
- Shared
The WhatsApp message in transit
Once a message leaves SaroConnect it travels over Meta's WhatsApp network to the patient's phone, and Meta's infrastructure is global. This is true of every WhatsApp message sent by anyone; we state it rather than hide it.
- Saaro handles it
Voice dictation audio
Audio for prescription dictation is processed and discarded after transcription. Processing location: voice processing region. Audio is not retained.
- Saaro handles it
Email notifications
Transactional email (login codes, invoices to the clinic owner) goes through the email sub-processor listed on the sub-processor page, with processing location shown there.
- Saaro handles it
Product analytics
Usage analytics on the marketing website and product interface do not include patient data. Their processing location is listed on the sub-processor page.
- Your clinic
Exports you download
Once an owner exports data to a laptop, phone or drive, its location is up to the clinic. Keep exports encrypted and delete them when no longer needed.
Residency is a property of the platform, not a setting you have to remember.
Single Indian region
All clinics on Saaro are hosted in hosting region. There is no option to pick a foreign region, so nobody can choose one by accident.
Owned messaging layer
Because SaroConnect is Lumotis's own infrastructure, there is no third-party BSP in another country holding your patient numbers and message content.
Learn moreOne record across branches
Multi-location clinics keep one patient record in one place. No per-branch copies, no synchronisation across regions.
Learn moreABDM through the Indian gateway
Records pushed under consent go through the ABDM gateway to the receiving Indian provider, encrypted end to end.
Learn morePublished sub-processor list
Every third party that touches data is named with its role and location, and you are notified before a change.
Learn moreRecord export stays local
Patient exports are generated and downloaded from the Indian region. No intermediate copy is placed elsewhere.
Learn more
Where the record has been is part of the record.
When a patient asks where their data is, the front desk should be able to answer from the screen. Each record's timeline shows storage region, every export, and every push to another provider under consent.
That is also the answer to an auditor's question about cross-border transfer: the log shows there were none, apart from consented ABDM pushes to Indian providers.
- Storage region shown on the record
- Every export logged with destination
- ABDM pushes logged with receiving HIU
- No entries for foreign transfers, because there are none
- Mon 1 SepRecord created · hosting regionIndia
- Mon 1 SepReport uploaded · object storage, IndiaIndia
- Tue 2 SepRx pushed under consent to hiu name via ABDMABDM
- Tue 2 SepCross-border transfersNone
Data category, location, and the control behind it.
Locations confirmed in the data processing agreement and the sub-processor list. Tokens are filled in at signature.
| Data category | Location | Control |
|---|---|---|
| Patient records | India, hosting region | Single-region hosting; no foreign replica |
| Reports and documents | India, hosting region | Object storage, encrypted at rest |
| Backups | India, separate location | Encrypted; never stored abroad |
| WhatsApp templates and logs | India (SaroConnect) | Lumotis-owned infrastructure |
| WhatsApp message in transit | Meta's global network | Disclosed; inherent to WhatsApp |
| Dictation audio | voice processing region | Processed and discarded; not retained |
| Transactional email | See sub-processor list | No clinical content in email |
| Analytics | See sub-processor list | No patient data collected |
| Owner exports | Wherever the clinic saves them | Encrypted archive; clinic responsibility |
Swipe to see every tier
Your questions answered.
The things clinics ask first.
In India, in {{HOSTING_REGION}}. Databases, report files, backups and the WhatsApp messaging layer are all in-country. There is no foreign replica.
Not as a blanket rule. It allows transfers except to countries the government restricts, and lets sectoral regulators go further. Health data is treated as sensitive, ABDM assumes Indian hosting, and patients expect it, so Saaro hosts in India regardless.
The WhatsApp message itself travels over Meta's global network once it leaves SaroConnect, as every WhatsApp message does. Dictation audio is processed in {{VOICE_PROCESSING_REGION}} and discarded. Everything else stays in {{HOSTING_REGION}}.
No. Every clinic on Saaro is hosted in {{HOSTING_REGION}}. Removing the choice means no clinic can end up in a foreign region by mistake.
The data processing agreement names the region and sub-processors. The sub-processor page lists each with its location. On request we provide a configuration summary from the hosting provider showing the region.
Records pushed under a patient's consent go through the ABDM gateway, which is Indian infrastructure, to the receiving Indian provider, encrypted end to end. Each push is logged on the patient's record.
Keep reading.
- FeaturesPatient recordsA record built from every visit, not a spreadsheet row. Prescriptions, reports, notes and follow-ups sit in one timeline, linked to the patient's ABHA if they have one.
- FeaturesWhatsApp automationSaaro runs on SaroConnect, Lumotis's own WhatsApp Business infrastructure. Reminders, prescriptions, reports and refills go out from your number, patient replies come back to the desk, and messaging is included in every plan.
- FeaturesMulti-clinicSaaro runs a clinic chain as one system: a shared patient index, doctors who move between branches, billing that stays separate per location, and a single view for the owner.
- TrustSecurityPatient data is encrypted in transit and at rest, seen only by the roles that need it, logged every time it is touched, and backed up so it can be restored. Here is the detail behind each of those claims.
- TrustSub-processorsA sub-processor is any company Lumotis uses to process clinic data on your behalf. This page lists them, says what each does and where it runs, and explains how you are told before one is added.
- TrustDPDP complianceConsent, notice, retention, erasure, breach reporting and grievance handling are obligations on the clinic. Here is what each one means for an OPD, and which parts the product does for you.
Ask where the data is. Get a straight answer.
Twenty minutes, and a configuration summary if you want it in writing.