Last updated: 11 November 2026
Privacy Policy
Medabha is early-access clinic software for doctors in India. This policy explains how we handle personal data under the Digital Personal Data Protection Act, 2023, the DPDP Rules, 2025, the IT Act, 2000, and the SPDI Rules, 2011.
Early access
Medabha is early-access software in active development. Features, uptime, and security controls may change. Do not rely on it as your only copy of clinical records. Export or keep independent records for medicolegal purposes. Early-access status does not reduce our duty to protect personal data, and it does not reduce your duties as a clinician or clinic. "Early access" describes the pace of feature and reliability changes, not a lower standard of data protection — it does not limit any statutory right you or your patients have under Indian law.
Who processes whose data
For clinic-account, billing, and marketing-lead data, Medabha is the Data Fiduciary under the Digital Personal Data Protection Act, 2023 (DPDP Act). For patient health records, prescriptions, consult notes, recordings, and WhatsApp messages you store in Medabha, your clinic is the Data Fiduciary and Medabha is a Data Processor acting on your instructions. Patients should send access, correction, or deletion requests to their clinic; we help the clinic fulfil them.
Data we collect
What we collect, and why: • Clinic account: name, email, mobile number, clinic name, city, specialty and a password (stored only as a hash). To create your account, sign you in and contact you about the service. Without these we cannot open an account. • Billing: your plan, payments and invoices. Card and UPI details stay with Razorpay. To charge for the plan and keep tax records. • Patient records your clinic enters: demographics, ABHA number if stored, history, notes, prescriptions, investigations, attachments and visit recordings. Only to run the clinic's software on its instructions (see "Who processes whose data"). • Usage: AI Scribe minutes, WhatsApp messages and report reads. To apply your plan's allowances and bill usage credits. • Sign-in records: time, IP address and approximate location of each sign-in. To protect accounts and show the clinic owner its access log. • Demo and contact forms: name, email, phone, specialty, message, IP address and approximate location. To reply, schedule a walkthrough and reduce spam. • Website chat: the messages you write in the chat box, the page you write from, your device type and approximate location, and any name, phone or email you choose to leave. To answer you. Deleted 180 days after the last message, or sooner if you ask at care@medabha.com. • Website visits: see "Public website visits" below.
How we use data
We process data only to provide Medabha, send transactional messages you configure, improve reliability, prevent abuse, and comply with law. We do not sell patient data. We do not use consultation audio or clinical notes to train foundation models. AI Scribe drafts are decision support; the signed note is yours.
Demo and marketing registrations
If you request a demo or contact us, we collect your name, email, phone, specialty, message, IP address, and approximate location. We use this to reply, schedule a walkthrough, and keep a lead record. We add you to our mailing list only if you tick the box asking for updates, and every such email has a one-click unsubscribe. You can ask us to delete a lead at care@medabha.com.
Patient health records
Your clinic decides what to record, who may access it, how long to keep it, and how to obtain patient consent — including consent to record a consult and to message on WhatsApp. Indian medical-record, Clinical Establishments, and NMC / telemedicine duties sit with the clinic and the registered medical practitioner, not with Medabha as a software vendor.
Processors & transfers
Our servers are in Bengaluru, India. We use these processors, each only for the job listed: • DigitalOcean: hosting the app and its database. • Cloudflare R2: encrypted off-site copies of daily backups. The key that opens them is not kept on our servers. • Sarvam AI: speech-to-text for AI Scribe audio. • OpenAI: drafting the AI Scribe note from the transcript, and reading lab-report photos when you use report reading. • Meta: the WhatsApp Business API, for messages sent from Medabha's sender. • Razorpay: subscription payments, and patient payments on a clinic's own Razorpay account. • Resend: account and transactional email. • Google (Firebase Cloud Messaging) and Apple (APNs): optional push notifications. • ipwho.is: the approximate city for an IP address, for the sign-in access log and the live view of website visitors. • Google Maps Places: city and clinic-address suggestions as you type. No patient data is sent. • Bunny Fonts: delivers the website's typeface, and sees your IP address when a page loads. Some of these process data outside India. The DPDP Act allows transfers abroad unless the government restricts a country, and we will follow any such restriction. We disclose these processors so you can decide whether the product fits your clinic. We are not a notified ABDM health locker. ABHA enrolment uses Aadhaar OTP through ABDM. The enrolment details go to the National Health Authority's ABDM system.
Retention & security
How long we keep data: • Clinic and patient records: while the account is active. When the owner deletes the account they are removed from our live systems at once, and from backups within 14 days, when those backups expire. • Billing and tax records: for as long as tax law requires. • Sign-in records and website visit records: 180 days. The live view of website visitors: about a day. • Demo and contact enquiries: until you ask us to delete them. • Patient share links stop working after 90 days by default. How we protect it: encryption in transit, access controls and clinic-level tenancy. Visit notes and patient history are encrypted in our database, visit recordings are encrypted on our servers, and daily backups are encrypted before they are stored or copied off the server. CERT-In directions require reporting listed cyber incidents within six hours and keeping certain logs; we treat those as binding on us as a body corporate. No software is perfectly secure; report suspected incidents to care@medabha.com immediately.
Data breaches
If we learn of a breach that affects personal data in Medabha, we will email each affected clinic owner without delay, and within 24 hours of confirming it, with what we know: what happened, which data was involved, what we have done, and what the clinic should do. For patient records the clinic is the Data Fiduciary and decides how to inform its patients and the Data Protection Board; we give it the details it needs to do that. For data where Medabha is the Data Fiduciary (clinic accounts, billing, sign-in records and enquiries), we also inform the people affected and the Data Protection Board of India, in the form and time the DPDP Rules set. We report incidents to CERT-In within six hours where its directions require it.
Significant Data Fiduciary status
Health details are personal data under the DPDP Act. Section 10 lets the central government notify a Data Fiduciary, including one that handles health data at scale, as a Significant Data Fiduciary. That brings extra duties: a Data Protection Officer, an independent data auditor, and periodic data protection impact assessments. No such notification currently names Medabha. If one does, we will comply with those duties and update this policy.
If Medabha is discontinued
If we stop offering Medabha, we will give clinics at least 30 days’ notice at the account email. During that window we will, on request to care@medabha.com, give the clinic a copy of its patient and consult records so it can keep the medicolegal file it is required to hold. After the window we delete remaining clinic and patient data from our systems, except what law requires us to keep (for example billing or incident logs). Turning the product off without that notice and hand-back would leave clinics unable to meet record-keeping duties — we will not do that. Still do not use Medabha as your only copy of clinical records.
Your rights
Under the DPDP Act you can ask us for a summary of the personal data we hold about you and how we use it; ask us to correct, complete, update or erase it; withdraw consent where we rely on consent; nominate someone to exercise these rights if you die or cannot act; and have a grievance redressed. Write to care@medabha.com, or use Settings to export or delete your clinic's data. Withdrawing consent does not undo processing already done, and some records must be kept where law requires a clinic or us to keep them. Requests about a patient's clinical record go to that patient's clinic, which is the Data Fiduciary for it; we help the clinic answer. You can ask for this notice in English or in any language listed in the Eighth Schedule to the Constitution. The DPDP Rules, 2025 were notified on 13 November 2025 and are phasing in: provisions on the Data Protection Board are already in force, Consent Manager registration follows from 13 November 2026, and most remaining operational duties (breach notice timelines, consent mechanics, and the rest) become enforceable by 13 May 2027. Where a DPDP provision is not yet in force, the IT Act, 2000 and the SPDI Rules, 2011 continue to apply to sensitive personal data, including health information.
Children
Paediatric clinics keep records of children under 18. The DPDP Rules exempt clinical establishments and healthcare professionals from the verifiable parental consent requirement for processing that is restricted to providing health services to the child, to the extent needed to protect the child's health. Anything beyond that, such as promotional messages to a parent, needs a parent or guardian's verifiable consent, which the clinic collects. Medabha does not track, profile or advertise to children, and Medabha's own accounts are for doctors and clinic staff, not children.
Grievance officer
Grievance Officer: Abhisek Kumar. Email care@medabha.com or call +91-9330983321. We acknowledge a grievance within 72 hours and resolve it within one month of receiving it. Patients with a question about their own clinical record should first contact their clinic, which decides how that record is used. The Data Protection Board of India was established in November 2025 and is still building out its complaint-handling capacity; once it is fully operational for adjudication, you may also lodge a complaint with the Board under the DPDP Act.
The Medabha mobile app
The Medabha app for Android and iOS, when available in your app store, is the same service in an app container: it signs in to the same clinic account and shows the same data. It stores no patient records on the device. The app requests the microphone only for AI Scribe, and notifications only if you turn them on. Uninstalling the app removes its local session; your clinic data stays on your account.
Audio recordings
AI Scribe records a consultation only while a clinician presses record, and the app shows a red recording indicator for the whole time. Audio is uploaded over an encrypted connection, encrypted again as soon as it is saved on our server, transcribed to produce a draft note, and is never used to train any model. Speech-to-text separates the speakers, and each speaker is labelled (for example doctor, patient or relative) from what they say, for the clinician to check. For the clinic's own clinicians only, phrases they often use are learned from visits a doctor confirmed, to label them in later visits; this is kept encrypted for that clinic and can be deleted under Settings → AI activity. Patients and relatives are never profiled, and no voiceprint is made. Recordings are stored against the consultation and are deleted when the clinic deletes the consultation or its account. Obtaining patient consent to record is the clinic's responsibility.
Notifications
Push notifications are optional and can be turned off in the app or in your device settings. Notification content is deliberately minimal: by default it names the event, never the patient. Push messages are delivered through Google (Firebase Cloud Messaging) on Android and Apple (APNs) on iOS, which see the message text but no clinical record.
Deleting your account
You can delete your Medabha account and all associated clinic data from Settings, or by writing to care@medabha.com. Deletion removes clinic and patient records, consultation audio, and transcripts. It cannot be undone, and it applies whether you signed up on the web or through an app store.
Public website visits
On the public Medabha website, blog, sign-in pages, and registration page we count page views, the referring site, campaign links, and search words when a browser still sends them. Google usually does not send the search query. We also record where people click and how far they scroll on the public site. After a clinic signs in, we count which screens are opened, with record numbers replaced by a placeholder, and we do not store link text from inside the app. A first-party cookie remembers how you first arrived for 30 days, so we can tell which searches lead to sign-ups. For visit history we store a daily keyed hash of the IP address and browser, not the IP itself, and we do not record what you type into forms, including passwords. While a page is open, the live view of who is on the site also keeps the IP address, approximate location, browser, screen size, language and timezone; these are deleted within a day after the page is closed. We keep these visit records for 180 days. This is separate from clinic patient records.
The Medabha app in ChatGPT (added 30 September 2026)
Medabha offers an app inside ChatGPT, run by OpenAI. This section explains what Medabha receives and shares through it. Your use of ChatGPT itself is governed by OpenAI's terms and privacy policy and by your ChatGPT data settings, which Medabha does not control. Without signing in. Anyone can ask the app about Medabha; that uses no personal data. A doctor can also ask it to build a clinic website preview. For that we receive only the business details typed in: doctor name, clinic name, specialty, city, and optionally address, clinic phone, a tagline and opening hours. We keep them for 7 days to show the preview, then they are deleted. We do not contact you about a preview unless you sign up. Connecting a clinic. A doctor or clinic owner can connect their Medabha account by signing in to Medabha and choosing what ChatGPT may do. Receptionist logins cannot connect. Clinic counts and reports (appointments, visits, fees for the owner) contain no patient names. Patient data. Patient tools are not offered from the clinic admin. Counts and reports can still be connected, and those contain no patient names. Details of patients under 13 are never sent, and neither are phone numbers, ABHA numbers, recordings, reports or attachments. ChatGPT cannot sign a prescription, send anything to a patient, or delete a record. Who is responsible. The clinic is the Data Fiduciary for its patients' data. Patient tools are not switched on from the clinic admin. Medabha acts as the clinic's processor for the counts and reports a connected doctor asks for. What we keep. Sign-in tokens are stored only in hashed form and stop working after 30 days without use, or when the doctor loses access. Every time ChatGPT reads or saves patient data we record which doctor, which action and which patient, and keep that record for 180 days. Our server logs note which tool was called, not what was asked or answered. Your controls. A doctor can disconnect the app from ChatGPT's settings. Access stops immediately.
Questions: care@medabha.com · Security & privacy · Terms of service