Privacy Policy

1. What Data We Collect

We collect only the minimum data necessary for the platform to function. The table below lists every category of data we collect, from whom, and why.

Data	Collected From	Purpose
Patient full name	Patient (entered at booking)	To display name at reception and doctor consultation room when token is called
Patient age	Patient (entered at booking)	Clinical queue categorization (pediatric, geriatric, general)
Patient sex	Patient (entered at booking)	Clinical routing (e.g., specialized consultation rooms, gender-specific queues where applicable)
Mobile phone number	Patient (entered at booking)	OTP verification to prevent fake bookings; SMS queue alerts; patient session identification
Email address (optional)	Patient (optional field at booking)	Sending booking confirmation email if patient opts to provide it
Home address / locality (optional)	Patient (optional field)	Stored in patient profile for receptionist reference; not used for tracking or profiling
Visit type	Patient (selected at booking)	Queue prioritization (e.g., emergency vs. general consultation vs. re-consultation)
Token number & queue position	Generated by system	Core queue management; displayed to patient on tracking screen and waiting hall TV
Consultation fee amount & payment mode	Entered by receptionist	Reception counter record of fee collected; not transmitted externally
Clinic name, doctor details, operating hours	Clinic operator (entered during onboarding)	Displayed to patients when they select a clinic to book; powers the queue engine
Clinic admin PIN (hashed)	Clinic operator	Authentication for clinic staff to access the reception and doctor console
IP address & browser metadata	Automatically from all users	Firebase App Check security validation; rate limiting; fraud detection — not stored as user-level records

2. Why We Collect It (Purpose & Legal Basis)

Under the Digital Personal Data Protection Act 2023 (DPDP Act), we process personal data on the following lawful bases:

• Consent: When a patient enters their mobile number and books a token, they are providing explicit, informed consent for us to use that data to manage their OPD queue slot, send OTP verification, and send queue status SMS alerts. This consent is given voluntarily and can be withdrawn (see Section 12).
• Contractual necessity: For clinic operators, data processing is necessary to operate the subscription service they have contracted for — managing their patient queue, reception console, and doctor consultation room display.
• Legitimate interest: IP address and browser metadata are processed for security purposes (App Check fraud prevention, rate limiting) where this does not override the rights of individuals.

We do not sell, rent, or trade any personal data to third parties for marketing, advertising, or commercial purposes. This is absolute and unconditional.

3. Browser Storage & Cookies

We do not use advertising cookies or cross-site tracking cookies. RMedQ uses your browser's localStorage (local device storage) to maintain app state. This data is stored entirely on your device and is not transmitted to our servers separately from normal app operations.

The following data is stored in your browser's localStorage when you use RMedQ:

• rmedq_tracked_token_id — your active token ID, so the live queue screen reloads correctly if you close and reopen the tab
• rmedq_auth_patient — your verified mobile number and name, stored so you don't have to re-verify OTP on every visit within the same session
• rmedq_selected_clinic_id — the clinic you last selected, for a faster repeat booking experience
• rashuv_theme — your light/dark mode preference
• rmedq_lang — your interface language preference (English or Hindi)
• rmedq_admin_session — if you are clinic staff, your admin role and session PIN state, so the reception console remains accessible during your shift
• rmedq_tracked_token_ids — a short list of recent token IDs you have tracked, used to restore multi-token tracking across sessions

You can clear all of this data at any time by clearing your browser's site data for rmedq.rashuv.com. This will log you out of any active session but does not delete records from the server — for server-side deletion see Section 12.

Firebase (Google) may set session cookies necessary for Firebase Authentication and App Check security functions. These are functional/security cookies and are not used for advertising or tracking.

4. Third-Party Data Processors

We use the following third-party services. Each receives only the data strictly necessary for their specific function:

Processor	Country	Function	Data Shared	Privacy Policy
Google Firebase / Google Cloud Platform	India (Mumbai — asia-south1)	Database, hosting, cloud functions, authentication	All patient token data, clinic settings, admin sessions	policies.google.com/privacy
Resend (resend.com)	USA	Transactional email delivery (booking confirmations)	Patient name, email address, token number, clinic name — only when patient provides an email	resend.com/privacy
SMS Gateway (via Firebase / configured carrier)	India	OTP delivery and queue status SMS alerts	Patient mobile number, OTP code, queue status message text	Subject to the gateway provider's terms
Cloudflare	USA / Global CDN	DNS, DDoS protection, and network edge security for rashuv.com and rmedq.rashuv.com	IP addresses and HTTP request metadata — not patient record data	cloudflare.com/privacypolicy
Google Play Store	USA / Global	Distribution of the RMedQ Android companion app	App install and update metadata per Google Play's standard policies	policies.google.com/privacy
Telegram	UAE (HQ) / Global infrastructure	Optional bot channel (@sahajqbot) for token booking and queue alerts	Telegram Chat ID, messages sent/received via the bot, contact sharing for mobile verification	telegram.org/privacy

