Your place in line should stay private.

1. Who operates Waitometer

Waitometer is developed and operated by Techifirm Services Pvt Ltd, registered in India and based in Mumbai, Maharashtra. A clinic, diagnostic centre, salon, bank, service centre, or other organisation using Waitometer is referred to as a “Business”. A person joining or following a queue is a “Customer”.

The Business decides why it serves a Customer and which visit details it needs. Techifirm processes queue information to provide Waitometer and separately controls limited product-security, support, and operational data.

2. Information we process

• Business information: organisation, location, services, queues, service points, authorised staff roles, and sign-in information.
• Visit information: a display name, token, queue position, visit state, service, timing, instructions, and operational actions such as late, skip, undo, cancel, or complete.
• Optional contact information: a phone number or other contact supplied for a visit, including delegated contact details. A phone number is not required for every visit.
• Optional location information: a one-time device position or manually entered starting place only when a Customer asks for travel guidance.
• Technical and safety information: session identifiers, IP-derived security signals, timestamps, device/browser details, request outcomes, audit records, and privacy-safe diagnostics.
• Commercial records: plan, usage, billing status, and provider attempt metadata. Waitometer does not need card numbers, UPI PINs, or banking passwords.

We do not sell personal data and do not use queue data for third-party advertising.

3. Why we use information

• create, order, update, and recover live or planned queue visits;
• show a Customer their private live position, expected wait, and next instruction;
• help authorised Business staff operate counters and resolve queue problems;
• secure accounts, prevent abuse, enforce tenant boundaries, and investigate incidents;
• provide support, measure reliability, reconcile usage, and improve Waitometer; and
• meet applicable legal, accounting, dispute, or regulatory requirements.

4. Consent and choices

Where consent is the basis for processing, it should be clear, specific, informed, and given through an affirmative action. Optional location is off until a Customer chooses to provide it. A Customer can decline location and continue using the queue. Withdrawing optional consent does not undo lawful processing already completed and may prevent the related optional feature from working.

5. Private links and public information

Public QR codes and queue links identify a Business queue; they do not contain a private visit credential. After joining, a Customer receives a high-entropy private visit link. Treat that link like a ticket: do not post it publicly or forward it to someone who should not see or act on the visit. A visible token number alone does not authorise access.

6. Sharing and service providers

We share only what is needed with:

• the Business and its authorised staff for the relevant queue or visit;
• hosting, database, cache, security, monitoring, and support providers acting for us;
• notification, route, payment, or communication providers only when that integration is enabled and needed; and
• courts, regulators, law enforcement, or another party when legally required or necessary to protect people, rights, or the service.

During the V1 pilot, paid messaging, email, push, OTP, and route providers are disabled unless a Business is told that a specific provider has been enabled.

7. Hosting and international processing

Waitometer’s V1 pilot web applications use Vercel. The API, worker, realtime service, PostgreSQL, and Redis are hosted in Fly.io’s Singapore region because Fly.io does not currently offer a Mumbai region. Data may therefore be processed outside India, subject to applicable law and contractual or technical safeguards. We will update this policy if the hosting arrangement materially changes.

8. Pilot retention

Shorter deletion may apply where technically possible and no legal or security need requires retention. Limited audit, security, billing, dispute, and backup records may follow separate documented schedules or be retained where law requires. The pilot retention profile remains subject to final legal review before Phase 19 is marked passed.

9. Security

Waitometer uses encrypted transport, scoped access controls, private visit sessions, tenant separation, audit records, rate limits, secret management, minimal logs, and tested recovery procedures. Redis and realtime messages are not the source of truth; PostgreSQL holds canonical queue state. No internet service can promise absolute security.

10. Children and assisted visits

Waitometer is not designed for children to create independent Business accounts. A parent, guardian, carer, or authorised staff member may manage a queue visit for a child or another person who needs assistance. The Business must collect only the minimum appropriate information and obtain any required authority.

11. Your privacy rights

Subject to applicable law, a person may ask for access to a summary of personal data, correction, completion, updating, erasure, withdrawal of consent, grievance handling, or nomination of another person to exercise rights where applicable. The quickest route for visit data is the Business that issued the queue link because it can identify the relevant visit without exposing a private link publicly.

A Business can escalate a verified privacy request to Techifirm through its Waitometer administrator support channel. Never include a private visit link, OTP, password, or unnecessary medical information in an ordinary support message.

12. Indian privacy framework

This policy is designed around the principles of lawful purpose, clear notice, data minimisation, security safeguards, and individual rights reflected in India’s Digital Personal Data Protection framework. You can read the official Digital Personal Data Protection Act, 2023 and the Ministry’s Digital Personal Data Protection Rules, 2025.

13. Changes and contact route

We may update this policy as Waitometer moves beyond the V1 pilot, enables providers, or changes legal or hosting requirements. Material changes will be dated and presented through the product or website. For a privacy concern, first contact the Business that supplied your queue link. Business administrators can use their established Waitometer pilot support channel to reach Techifirm’s privacy and grievance owner.

Techifirm Services Pvt Ltd · Mumbai, Maharashtra, India