Tarteeb Health

Privacy Policy

Last updated: 8 November 2026 (draft for legal review)

This policy explains what Tarteeb Health collects, why, who it is shared with, and the choices patients and clinics have. We wrote it in plain language. If anything is unclear, write to tarteebhealth@gmail.com.

See also our Terms of Service.

1. Who we are and our role

Tarteeb Health (“we”, “us”) is a clinic queue and appointment service run by [registered business name], [registered address], India. Contact: tarteebhealth@gmail.com.

We play two roles under India’s Digital Personal Data Protection Act, 2023 and its Rules (“DPDP law”):

  • For patient data, the clinic is in charge (the “Data Fiduciary”). The clinic decides what to record and why; we process it on the clinic’s instructions (as a “Data Processor”). Patients should first contact their clinic about their data.
  • For clinic accounts (owners, doctors and reception staff who sign in), and for visitors to our website, we are in charge of that data.

2. What we collect

Clinic staff accounts

  • Name, email address, role (owner, doctor or reception) and the clinic(s) you belong to.
  • Sign-in records, and which device and time each queue action came from (for the clinic’s tamper-evident activity record).

Patients (entered by the clinic, or by the patient when booking online)

  • Name, age (optional), phone number (optional for walk-ins), and a caregiver’s phone number if given.
  • Visit details: doctor, date, token number, visit type, arrival and consultation times, and cancellation reasons.
  • Whether the patient agreed to receive appointment messages, and when.
  • Consultation notes, only if a doctor writes them. Reception staff cannot see these.

Automatically

  • For booking abuse protection: a one-way scrambled (hashed) form of the visitor’s IP address and phone number, kept for short periods, and a Cloudflare Turnstile check.
  • Technical error reports with personal details removed (see “Error tracking”).
  • “Use my location” (clinic setup only, and only if you tap it): your browser shares your position, we round it to about 1 km and send only those approximate coordinates to BigDataCloud to find your state and district. We do not store the coordinates, and patients are never asked for their location.
  • On clinic devices, the app keeps today’s queue in the browser’s storage so it keeps working during a power cut. It is cleared after it syncs and when the day changes.

We do not collect Aadhaar numbers, payment card details, or diagnoses through the booking page.

3. Why we use it

  • To run the clinic’s queue: tokens, wait times, the doctor screen, the waiting-room TV and the patient’s live queue link.
  • To let staff sign in and to keep each person’s access to their own role.
  • To keep a tamper-evident record of queue changes, so disputes and mistakes can be checked.
  • To send booking emails and “your turn is near” phone alerts, only to patients who asked for them. Automatic WhatsApp and SMS messages are not live yet.
  • To protect the service from abuse, fix errors and keep it secure.

We never sell personal data, never show advertising, and never use patient data to train AI models.

4. Consent and lawful use

Patients give their details to the clinic to receive care. The booking page and reception tell patients what the clinic keeps and why. Appointment messages are sent only with separate, optional consent, which a patient can withdraw at any time by telling the clinic.

For staff accounts, we process data to provide the service the clinic signed up for. For children, a parent or guardian gives the details; clinics use children’s data only to provide health services.

5. The waiting-room TV and queue link

If the clinic turns on “Show first names on TV”, the TV shows and may announce a patient’s first name only beside the token number. It never shows surnames, age, phone numbers or medical details. Clinics can turn first names off.

The patient’s live queue link shows only the token, the wait, the doctor and the clinic’s name and town. Each link is private, hard to guess, and stops working after the visit day.

6. Who we share data with

Only with service providers we use to run Tarteeb Health, under contracts that require them to protect it:

ProviderWhat forData involved
SupabaseDatabase, sign-in and file storageAll service data (stored in Mumbai, India)
VercelWebsite hostingRequests passing through the website
BrevoEmails: sign-in codes, booking confirmations and reminders, payment receiptsStaff and owner email addresses; for patients who gave an email: email address, first name, clinic, token and time
Cloudflare TurnstileBot check on the booking pageBrowser signals and IP address
SentryError trackingError reports with personal data removed: no names, phone numbers, emails, queue links or IP addresses
BigDataCloudFinding the district when a clinic taps “Use my location” during setupApproximate coordinates (rounded to about 1 km), nothing else
Microsoft Azure Speech (if the clinic turns on the neural TV voice)TV announcementsAnnouncement text: token number and, if enabled, first name
Browser push services (Google, Mozilla, Apple)Delivering “your turn is near” alerts a patient turned onAn encrypted alert (token and clinic name); the push service cannot read it

We may disclose data if Indian law requires it, for example to a court or government authority with legal power to ask. Some providers may process data outside India, as allowed by DPDP law; we will follow any restrictions the Government of India notifies.

7. How long we keep it

  • Patient and visit records stay as long as the clinic uses Tarteeb Health, because clinics often must keep medical records for several years. The clinic decides when to remove or anonymise a patient.
  • If a clinic leaves, we give the owner a way to export its data, then delete it within 90 days, except what the law requires us to keep.
  • The activity record is kept as long as the clinic’s data, so it stays complete. When a patient is anonymised, their name, phone and age are blanked in it as well.
  • Booking protection data (hashed IP and phone) is kept only for the day or hour it is needed. Error reports are kept for up to 90 days.
  • Database backups follow our hosting provider’s schedule and are overwritten after their retention period.

8. Your rights

Under DPDP law you can ask to see a summary of your personal data, correct or complete it, erase it (where the law doesn’t require it to be kept), withdraw consent for messages, and nominate someone to act for you.

  • Patients: ask your clinic. Owners can download a copy of your data or anonymise you from Tarteeb Health. If the clinic doesn’t respond, write to us at tarteebhealth@gmail.com and we will help the clinic respond.
  • Clinic staff: write to tarteebhealth@gmail.com.

We reply within 30 days. To protect you, we may need to confirm who you are first.

9. How we protect data

  • Every clinic’s data is separated at the database level; each person sees only what their role allows.
  • Data is encrypted in transit (HTTPS) and at rest by our hosting providers.
  • Queue changes are written to an append-only, hash-chained activity record, so tampering shows.
  • Secret keys stay on our servers and are never sent to browsers.

Clinics are responsible for keeping their own devices, passwords and printed token slips secure. If a personal data breach happens, we will inform the affected clinics and, as DPDP law requires, the Data Protection Board of India and affected people.

10. Error tracking

When something breaks, a short technical report goes to our error-tracking provider, Sentry: what failed, the type of page (for example “queue link”, never the link itself) and where in our code. Before it leaves the app, and again on our server, we remove names, phone numbers, email addresses, queue links and codes, notes and anything typed into forms. We do not send IP addresses, cookies or sign-in details, and we do not record screens or sessions. Error reports are kept for up to 90 days.

11. Cookies and local storage

We use only what is needed to work: a sign-in cookie, and browser storage for offline use, language and display choices. No advertising or tracking cookies.

12. Complaints and Grievance Officer

Grievance Officer: [name], tarteebhealth@gmail.com, [phone]. We acknowledge complaints within 48 hours and resolve them within 30 days. If you are not satisfied, you can complain to the Data Protection Board of India.

13. Changes to this policy

We will post changes here and update the date above. For important changes, we will tell clinic owners by email before they take effect.

← Back to Tarteeb Health