Patient data stored in Google Firebase is hosted in the asia-south1 region (Mumbai, India), ensuring compliance with Indian data residency requirements. Email confirmation data processed by Resend travels to their US infrastructure for delivery; this is limited to patients who voluntarily provide an email address.

We do not use Google Analytics, Facebook Pixel, or any behavioral advertising or analytics trackers on RMedQ.

5. How Long We Keep Your Data (Retention)

We apply different retention periods depending on the type of data:

• Active queue tokens: Tokens are "live" during the clinic's operating hours on their date. At the end of each clinic day, tokens move from the active queue to an archived state in Cloud Firestore.
• Archived token records: Archived tokens (patient name, mobile number, age, sex, token number, visit date, clinic ID) are retained for up to 12 months from the visit date. This allows patients to view their history and allows clinics to look up returning patients for re-consultation. After 12 months, records are eligible for automated purging.
• Patient profile data (name, mobile number, age, sex, address stored for repeat-visit convenience): Retained as long as the patient has had a visit within the past 12 months, or until the patient requests deletion.
• Clinic operator data (clinic settings, doctor details, subscription records): Retained for the duration of the clinic's active account plus 90 days after account closure, after which it is deleted.
• Email delivery logs (via Resend): Subject to Resend's own retention policy. We do not independently store delivery logs beyond what Firestore records.
• IP address / request metadata: Not retained as user-level records. Firebase App Check and Cloudflare process this for security purposes under their own retention policies.

6. How Data Is Secured

• Encryption in transit: All communication between your browser/app and our servers uses TLS 1.3.
• Encryption at rest: Cloud Firestore data is encrypted at rest by Google using AES-256.
• Firebase App Check: We use Firebase App Check to verify that API requests come from legitimate instances of the RMedQ web app or Android app, preventing automated abuse.
• Firestore Security Rules: Server-side Firestore rules enforce that clinic staff can only access their own clinic's data, and patients can only access tokens associated with their verified mobile number.
• Admin PIN protection: Clinic admin PINs are not stored in plaintext. Session state is maintained in localStorage on the clinic device and does not persist after the session ends or the browser is cleared.
• No public exposure of sensitive fields: Mobile numbers are never displayed in full on the waiting hall TV screen. Only the last 4 digits are shown in the booking pass where needed for identification.

7. Waiting Hall TV Display Privacy

The RMedQ waiting hall TV streaming mode (intended for display screens in clinic lobbies) shows only:

