1. Introduction
Doctors Vedika Healthcare Platform Pvt. Ltd. ("Doctors Vedika", "we", "our", or "us") operates the Doctors Vedika mobile application, website, and related healthcare services (collectively, the "Platform").
This Privacy Policy explains how Doctors Vedika collects, uses, stores, protects, and shares personal and healthcare-related information when you use the Doctors Vedika Platform.
By using Doctors Vedika, you acknowledge that you have read and understood this Privacy Policy.
2. About Doctors Vedika
Doctors Vedika is operated by Doctors Vedika Healthcare Platform Pvt. Ltd., having its registered office in Hyderabad, Telangana, India.
Doctors Vedika provides healthcare-related digital services, including doctor discovery, appointment booking, doctor and patient profiles, consultation management, medical record management, consultation transcription and summarization, and related healthcare services.
3. Eligibility
Doctors Vedika is intended for users who are 18 years of age or older.
By creating an account or using the Platform, you confirm that you are at least 18 years old.
Doctors Vedika does not knowingly permit persons under 18 to independently create or use an account.
4. Information We Collect
Patient Information
Full name, email address, mobile number, date of birth, gender, address, profile photograph, emergency contact information, blood group, and other information voluntarily provided by the patient.
Email/password authentication is provided through Supabase Authentication. Patients may also use supported Google/Gmail authentication. Doctors Vedika currently does not use mobile-number or OTP-based authentication.
Doctor Information
Doctor's name, email address, phone number, profile photograph, qualification, specialization, registration/licence number, hospital/clinic information, professional experience, medical certificates, licence certificates, and identity verification documents including Aadhaar where required.
Doctor verification documents are used for administrative and verification purposes. Doctor Aadhaar, certificates, and other identity documents are not displayed to patients. A doctor's applicable licence/registration number may be displayed to patients.
5. Appointment Information
When a patient books an appointment, we may store patient details, doctor details, hospital/clinic, appointment date, appointment time, appointment status, symptoms provided by the patient, disease/condition information provided by the patient, and other information required for appointment management.
6. Health and Medical Information
Doctors Vedika may process healthcare-related information including symptoms, diseases and medical conditions, medical history, consultation information, doctor's notes, prescriptions, consultation transcripts, consultation summaries, medical reports, laboratory reports, medical images, scanned documents, and other healthcare information provided through the Platform.
7. Medical Records
Authorized Doctors Vedika administrators may upload medical records through the administration platform. These may include PDF reports, laboratory reports, prescriptions, medical images, scanned documents, and other healthcare-related documents.
Relevant medical records may subsequently be made available to authorized doctors for healthcare purposes.
Medical files are securely stored using Supabase infrastructure.
8. Profile Photographs
Users may upload profile photographs. Profile photographs are stored using Supabase Storage.
Depending on the user's role and Platform functionality, profile photographs may be visible to the patient, the relevant doctor, and authorized Doctors Vedika administrators.
9. Consultation Recording
Doctors Vedika provides an optional consultation recording feature for doctors.
Recording is not automatic, is started only when the doctor actively selects the recording option, and requires applicable consent before recording begins.
The consultation audio is temporarily stored on the device while recording is in progress. After the doctor stops the recording, the audio is processed for transcription.
The original audio is not permanently stored in the Doctors Vedika database. After applicable processing, the temporary audio file is automatically deleted from the device.
10. AI Transcription and Summarization
Doctors Vedika uses third-party AI services to provide consultation transcription and summarization.
Sarvam API
Consultation audio may be processed through the Sarvam API to convert speech into text. The consultation audio is not permanently stored by Doctors Vedika. Based on our current implementation and service configuration, Sarvam does not retain the consultation data submitted for this transcription functionality.
Google Gemini API
Consultation transcripts may be processed through the Google Gemini API to generate a consultation summary. The resulting transcript and summary may be stored in Doctors Vedika's database as part of the consultation record.
Consultation transcripts and summaries may be accessible to the relevant patient, the relevant doctor, and authorized Doctors Vedika administrators.
11. Hospital Locations
Doctors Vedika does not collect or track the user's live location.
The Platform may display hospital addresses or location links. When a user selects a hospital location link, they may be redirected to Google Maps or another supported mapping application.
Doctors Vedika does not obtain or store the user's live location through this functionality.
12. Telephone Communication
Doctors Vedika may display hospital, doctor, or reception/front-desk telephone numbers.
When the user selects the number, the device's default phone application may open.
Doctors Vedika does not provide in-app calling and does not record or monitor calls made through the device's native phone application.
13. Notifications
Doctors Vedika provides notifications inside the application. These may relate to appointments, consultations, account activity, healthcare service updates, and other Platform activities.
Doctors Vedika currently does not send these notifications to the phone's system notification panel when the application is closed.
14. Payment Information
Doctors Vedika currently does not process payments through the application.
Patients can currently book appointments, but payment functionality has not yet been integrated.
Therefore, Doctors Vedika does not currently collect payment card, banking, UPI, or other payment credentials through the Platform.
If payment functionality is introduced in a future version, this Privacy Policy will be updated as appropriate.
15. How We Use Information
Create and manage accounts; authenticate users; manage patient and doctor profiles; facilitate appointments; manage consultations; maintain healthcare records; process medical information; transcribe consultations; generate consultation summaries; allow authorized doctors to access relevant patient information; allow authorized administrators to manage the Platform; provide notifications; provide customer support; maintain Platform security; improve Platform functionality; detect unauthorized activity; and comply with applicable laws and regulations.
16. How We Share Information
Doctors Vedika does not sell personal or health information.
Information may be shared or made accessible when necessary for providing the Platform, including with relevant doctors, authorized Doctors Vedika administrators, technology providers such as Supabase, AWS, Sarvam API, Google Gemini API, Google Maps, and legal or regulatory authorities where required or permitted by law.
17. Third-Party Services
Supabase is used for authentication, database services, and secure file storage.
Amazon Web Services (AWS) is used for backend APIs, servers, business logic, and supporting infrastructure.
Sarvam API is used for consultation transcription.
Google Gemini API is used for consultation summarization.
Google Maps may be used when users choose to open hospital location links.
Third-party services are subject to their respective terms and privacy practices.
18. Data Security
Doctors Vedika uses reasonable technical and organizational measures to protect personal and healthcare information.
Our infrastructure uses services including AWS and Supabase and includes applicable security controls such as secure authentication, access controls, role-based access, secure cloud infrastructure, secure data transmission, SSL/TLS, restricted administrative access, and secure database and storage configurations.
No electronic system can be guaranteed to be completely secure.
19. Data Retention
Doctors Vedika retains personal and healthcare information for as long as reasonably necessary to provide services, maintain healthcare and consultation records, meet legal and regulatory requirements, resolve disputes, maintain security, enforce agreements, and protect legitimate interests.
The retention period may vary depending on the type and purpose of the information.
When information is no longer required, reasonable steps will be taken to delete, anonymize, or securely dispose of it, subject to applicable legal and regulatory requirements.
20. Your Privacy Rights
Subject to applicable law, users may request access to their personal information, correction of inaccurate information, deletion of personal information, information about how their information is processed, and resolution of privacy concerns.
Requests can be made through support@doctorsvedika.com. Identity verification may be required before processing certain requests.
21. Children's Privacy
Doctors Vedika is intended for users 18 years of age or older.
We do not knowingly permit persons under 18 to independently create or use Doctors Vedika accounts.
22. International Processing
Our third-party infrastructure and service providers may process information in locations outside the user's state or country.
We take reasonable measures to ensure appropriate safeguards are applied to such processing where required.
23. Changes to This Privacy Policy
We may update this Privacy Policy to reflect changes in Platform functionality, data processing, third-party services, security practices, or legal requirements.
The Last Updated date will be changed when this policy is updated.