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

Clinic account details (name, email, phone, clinic name, city, specialty, billing). Patient data your clinic enters (demographics, ABHA number if stored, history, notes, prescriptions, investigations, attachments). Usage data for AI Scribe and WhatsApp. Marketing and demo form submissions, including IP address and approximate location used to contact you and reduce spam.

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 do not add you to unrelated marketing lists from that form. 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

Subprocessors include cloud hosting, OpenAI (AI Scribe transcription), Meta (WhatsApp Business API), Razorpay (payments), and Google / Apple (optional push). Some of these process data outside India. DPDP does not impose a blanket health-data localisation rule, but the government may restrict transfers. We disclose these processors so you can decide whether the product fits your clinic. We do not currently operate a notified ABDM health locker or ABHA OTP fetch.

Retention & security

Clinic data is retained while the account is active, and for a limited period afterwards if needed for billing, disputes, or law. Patient share links expire after sign (default 90 days). We use encryption in transit, access controls, and clinic-level tenancy. CERT-In directions require reporting listed cyber incidents within six hours and retaining 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.

Significant Data Fiduciary status

Medabha processes health data, which the DPDP Act treats as sensitive. Section 5 of the Act lets the central government notify certain data fiduciaries — including, potentially, health-technology processors handling data at scale — as a Significant Data Fiduciary, with extra duties such as appointing a Data Protection Officer and an independent data auditor, and running 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

Clinics may access, correct, export, or delete account data, or ask us to help with a patient request, by writing to care@medabha.com. Patients should contact their clinic for clinical records. You may withdraw consent for processing that is based on consent, subject to law that requires a clinic to keep records. 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 may store data of persons under 18. Under DPDP, processing children’s data generally needs verifiable parental or guardian consent, and the clinic is responsible for collecting it. Do not use Medabha to profile, target, or advertise to children.

Grievance officer

Privacy and data grievances: care@medabha.com. We aim to acknowledge within 72 hours and resolve within a reasonable period. 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 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, transcribed to produce a draft note, and is never used to train any model. 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. 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. 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 off until the clinic owner switches on patient access in Medabha under Settings → ChatGPT, and each doctor must also tick them when connecting. Only then, when a doctor asks, ChatGPT receives the patient details needed to answer: name, age, gender, last visit date, recent visit summaries, allergies and, if allowed, medicines. These details then appear in that doctor's ChatGPT conversation. Details of patients under 13 are never sent, and neither are phone numbers, ABHA numbers, recordings, reports or attachments. Drafts ChatGPT saves stay unsigned in Medabha; 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 and decides whether to allow patient access. A clinic that turns it on should tell its patients, and should use it only as its own obligations allow. Medabha acts as the clinic's processor. What we keep. Sign-in tokens are stored only in hashed form and stop working after 30 days without use, when the doctor loses access, or when the clinic disconnects. Every time ChatGPT reads or saves patient data we record which doctor, which action and which patient, and show it to the clinic owner under Settings → ChatGPT for 180 days. Our server logs note which tool was called, not what was asked or answered. Your controls. The clinic owner can switch patient access off or disconnect every doctor at once in Settings → ChatGPT; access stops immediately. A doctor can also disconnect the app from ChatGPT's settings.

Privacy Policy