Draft: details in yellow are filled in after business registration, and the text is reviewed by a lawyer before launch.
Last updated: 1 November 2026
Waitmatic is operated by [Legal business name], [Registered address], Ahmedabad, Gujarat, India (“we”, “us”). This policy explains what personal data the Waitmatic app and the website waitmatic.in handle and why.
Who this covers
- Restaurant users: owners, managers and staff who use the Waitmatic app.
- Customers: people a restaurant adds to its waiting queue.
Data we collect
| Who | What |
|---|---|
| Restaurant users | Name, mobile number, restaurant name, city and address, role, and actions in the app (queue actions, settings changes). |
| Customers | Mobile number, name, number of people, an optional note (for example “Kids”), token number, queue times and status, and an optional rating or comment. |
| Payments | Plan, amount and payment reference. Card and UPI details are handled by Razorpay; we never see or store them. |
| Technical | App version, phone model and operating system version, and error reports, so we can fix problems. Phone numbers are hidden in these reports. |
Why we use it
- To run the queue: create tokens, estimate waits, and send the customer their token, live tracking link and status updates by WhatsApp and SMS.
- To sign users in with a one-time SMS code.
- To show each restaurant reports about its own queue.
- To bill restaurants for their plan.
- To keep the service secure and fix errors.
Customer messages are service updates about that visit only. We do not send marketing messages, and we do not sell personal data.
Legal basis
We process customer data on behalf of the restaurant, which asks the customer for consent to send updates to their number. We process restaurant users’ data to provide the service they signed up for.
Who can see the data
Each restaurant can see only its own customers. Customers can see only their own token on their private link. Our founder team can see account and usage information to support restaurants; every such view is recorded. We use these service providers:
- Supabase (database and login hosting)
- Meta Platforms (WhatsApp Business messages)
- MSG91 (SMS messages and login codes)
- Razorpay (subscription payments)
- Vercel (website hosting)
- Expo (app builds and updates)
How long we keep it
- Customer mobile numbers and names: deleted automatically 90 days after the customer’s last visit (the restaurant can choose 7–730 days).
- Tracking links: stop working 2 days after the visit.
- Error and security logs: 180 days.
- Restaurant accounts: while active, and deleted within 7 days of a deletion request, except records we must keep by law (for example invoices).
- Anonymous queue statistics: kept for reports.
Your rights
Under India’s Digital Personal Data Protection Act, 2023 you may ask to access, correct or erase your personal data, withdraw consent, nominate someone, and raise a grievance. Restaurant users can delete their account inside the app (More → Delete restaurant account or Remove my login). Customers can ask the restaurant, or write to us.
Security
Data is encrypted in transit. Each restaurant’s data is separated at the database level, and access is limited to what each role needs. Login tokens on phones are kept in the phone’s secure storage. We limit login codes and other actions to stop abuse.
Children
The Waitmatic app is a business tool and is not meant for children.
Changes
We will update this page and the date above when this policy changes. Important changes are announced in the app.
Contact and grievance officer
[Grievance officer name], Grievance Officer, [Legal business name] — support@waitmatic.in. We acknowledge within 48 hours and reply within 7 days.