Vaididea Healthcare Private Limited
Privacy Policy
Notice of data collection and processing practices · www.vaididea.in
Effective date: [DD Month YYYY] · CIN: [CIN] · Registered office: [registered office address]
Privacy at a glance
This table is a short summary. The full Policy that follows is the notice that applies to you, and if anything here differs, the full Policy prevails.
| Question | Short answer |
|---|---|
| Who is responsible for my data? | Vaididea is responsible for the data it collects to run your account and the Platform. A Provider (such as your doctor or hospital) is responsible for your clinical records that it keeps, and Vaididea only processes those on the Provider’s instructions. Article III explains this. |
| What do you collect? | Your identity and contact details, health information you give us or a Provider records, your location when you use location features, payment and insurance details, device data, and information from sensors and cameras when you switch those features on. Article IV lists everything by role and feature. |
| Why? | To run your account, bookings, consultations, medicine and lab orders, emergency help, payments, AI features, safety and outbreak alerts. Article VI lists each purpose. |
| Do you sell my data or show me ads based on it? | No. Vaididea does not sell your personal data or Health Data, and does not use Health Data for third-party targeted advertising. |
Article I. Introduction and Scope
1.1Vaididea Healthcare Private Limited (“Vaididea”, “Company”, “we”, “us” or “our”) operates the website www.vaididea.in, the Vaididea mobile applications (including the Patient Application, the Ambulance Application and the Delivery Application) and the Provider portals (together, the “Platform”). This Privacy Policy (“Policy”) explains what personal data, including Health Data, Vaididea collects from you, how and why it is processed, with whom it is shared, how long it is kept, and the rights you have under the Digital Personal Data Protection Act, 2023 (“DPDP Act”), the DPDP Rules, 2025 (“DPDP Rules”) and other Applicable Law.
1.2This Policy is the privacy notice referred to in the Vaididea Terms and Conditions(“Terms”) and is read together with them. Terms defined in the Terms and not defined here have the same meaning here. Where this Policy gives you greater protection for your personal data than the Terms, this Policy prevails on that point. Nothing in the Terms or in this Policy reduces a right you have under the DPDP Act or any other Applicable Law.
| Question | Short answer |
|---|---|
| How does AI use my data? | AI Features may send what a request needs to third-party AI providers, some of which may process it outside India. AI models are trained or improved on your data only with your separate opt-in. Article VII explains this. |
| What happens in an emergency? | When you raise an SOS (or an automatic crash alert fires), we share your location and the medical details you chose with ambulances, hospitals, doctors and your Guardians so help can reach you. Article VIII explains this. |
| Who sees my health records? | A Provider sees them only if you allow it (or in an emergency, or where law requires), and every view of a historical or sensitive record is logged. |
| What are my choices? | You can withdraw consent, access, correct and erase your data, nominate someone, and complain to us and to the Data Protection Board of India. Article XIX explains how. |
| How do I contact you? | Write to the Grievance Officer in Article XXI. You get an acknowledgement in 24 hours and a resolution in 15 days. |
1.3This Policy applies to every User in every role: Patient, Guardian, Doctor, Hospital, Clinic, Pharmacy, Diagnostic Centre, Ambulance Operator, Blood Bank, Wellness or Gym Provider, Sahayak and Healthcare Agent. A Provider’s own processing of its patients’ clinical records, as an independent Data Fiduciary, is also governed by that Provider’s own privacy notice (see Article III).
1.4This Policy is a standalone notice. It is shown to you before or when we first collect your personal data, separately from the Terms, and you can open it again at any time from the Platform’s privacy settings.
1.5This Policy is available in English. You may ask for it, or switch it in the Platform, into any language in the Eighth Schedule to the Constitution of India that the Platform supports. If a translation is not available for a language, or the versions differ, the English version prevails, except where law requires otherwise.
1.6The DPDP Act and the DPDP Rules apply to Vaididea to the extent and from the dates on which their respective provisions come into force. Vaididea complies with applicable requirements from their effective dates and may adopt additional safeguards before those dates. Nothing in this Policy excludes or limits any right or obligation that applies under Applicable Law.
Article II. Definitions
| Term | Meaning |
|---|---|
| Personal Data | Any data about an individual who is identifiable by or in relation to that data. |
| Health Data | Information about a User’s physical, mental or reproductive health, medical history, prescriptions, laboratory results, vital signs, allergies, fitness and diet data, or biometric identifiers, which Vaididea treats as sensitive and protects with enhanced safeguards, whether or not the law classes it as a special category. |
| Data Principal | The individual to whom personal data relates. In this Policy, and in the Terms, this is the User. |
| Data Fiduciary | A person who, alone or with others, decides the purpose and means of processing personal data. |
| Data Processor | A person who processes personal data on behalf of a Data Fiduciary. |
| Consent Manager | A person registered with the Data Protection Board of India who lets a Data Principal give, manage, review and withdraw consent through an accessible, transparent and interoperable platform. |
| Processing | Any operation on personal data, including collection, recording, storage, use, sharing, disclosure, erasure or destruction. |
| Guardian | A User who has delegated, consent-based access to another User’s profile, including the parent or lawful guardian of a child or of a person with a disability, as the Terms explain. |
| Healthcare Agent | A delivery agent, sample-collection agent or other agent who uses the Delivery Application, as the Terms explain. |
| Digital Health ID | Your unified profile on the Platform, shown in the Applications as the Health Card with a QR code. |
| AI Features | Any artificial-intelligence or machine-learning function on the Platform, including the AI Symptom Checker, Disease Prediction module, AI Food and Diet Tracker, camera-based vitals estimation, other computer-vision tools and the Vaididea AI assistant. |
Article III. Our Role: Data Fiduciary or Data Processor
3.1Our role depends on who in fact decides why and how the data is processed. In the ordinary case, the allocation is as follows:
| Data | Vaididea’s role | Who carries the main duties |
|---|---|---|
| Your account, login, Digital Health ID, app usage, device data, support requests, payments through the Platform, location features, SOS and dispatch, AI Feature use, outbreak and safety analytics, and security | Data Fiduciary | Vaididea |
| Clinical records that a Provider keeps in its electronic record system hosted or managed through the Platform (consultation notes, prescriptions, reports, discharge summaries, nursing and billing records) | Data Processor, on the Provider’s documented instructions under a Data Processing Agreement | The Provider, as Data Fiduciary |
| Data that Vaididea and a Provider decide together how to use | Joint Data Fiduciaries | Each for its own duties |
3.2Where Vaididea is a Data Processor, the Provider, and not Vaididea, is responsible for the notice and consent for its own collection of that data and for answering your requests about those records. Vaididea processes that data only as the Provider lawfully instructs and as the Data Processing Agreement allows. Vaididea staff do not open a Provider’s clinical records except as the Provider instructs, or for support, security or legal reasons, and each such access is logged.
3.3If you ask Vaididea about a record that a Provider controls, we will pass your request to that Provider and tell you we have done so.
3.4When a Provider is the Data Fiduciary, you should also read that Provider’s privacy notice. A Provider’s duties are in clause 5.56 of the Terms.
Article IV. Personal Data We Collect
4.1What we collect depends on your role and the features you use. The role allocation for that data is set out in the table under clause 3.1.
Patients
| Category | What it includes | When we collect it |
|---|---|---|
| Identity and contact data | Name, date of birth, gender, phone number (for OTP login), email, address, photograph if you add one, Digital Health ID and QR code | Registration and profile |
| Verification data | Government identity documents, only where needed for verification or an insurance or scheme claim; ABHA number if you link one | When you choose to link or claim |
| Health Data | Medical history, allergies, current medicines, vital signs, laboratory and diagnostic reports, prescriptions, discharge summaries, immunisation records, and, where you use those modules, fertility, reproductive-health, pregnancy, women’s-health or mental-health records | When you enter it, when a Provider records it, or when a lab or pharmacy uploads it |
| Consultation data | Appointment details and reasons for the visit, chat and message content with Providers, and call metadata such as time and duration. Audio or video of a consultation is recorded only with the consent of everyone on the call | Booking and teleconsultation |
| AI Feature inputs and outputs | Text you type to the AI assistant or symptom analyser, symptoms you select, meal photos you upload, vitals context used to answer you, and the answers given | When you use an AI Feature |
| Fitness, diet and wearable data | Steps, heart rate, sleep, workouts and similar readings you connect through Health Connect or similar services, diet logs and food images | When you connect a source or log data |
| Camera-based vitals | Pulse, breathing rate, heart-rate variability, and wellness stress estimate worked out on your device (SpO2 pulse oximetry excluded) | When you run a vitals scan. The reading leaves your device only if you save or share it |
| Location data | Precise or approximate device location | For nearby search, Emergency Services and live tracking, delivery and collection tracking, and city-level outbreak alerts |
| Emergency data | SOS requests, their status and timing, live location during an SOS, the medical details you chose to include, crash-detection triggers and whether you cancelled them | When you or the Application raise an SOS |
| Payment, wallet and insurance data | Transaction records, billing history, wallet balance and transactions, subsidy or scheme use, insurance policy details, claim and cashless status. We do not store full card or bank-account credentials | Payments and claims |
| Orders and fulfilment data | Medicine orders, prescription images, delivery address, lab orders, home-collection slots and results | Pharmacy and laboratory orders |
| Reviews and communications | Ratings, reviews, support messages, grievance records, consent requests and notification preferences | When you use the Platform |
| Device and usage data | Device identifiers, IP address, operating system, app version, language, app-usage logs, crash reports, notification tokens and security logs | Automatically |
Guardians and family members
4.2If you add a family member or dependant, we collect their identity, contact and Health Data as you or their lawful guardian provide it, the relationship, and records of consent given or withdrawn for them. If you add a family member or emergency contact from your phone’s contacts, the Application reads your contacts only when you choose to add someone, and uses only the contact or contacts you select. Providers
4.3For Doctors, Hospitals, Clinics, Pharmacies, Diagnostic Centres, Blood Banks, Wellness and Gym Providers and their staff, we collect: identity and contact details; registration certificates, medical or professional licences, degrees, drug licences, facility and trade licences and insurance; staff sub-account details and role-based access records; availability calendars and practice details; bank, tax and GST details needed for payouts and invoices; revenue-split and payout settings; fee lists and packages; reviews received; and activity and audit logs. Ambulance Operators and drivers
4.4For Ambulance Operators and drivers we collect: identity and contact details; vehicle registration, fitness certificate, permit, motor insurance, driver licence and State EMS or ambulance registration; live location only while you are on duty or on an active job; job history, acceptances, cancellations and trip logs; payment and payout details; and call records and trip logs made for safety, quality and dispute handling, as clause 5.25 of the Terms states. Healthcare Agents and Sahayaks
4.5For Healthcare Agents and Sahayaks we collect: identity and contact details; the Provider that added or engaged you; verification and training records; task assignments, areas and routes; live location only while a task is active; handover, sample-collection and cash-collection records; and performance and incentive records the assigning Provider keeps. Category What it includes When we collect it Device and usage data Device identifiers, IP address, operating system, app version, language, app-usage logs, crash reports, notification tokens and security logs Automatically
Website visitors
4.6For visitors to www.vaididea.in we collect device and browser data, IP address, pages viewed and cookie or similar identifiers, as Article XVIII describes. Device permissions and sensors
4.7Some features need your device’s permission. You can change a permission at any time in your device settings, but a feature that needs it may then stop working.
| Permission or sensor | What we use it for |
|---|---|
| Location | Nearby hospitals, doctors, pharmacies and gyms; SOS dispatch and tracking; delivery and collection tracking; city-level outbreak alerts |
| Motion sensors (accelerometer, gyroscope) | Crash detection, only if you switch it on |
| Camera | Video consultations, camera-based vitals, food photos, QR scanning, document and prescription photos |
| Microphone | Video and audio consultations and voice features |
| Contacts | Adding a family member or emergency contact, only when you choose to |
| Notifications | Reminders, order and appointment updates, SOS status, health alerts |
| Health Connect and similar services | Reading the wearable and fitness data you connect |
| Storage and photos | Uploading reports, prescriptions and images you choose |
Article V. How We Collect Data
5.1We collect personal data:
- (a)Directly from you when you register or use a feature.
- (b)From a Provider’s staff who enter data while giving you care, such as a nurse recording vitals or a laboratory uploading a report.
- (c)Automatically from your device, its sensors, application logs and cookies.
- (d)From Guardians who add or manage a dependant.
- (e)From third parties you have connected, such as insurers, third-party administrators, payment aggregators, wearable services and government health registries including the Ayushman Bharat Digital Mission.
- (f)From Healthcare Agents and Ambulance Operators who record the steps of a delivery, collection or trip.
5.2You decide what health information to enter, but some features work properly only with accurate input. Wrong input can affect AI output and emergency triage (clause 5.2 of the Terms).
Article VI. Why We Process Your Data
6.1Vaididea processes personal data only for the specified purposes below, or those that apply to your role and use of the Platform. For each purpose we state the lawful basis: consent, or a legitimate use that Section 7 of the DPDP Act allows (such as a medical emergency or compliance with law).
| Purpose | Main data used | Basis |
|---|---|---|
| Create and run your account, login and Digital Health ID | Identity, contact, device | Consent |
| Book appointments, manage queues and tokens, send reminders, and run other operational modules in Schedule A to the Terms | Identity, appointment, location, communications | Consent |
| Show Doctors and Providers in search results and rank them, including personalising results using the chronic conditions you entered and your past consultations on the Platform | Profile, Health Data you entered, consultation history, location, ratings | Consent |
| Let a Provider see your records for your care | Health Data | Your consent, each time or as you grant it |
| Run teleconsultations, e-prescriptions and chat | Identity, Health Data, communications | Consent |
| Take, deliver and track medicine and laboratory orders, home delivery and home sample collection | Identity, address, prescription, order, location during a task | Consent |
| Raise and route an SOS, dispatch ambulances, notify hospitals, doctors and Guardians, and track the trip | Identity, live location, medical details you chose, trip data | Consent, and legitimate use for a medical emergency |
| Detect a possible crash and start an automatic SOS countdown | Motion-sensor data, location | Consent |
| Process payments, wallet, subsidies, billing, refunds and insurance claims | Payment, insurance, billing | Consent, and legitimate use for legal obligations |
| Produce AI Feature output for you | Your inputs, vitals context | Consent |
| Train, validate or improve AI models and support research with de-identified or aggregated data | De-identified or aggregated Health Data | Your separate opt-in only |
| Produce outbreak and public-health analytics and send localised advisory alerts | Non-identifying signals and city-level location | Consent, which you can withdraw (Article IX) |
| Verify Providers, operators and agents and keep them current | Verification and licence data | Consent, and legitimate use for legal obligations |
| Keep the Platform secure, prevent fraud and misuse, and keep access logs | Device, usage, security logs | Consent, and legitimate use for security and law |
| Send service messages (OTPs, alerts, receipts) | Contact, device | Consent |
| Send marketing messages | Contact, preferences | Your separate opt-in only, which you can withdraw |
| Answer your requests, support queries and grievances | Contact, communications | Consent |
| Comply with law, including medical-record, tax and reporting duties, and respond to lawful orders | Records as required | Legitimate use for legal obligations |
6.2We do not use your personal data for a purpose that is not listed here unless we first tell you and, where the law requires, ask for your consent.
6.3Vaididea does not sell personal data or Health Data to any third party, and does not use Health Data to show you third-party targeted advertising.
Article VII. AI Features and Your Data
7.1The AI Features include the AI assistant (chat), the symptom analyser and Disease Prediction module, the AI Food and Diet Tracker (including food-photo recognition), and camera-based vitals. They give general, probabilistic information. They are not medical advice, as Article VI of the Terms explains.
7.2To answer you, an AI Feature uses what you give it: your typed questions, symptoms you select, meal photos, and, where it helps the answer, recent vitals or other context from your own profile. It also keeps the answer it gave.
7.3Third-party AI providers and Google Play Data Safety. To produce some answers, Vaididea’s backend servers send the text, voice intake transcript, symptom questionnaire or health context that a request needs to a third-party AI model provider: Groq, Inc., Hugging Face, Inc. and OpenAI, LLC. Your device does not send this data to those providers directly. In accordance with Google Play's Data Safety Declaration, health data processed through these providers is declared as “Shared” with vetted third-party processors solely to provide core application functionality. Vaididea limits what is sent to what the request needs and engages each provider under written terms prohibiting training on user data (see clause 13.4). Some of these providers may process the data outside India (see Article XIV).
7.4Training and research. Vaididea trains or improves AI models, and uses data to test and validate AI Features or for health research and public-health work with academic, medical-college, non-governmental and government partners, only with de-identified or aggregated data and only if you have given the separate opt-in in your consent settings. Research partners are bound by written terms that forbid re-identification and misuse. You can withdraw this opt-in at any time without losing any Service. Withdrawal works going forward (clause 10.4). The one exception is the outbreak analytics in Article IX, which has its own consent.
7.5Camera-based vitals and Medical Disclaimer. The reading is worked out on your device. Nothing leaves your device unless you save the reading to your profile or share it, and a saved reading is then Health Data like any other. Medical Disclaimer: Vaididea is not a certified medical device and is not intended for the diagnosis, cure, mitigation, treatment or prevention of any disease or medical condition. In accordance with Google Play Health App policies, camera-based estimations do not measure blood oxygen saturation (SpO2) and are not intended for clinical pulse oximetry. All camera-derived signals are wellness and preliminary indicators only. Always consult a qualified registered medical practitioner for any clinical diagnosis or medical emergency.
7.6No automated decisions about your access. AI output is information for you and for your Doctor. Vaididea does not use AI output on its own to decide whether you may use a Service, to refuse an emergency request or to rank you against other Users. Where AI assists a Provider, the Provider’s registered medical practitioner remains responsible for clinical decisions.
7.7Voice features. Voice input is turned into text so the Application can act on it. A voice feature does not keep your audio longer than needed to process it, unless a feature you use says otherwise and you have agreed (for example, a recorded consultation).
7.8Safety review. Vaididea keeps logs of AI requests and outputs for safety, bias and error review, as clause 6.6 of the Terms provides. Those logs are kept for the period in Article XV and are not used to train models unless you have given the opt-in in clause 7.4.
7.9Google Play Health Connect Policy and Limited Use Declaration. Our use and transfer to any other app of information received from Health Connect will adhere to the Google Play Health Connect Permissions policy, including the Limited Use requirements: (a) Permitted Purpose: We access and process Health Connect data (steps, heart rate, sleep logs, workouts, calories) solely to provide and improve user-facing wellness and health monitoring features of the application and to facilitate direct consultation sharing with your treating doctor upon your explicit consent. (b) No Sale of Data: We never sell Health Connect data to third parties, data brokers, or information resellers under any circumstances. (c) No Advertising: We never use or transfer Health Connect data for serving personalized, retargeted, or interest-based advertising. (d) No Human Access: No human reads or accesses your raw Health Connect data unless you have given explicit prior consent for a specific clinical consultation, it is required for platform security or legal compliance, or it is aggregated and de-identified for public health analytics in accordance with Article IX.
7.10Online Pharmacy Licensing, Medicine Delivery, and Prescription Verification. In compliance with Google Play Prescription Drugs Policy, the Drugs and Cosmetics Act, 1940, and the Drugs and Cosmetics Rules, 1945: (a) Licensed Pharmacy Dispensation: All physical medicines and pharmaceutical products ordered through the Platform are dispensed exclusively by licensed retail pharmacies possessing valid Form 20 and Form 21 retail drug licenses issued by State Drug Licensing Authorities. VaidIdea does not manufacture, wholesale, or directly sell scheduled pharmaceuticals. (b) Mandatory Prescription Verification: In accordance with Indian law and Google Play safety standards, prescription drugs (including Schedule H and Schedule H1 drugs) will not be dispensed without a valid, legible digital prescription or uploaded physical prescription issued by a Registered Medical Practitioner (RMP). Every prescription is independently verified by a qualified registered pharmacist employed by the fulfilling pharmacy prior to dispensation. (c) Prohibited Drugs: Schedule X medications, habit-forming narcotics, psychotropic substances under the NDPS Act, and unapproved investigational drugs are strictly barred from online ordering. (d) Delivery Security: Delivery partners transport medications in tamper-evident sealed packages and verify recipient identity via one-time password (OTP) or digital signature at handover.
Article VIII. Emergency Services, SOS and Crash Detection
8.1When an SOS is raised, Vaididea collects your name, contact number, live location (updated during the emergency), the medical details you chose to include (for example blood group or allergies), the SOS status and times, and trip data from the operator or hospital.
8.2During an active SOS, the Application may share that data as follows. The recipients and the data are limited to what the emergency needs.
| Recipient | What they receive | Why |
|---|---|---|
| Ambulance operators alerted nearby, and the operator who accepts | Name, contact number, live location, the medical details you chose, status | To decide whether to accept and to reach you |
| A Hospital running its own fleet (Direct Hospital SOS), and the receiving hospital and nearby hospitals | Expected arrival time, live location, the medical details you chose | To prepare for your arrival |
| Nearby Doctors | An alert with the information needed to prepare | To be ready to help |
| Your Guardians and emergency contacts | An SOS alert, live location and status updates | So the people you trust know and can help |
| Vaididea dispatch team | The SOS record | To monitor dispatch, support you and keep the service safe |
8.3We process SOS data on the basis of your consent and, where it applies, the legitimate use of responding to a medical emergency under Section 7 of the DPDP Act. You can choose which medical details are included in your settings.
8.4Someone else’s emergency. Anyone may raise an SOS for another person. We collect the location of the person who needs help and the details of the person who raised the SOS. No one has to pay or give personal details before help is dispatched.
8.5Crash detection. If you switch on crash detection, the Application uses your phone’s accelerometer and gyroscope to decide whether a serious crash may have happened. If it detects one, it starts a short countdown with an alarm and sends an SOS unless you cancel. Vaididea keeps a record of the trigger (time, location and whether you cancelled), not a continuous record of your movement. You can switch crash detection off at any time and it stops using the sensors for this purpose.
8.6Hospital fleets. Where a Hospital runs its own ambulances through the Hospital portal, the Hospital is the Data Fiduciary for its fleet, driver and dispatch records, and Vaididea is its Data Processor for them.
8.7Operators. The Ambulance Application collects an operator’s location only while on duty or on an active job, and limits the patient data an operator sees to what the trip needs.
Article IX. Public Health and Outbreak Analytics
9.1Vaididea monitors for possible disease outbreaks so that it can send precautionary advisory alerts. In addition to reports from Hospitals and Diagnostic Centres, it may use signals from the Patient Application: text typed to the AI assistant or symptom analyser, reasons given when booking an appointment, diagnoses recorded by Doctors, SOS requests and data from connected wearables.
9.2Each signal is reduced to non-identifying fields (such as city, age band, gender and a symptom or disease category) when it is collected. Your name, phone number, exact address and account identifier are not part of it. A diagnosis recorded by a Doctor is used only where the Provider has authorised it.
9.3Your choice. This use is based on your consent, which you can give or decline separately and withdraw at any time in your settings. After withdrawal, your later signals are not included. Signals already reduced to non-identifying fields cannot be traced back to you and are not removed.
9.4Alerts. Advisory alerts go to Users within a defined area and rest on statistically aggregated, de-identified data. They are not diagnoses and never identify or describe the health of any identifiable person.
9.5Vaididea does not publish or alert at a level of detail that could identify a person, takes extra care with any result about a small group, and does not try to re-identify the data. Vaididea may share aggregated, de-identified outbreak signals with public-health authorities where law requires or permits.
Article X. Consent, Legitimate Uses and Managing Your Choices
10.1Unless a legitimate use under Section 7 of the DPDP Act applies, Vaididea processes personal data only with your free, specific, informed, unconditional and unambiguous consent, asked for through a clear and itemised notice. This Policy and the consent screens in the Platform are that notice.
10.2Optional uses are asked for separately and you can say yes or no to each one. Saying no to an optional use does not stop you using the core Services. The separate consents are: Provider access to your Health Data (a request each time, or a standing permission you set) Location Camera, microphone, contacts and sensor features, including crash detection AI Feature use Using de-identified or aggregated data to train AI models and for research (opt-in) Outbreak analytics (Article IX) Recording a consultation (needs everyone on the call) Assisted access by a Sahayak or Healthcare Agent Marketing messages (opt-in)
10.3We rely on legitimate uses only where the law allows, mainly responding to a medical emergency and complying with a legal obligation.
10.4Withdrawing consent. You can withdraw consent at any time in the Platform’s privacy and consent settings, which stay available whether or not a Consent Manager is in use. Withdrawal is as easy as giving consent. It works going forward only. It does not affect processing already done, and it does not undo a clinical transaction, prescription, billing record or statutory record that is already complete. If you withdraw a consent that a feature needs, that feature may stop working. Once the Consent Manager framework under the DPDP Rules applies, you may also manage consent through a registered Consent Manager.
10.5We keep a record of each consent you give or withdraw, with the version of the notice, the date and time, and how it was given.
10.6Consent given by assisted, voice or low-literacy methods, such as an OTP, a spoken confirmation or a thumb or biometric confirmation, is valid if the Platform’s record shows it was given. The confirmation is kept as a consent record. You can withdraw it at any time.
Article XI. Children, Persons with Disabilities, Guardians and
Assisted Access
11.1A person under eighteen (18) can use the Platform only through a verified Guardian account. Before processing a child’s personal data, Vaididea obtains verifiable consent from the parent or lawful guardian through the Guardian linking and verification process on the Platform, as Section 9 of the DPDP Act and the DPDP Rules require. The same applies to a person with a disability who has a lawful guardian.
11.2Vaididea does not track or monitor a child’s behaviour and does not direct targeted advertising at a child, except as the DPDP Act and Rules allow. A Guardian can review, change or withdraw consent for a child at any time.
11.3A Guardian’s access to a dependant’s records is only to manage that person’s care, and it is logged and subject to audit.
11.4The DPDP Rules exempt some processing of a child’s data by clinical establishments and healthcare professionals for health services from the verifiable-consent requirement. That processing is the Provider’s responsibility as Data Fiduciary and does not change what Vaididea does for its own processing.
11.5If we learn that a person under eighteen has registered without a Guardian, we will restrict the account and ask for Guardian verification before going further.
11.6Assisted access. A Sahayak or Healthcare Agent can help you register, book, record vitals or join a consultation only with your informed consent, given in a way the Platform offers, and after explaining in your language what is being done. They can use only the access you grant and must not keep or share your Health Data. On shared devices, sessions can expire and users must log out after use.
Article XII. Sensitive Categories of Data
12.1Fertility and IVF, pregnancy and women’s-health data, mental-health data, information about HIV status and other conditions that carry stigma, and biometric confirmations used for consent need extra care. For these, Vaididea applies stricter access controls, encryption, enhanced consent controls and fuller access logging.
12.2A Provider must keep this information confidential as the HIV and AIDS (Prevention and Control) Act, 2017, the Mental Healthcare Act, 2017 and other law require, and must not discriminate against you because of it (clause 5.66 of the Terms).
12.3Vaididea does not use fertility, reproductive, mental-health or HIV-related data for marketing, and does not use it in outbreak analytics.
Article XIII. Disclosure and Sharing of Data
13.1We disclose personal data, including Health Data, only to the following, and only as far as needed.
| Recipient | When and what |
|---|---|
| A Provider you authorise | Your records, as you grant access, by showing your Health Card QR, or through a consent request. Every view of a historical or sensitive record is logged and the log is available to you on request |
| A Guardian | A dependant’s data, to manage that person’s care |
| SOS recipients | As Article VIII sets out |
| Healthcare Agents, Ambulance Operators and delivery partners | The details a task needs, such as name, address, phone, order or sample details and location during the task |
| Pharmacies, Diagnostic Centres and Hospitals you order from | The details needed to fulfil your order or visit |
| Insurers and third-party administrators | The details needed for a claim or cashless request you start |
| Payment aggregators, gateways and banks | The details needed to take a payment or issue a refund |
| Government health registries such as the Ayushman Bharat Digital Mission, and public-health authorities | When you have connected the integration, or where law requires or permits |
| Service providers (sub-processors) | As clause 13.4 sets out |
| Courts, regulators and law-enforcement authorities | Where Applicable Law or a valid legal process requires. Unless the law forbids it, we tell you before or soon after, and share only what is required |
| A successor to Vaididea | In a merger, acquisition or sale of assets, only on terms that protect your data at least as well as this Policy, and we will tell you |
13.2No sale and no advertising. Vaididea does not sell personal data or Health Data, does not share it with data brokers, and does not use Health Data for third-party targeted advertising. Aggregated or de-identified data is shared only as clause 7.4 and Article IX set out.
13.3When you grant a Provider access, the Provider becomes responsible for the data it receives and must use it only for the purpose you consented to and in line with medical confidentiality.
13.4Service providers. Vaididea uses service providers for hosting and storage, maps, push notifications, AI models, messaging, video calls, payments and analytics. Each is bound by written confidentiality and data-protection terms that give the same protection, and a list is available on request. As at the effective date, the categories and providers include:
| Category | Purpose | Providers |
|---|---|---|
| Hosting, database and file storage | Running the Platform and storing data locally in India (ap-south-1 Mumbai) | Supabase (Mumbai, India) and Amazon Web Services S3 (AWS ap-south-1 Mumbai, India) |
| Maps and location | Nearby search, routing and tracking | Google Maps Platform |
| Push notifications | Alerts and reminders | Firebase Cloud Messaging |
| AI models (Google Play Data Safety: Shared) | Producing AI Feature output, clinical voice intake transcription, triage assistance, and natural language medical summaries (clause 7.3) | Groq, Inc., Hugging Face, Inc., OpenAI, LLC (zero-training, encrypted server-to-server) |
| Video calls | Teleconsultation (the call itself runs between participants using WebRTC) | Our signalling and relay servers |
| Payments | Collection, refunds and payouts | RBI-authorised payment aggregators and PCI-DSS-compliant gateways |
| Messaging | OTPs, SMS, WhatsApp and email | Telecom and messaging partners |
Article XIV. Cross-Border Transfer of Data
14.1Primary Hosting in India. All primary health data, patient records, and core databases are stored on cloud servers located within the territory of India (Amazon Web Services AWS ap-south-1 Mumbai region and Supabase India), satisfying Indian data localization mandates under the DPDP Act, 2023. Where a specific feature uses a service provider that processes data outside India, including the third-party AI providers in clause 7.3, the transfer or processing happens only as the DPDP Act and Central Government notifications permit, and only the data the request needs is sent ephemerally over encrypted channels.
14.2We do not transfer personal data to a country or territory that the Central Government has restricted by notification.
Article XV. Data Retention and Erasure
15.1Vaididea keeps personal data only as long as the purpose needs or Applicable Law requires. After that, it is erased or anonymised. A legal hold, an active grievance, an audit or a legal proceeding can extend a period. Backups are overwritten in the normal backup cycle.
15.2Retention periods:
| Data | How long we keep it |
|---|---|
| Account and identity data | While your account is active. After closure, registration information is kept for 180 days, as the Intermediary Guidelines Rules require, and then erased or anonymised unless law or a dispute requires longer |
| Health Data in your Digital Health ID | Until you ask for erasure or close your account, subject to clause 15.3 and any legal retention |
| Clinical records a Provider keeps on the Platform | As the Provider instructs and the law requires (clause 15.3) |
| Consent records | Three (3) years after the consent ends, or longer if needed to answer a claim |
| Security, access and activity logs, including usage logs and crash reports | One (1) year, as the DPDP Rules require for logs used to detect unauthorised access, or longer where other law requires |
| AI assistant and symptom history | Until you delete it or close your account. Logs of AI requests and outputs kept for safety review are kept for one (1) year |
| Camera-based vitals | On your device. A reading you save is Health Data like any other |
| Precise SOS and trip location trail | Ninety (90) days from dispatch, after which only anonymised, aggregated data is kept |
| SOS event record (time, status, parties, outcome, without the location trail) | Three (3) years, for safety and dispute handling |
| Ambulance operator duty-location data | Ninety (90) days |
| Operator call records and trip logs | One (1) year, or longer if a dispute or complaint is open |
| Healthcare Agent task and location data | One (1) year |
| Payment, wallet, billing and tax records | The period tax and company law require, generally between six and eight years |
| Medicine orders and prescription images | The period the fulfilling Pharmacy’s recordkeeping duties require |
| Provider and operator verification documents | While the Provider is listed and for three (3) years after delisting, or longer if law or a dispute requires |
| Support and grievance communications | Three (3) years from resolution |
| Marketing preference data | While your account is active and for one (1) year after |
| Records of removed content | 180 days, or longer if a court or authority requires |
| Outbreak signals | Held only in non-identifying, aggregated form, with no time limit |
15.3Clinical records. Clinical records, including discharge summaries and statutory documents, are kept for at least the period set by the clinical-establishment, medical- record and other laws that apply, which differs by type of record and by State, and subject to each Provider’s own duties. A Provider’s own duty to keep records continues even if you withdraw consent or close your account.
15.4Erasure and notice. You can ask for erasure at any time (Article XIX). Where the DPDP Rules require advance notice before we erase personal data for inactivity, we give you that notice, and you can log in or ask us to keep the data before it is erased.
15.5If you close your account, data we must keep by law is kept for that period only and is not used for any other purpose.
Article XVI. Data Security
16.1Vaididea uses reasonable security safeguards suited to the sensitivity of the data, including: encryption of Health Data in transit and at rest; role-based access control, so that Provider staff see only data within their role and your consent; separate sub- accounts, with one login for each person; audit logs of access, especially to historical or sensitive records; monitoring and regular review of logs to detect unauthorised access; backups and measures to keep the Platform running after a failure; periodic security review and vulnerability assessment; confidentiality duties for staff and written security obligations for service providers; and session controls, including session expiry on shared devices.
16.2No method of storage or transmission is completely secure, and we cannot guarantee absolute security. You help by keeping your login credentials, OTPs and Health Card confidential and by telling us at once about any unauthorised access. Nothing in this Article limits liability that cannot be excluded under clause 14.4 of the Terms.
16.3You can report a security weakness to the Grievance Officer. Clause 11.9 of the Terms protects good-faith reporting.
Article XVII. Personal Data Breach
17.1If a personal data breach affects data for which Vaididea is the Data Fiduciary, Vaididea will contain and remedy it and will tell each affected User without delay. The notice will say, in plain language, what happened, its nature, extent, timing and location, the likely consequences for you, what we have done and are doing, what you can do to protect yourself, and whom to contact.
17.2Vaididea will tell the Data Protection Board of India without delay, and will send a detailed report within seventy-two (72) hours (or any longer period the Board allows). It will also follow the directions of the Indian Computer Emergency Response Team (CERT- In), including its reporting periods.
17.3If a breach affects clinical records that a Provider controls, Vaididea tells that Provider without delay. The Provider, as Data Fiduciary, carries the duty to tell you and the Board, and Vaididea helps. A Provider must tell Vaididea within twenty-four (24) hours of any breach affecting data on the Platform (clause 5.56 of the Terms).
17.4These duties apply as the DPDP Act and Rules apply from time to time. Until the relevant provisions are in force, Vaididea follows the same standard as a matter of practice.
Article XVIII. Cookies, Tracking Technologies and
Communications
18.1The website and Applications use cookies, software development kits (SDKs), device identifiers and similar tools. They fall into three groups: those needed to run the Platform and keep it secure; those that remember your preferences, such as language; and those that help us understand use of the Platform through aggregated analytics, including crash reports. Tools that are not strictly needed are used only with your consent.
18.2Vaididea does not use cookies or SDKs to show you third-party targeted advertising based on Health Data. You can control cookies in your browser or device settings and in the Platform’s privacy settings. Blocking some tools may stop some features from working.
18.3Service messages. We send service messages that you need, such as OTPs, appointment and order updates, SOS status, receipts and security alerts, by SMS, WhatsApp, calls, email and app notifications.
18.4Marketing messages. We send marketing messages only if you have separately opted in. You can opt out at any time in your settings or by following the instructions in the message, and service messages continue. Providers must not send unsolicited commercial messages to Patients and must follow TRAI rules.
Article XIX. Your Rights and How to Use Them
19.1Subject to the DPDP Act and Rules, you have the right to: Access: get a summary of the personal data we process about you and what we do with it, and the identities of the other Data Fiduciaries and Data Processors we have shared it with, with a description of the data shared. You can also see who viewed your historical or sensitive records. Correction, completion and updating: correct inaccurate data, complete incomplete data and update data. Erasure: ask us to erase personal data you no longer want us to hold, unless we must keep it by law (Article XV). Withdraw consent: at any time, as Article X sets out. Grievance redressal: complain to the Grievance Officer and then, if you are not satisfied, to the Data Protection Board of India. Nominate: name another person to use these rights for you if you die or cannot act, through the Platform.
19.2You can also ask for a copy of your records through the Platform or the Grievance Officer. Where a Provider controls a record, we pass your request to that Provider (clause 3.3).
19.3Account Deletion & How to use your rights. You may delete your account and request erasure of associated personal data at any time: (a) In-App: Open Profile → Settings → Delete Account in the Vaididea Mobile Application; (b) Web Portal: Submit a deletion request online without installing the application at https://vaididea.in/account-deletion (or submit the official Google Form linked on that page); or (c) Write directly to the Grievance Officer at privacy@vaididea.in. Non-statutory personal data is permanently deleted within 48 hours. Where medical records or consultation data must be kept by statutory requirement (Telemedicine Practice Guidelines, 2020 or Drugs and Cosmetics Act), such records are isolated and retained strictly for the statutory duration (Article XV). We do not charge for deletion or data requests.
19.4How quickly. We acknowledge your request within twenty-four (24) hours and resolve it within fifteen (15) days. In every case we respond within the period the DPDP Rules allow, which is no more than ninety (90) days for a grievance. If we cannot do something the law prevents, we tell you why.
19.5Your duties. The DPDP Act asks you to comply with the law, not to impersonate another person, not to hide material information when giving identity details, not to make a false or frivolous complaint and to give only verifiably authentic information when you ask for correction or erasure.
Article XX. Provider, Operator and Agent Data
20.1Providers as Data Fiduciaries. A Provider that keeps its patients’ clinical records is the Data Fiduciary for them. It must get valid consent, keep reasonable security safeguards, honour Data Principal requests, sign the Data Processing Agreement, tell Vaididea within twenty-four (24) hours of any breach, and cooperate with the Data Protection Board and Vaididea.
20.2Staff accounts. A Hospital, Clinic or other Provider must give each staff member their own login, restrict access by role and is responsible for its staff and sub-accounts. Vaididea logs their access.
20.3Public profile. A Provider’s public listing shows information such as name, registration number, specialisation, fees, availability and reviews. A Provider may update or remove its profile through the Platform, and Vaididea may keep a copy where law, a dispute or patient records require it.
20.4Payouts, splits and ledgers. Bank, tax and GST details, revenue-split settings, payout records and ledgers are visible only to the parties to that arrangement and to Vaididea, and are shared with payment partners only as needed to settle payouts.
20.5Ambulance Operators. We collect an operator’s location only while on duty or on an active job, may record calls and trip logs for safety, quality and dispute handling, and show an operator only the patient data a trip needs.
20.6Healthcare Agents. We share an agent’s live location with the Patient and the assigning Provider only while a task is active.
20.7Provider data exit. On termination, a Provider can download the records and patient data it controls within ninety (90) days, in a standard machine-readable format, after which the data is erased or anonymised as Article XV provides.
Article XXI. Grievance Officer and Contact
21.1In line with the Information Technology Act, 2000, the Intermediary Guidelines Rules, the Consumer Protection (E-Commerce) Rules, 2020 and the DPDP Act, Vaididea has appointed a Grievance Officer to handle complaints about the Platform and the processing of personal or Health Data. The same officer is the person who answers Data Principals’ questions about that processing. If Vaididea is notified as a Significant Data Fiduciary, it will also appoint a Data Protection Officer as the DPDP Act requires.
| Contact detail | Information |
|---|---|
| Grievance Officer | [Name], [Designation] |
| [grievance@vaididea.in] | |
| Postal address | [Registered office address] |
| Response timeline | Acknowledgement within twenty-four (24) hours; resolution within fifteen (15) days (and within any longer period consumer law allows for e-commerce matters) |
21.2Complaint help in regional languages is available through the Application or a Sahayak.
21.3If you are not satisfied with our reply, you can complain to the Data Protection Board of India about a personal data matter, and to a Consumer Disputes Redressal Commission about a service matter.
Article XXII. Changes to this Policy
22.1Vaididea may update this Policy for changes in law, features or business practice. We notify a material change through the Platform or to your registered email or phone at least fifteen (15) days before it takes effect. A change that widens how your Health Data is used needs your fresh consent. If you disagree with a change, you may stop using the Services and ask for erasure of your data.
22.2Vaididea keeps earlier versions of this Policy and gives you a copy of the version that applied to you on request. At least once a year, Vaididea reminds Users of this Policy and any changes.
Article XXIII. Governing Law
23.1This Policy is governed by the laws of India, including the DPDP Act and the Information Technology Act, 2000. Disputes about this Policy follow Article XVII of the Terms. Nothing in this Policy takes away your right to complain to the Data Protection Board of India or to approach a Consumer Disputes Redressal Commission.