• The token number (e.g., #A-15)
• The doctor room number
• The patient's first name or a partial name, depending on clinic configuration

Mobile phone numbers, home addresses, consultation fees, clinical visit types, and any other personal details are never broadcast on waiting hall TV screens or audible announcement systems.

8. No Medical Records

RMedQ is strictly an OPD queue management system. It does not store, transmit, or process:

• Doctor consultation notes or diagnoses
• Prescription details or medication history
• Lab test results or radiology reports
• Chronic illness, allergy, or medical condition information
• Insurance or government health scheme data

If a clinic uses a separate Electronic Medical Records (EMR) system alongside RMedQ, that EMR system operates independently and is subject to its own data practices. RMedQ does not integrate with or receive data from any third-party EMR system.

9. Android App

The RMedQ Android app (com.rashuv.rmedq) is available via direct APK distribution and on Google Play. The Android app is a WebView wrapper around the RMedQ web application (rmedq.rashuv.com). It does not independently collect or transmit data beyond what the web app collects.

The Android app requests the following device permissions:

• INTERNET — required to load the RMedQ web app and connect to Firebase
• POST_NOTIFICATIONS — to display OPD queue alert notifications (e.g., "Your token is next") via Firebase Cloud Messaging. You can revoke this permission in Android Settings at any time.

The app does not access your camera, microphone, contacts, location, or storage. It does not collect device identifiers for advertising purposes.

Google Play's standard data collection practices apply to the app's distribution and update mechanism. See Google's Privacy Policy.

10. Telegram Bot (@sahajqbot)

RMedQ offers an optional Telegram bot (@sahajqbot) as an alternative channel for patients to book OPD tokens and track their live queue position. Use of the Telegram bot is voluntary — it is not required to use RMedQ.

What the Telegram bot collects and stores:

• Telegram Chat ID: Your unique Telegram user ID is stored in our Firestore database, linked to your verified mobile number. This is used to send you queue alerts and maintain your session.
• Session state: Your current flow step (e.g., booking in progress), selected clinic, language preference, and role are stored in Firestore under a bot_sessions collection. This persists across bot restarts so your conversation is not lost.
• Mobile number: Verified via Telegram's native contact sharing. Your phone number is stored and linked to your Telegram Chat ID exactly as it would be if you booked via the PWA.
• Patient profile: Age, sex, and locality entered during onboarding are stored in Firestore against your mobile number — shared with the PWA and Android app.

What appears in the Telegram chat:

• Your token number, patient name, clinic name, doctor name, and Estimated Consultation Time (ETC) are displayed directly in the Telegram chat as a live consultation card.
• Queue proximity alerts ("You are 2 tokens away", "It's your turn") are sent as Telegram messages containing your name and token number.
• These messages are visible to anyone with access to your Telegram account. Treat your Telegram account with the same care as your phone. If you share a device, be aware that queue and appointment details will be visible in the chat history.

Telegram's own privacy practices:

The Telegram bot operates over Telegram's platform. Telegram processes your messages and chat data under their own privacy policy. See telegram.org/privacy. We have no control over how Telegram stores or processes data on their infrastructure. We only control what we store in our own Firestore database.

To remove your Telegram bot data:

Email [email protected] with subject "Telegram Bot Data Deletion". We will delete your bot_sessions record and unlink your Telegram Chat ID from your patient profile within 15 business days. This does not delete your patient token history — request that separately if needed.

11. Children's Privacy

RMedQ is used in OPD clinic settings where children are frequently patients. When a child's token is booked, it is done by a parent or guardian who provides their own verified mobile number. The child's name and age are entered by the parent/guardian.

We do not knowingly allow children under 18 to independently register accounts or book tokens without parental oversight. If you believe a child's data has been submitted without appropriate consent, contact us at [email protected] and we will delete the record.

12. Your Rights Under DPDP Act 2023

Under India's Digital Personal Data Protection Act 2023, you have the following rights regarding your personal data processed by Rashuv Technologies through RMedQ:

• Right to information: You have the right to know what personal data we hold about you and how it is being processed. This Privacy Policy is our primary disclosure.
• Right to correction: You may request correction of inaccurate personal data (e.g., a misspelled name, wrong age).
• Right to erasure: You may request deletion of your personal data from our systems. See Section 12 for how to do this.
• Right to grievance redressal: You may raise a complaint about our data practices with our Grievance Officer (see Section 14). If unresolved, you may approach the Data Protection Board of India once it is constituted under the DPDP Act.
• Right to withdraw consent: You may withdraw consent for data processing at any time. Withdrawal does not affect the lawfulness of processing that occurred before withdrawal. See Section 12 for the withdrawal process.

13. How to Withdraw Consent or Delete Your Data

Patients — to request data deletion or consent withdrawal:

1. Email [email protected] with the subject line "Patient Data Deletion Request"
2. Include your mobile number (the one you used to book tokens) and the approximate clinic name or visit date
3. We will verify your identity (by sending an OTP to the mobile number you provide) and process the deletion within 15 business days
4. Deletion removes your mobile number, name, and associated token history from our Cloud Firestore database. It cannot be undone.

Clinic operators — to close your account and delete all clinic data:

1. Email [email protected] with the subject line "Clinic Account Deletion Request"
2. Include your clinic ID or registered email and confirm you want all data (clinic settings, patient queue records, doctor profiles) permanently erased
3. We will process verified clinic deletion requests within 30 days

To withdraw consent without full deletion: You may also simply stop using RMedQ. Since OTP consent is per booking session, there is no ongoing subscription of consent to withdraw beyond your stored session data in localStorage (which you can clear on your device) and your archived token records (which you can request deletion of via the process above).

14. Changes to This Policy

We will update this Privacy Policy when our data practices change or when required by law. Material changes will be communicated by:

• Updating the "Effective Date" at the top of this page
• Displaying a notice in the RMedQ clinic dashboard for registered operators
• For changes that materially affect patient rights, posting a notice on the booking interface at rmedq.rashuv.com

We will give at least 14 days' notice before material changes take effect for registered clinic operators.

15. Grievance Officer & Contact

Under the DPDP Act 2023, Rashuv Technologies has appointed a Data Protection & Grievance Redressal Officer. For any privacy-related inquiries, correction requests, deletion requests, or complaints: