Privacy notice

Last updated: 1 September 2026 · This is a product notice, not a claim of certification.

Smart Queue is hospital queue software. This page explains what we collect on the public website and, in broad terms, what the product stores when a hospital uses the service. It is written so an administrator can read it before a demo.

Who this covers

Website and demo enquiries

If you submit the demo form we receive hospital name, your name, role, phone, city, and approximate OPD size. That request is sent through our form provider so we can reply by email, phone or WhatsApp.

The public site may use standard analytics (page views, device, approximate region). We do not sell website leads.

What the product is for

The application stores what a live OPD queue needs: hospital account, staff access, doctor lists, token numbers, queue position, timestamps, and the patient details reception enters to issue a token. Each hospital’s records are separated from every other hospital at the database layer.

What we do not do with hospital data

Access inside a hospital

Reception, doctor, manager and patient views are role-based. Staff screens are gated by a hospital PIN checked on the server. A hospital manager can reset staff PINs.

Security in transit

Application traffic is served over HTTPS.

Retention and leaving the service

Enquiry data is kept so we can answer you and, if you become a customer, support the account. If a hospital stops using Smart Queue, we will delete or export operational data on a written request to hello@smarthospitalqueue.com, subject to any legal hold we are required to honour.

Your requests

Email hello@smarthospitalqueue.com to access, correct or delete an enquiry, or to raise a hospital-data question. We will not pretend this page is a DPDP certification. Indian hospitals that need a formal processing addendum should ask for one before go-live.