RestoMama Merchant Privacy Policy

RestoMama is a product of Priority Queues Private Limited.


Company	Priority Queues Private Limited
CIN	U47413KL2026PTC105859
Registered office	Door No. 463, Thayyil House, Vazhukakkode, Anjumoorthy, Palakkad, Kerala 678682, India
Phone	+91 97477 47702 (Monday to Saturday, 9:30 am – 6:30 pm IST)
Email	admin@priorityqueues.com
Website	https://priorityqueues.com

This policy explains how Priority Queues Private Limited ("Priority Queues", "we", "us", "our") handles personal data about the people who use RestoMama for restaurants and other food businesses, and about people who ask to join it. It covers:

restaurant owners, admins, managers and staff who sign in to RestoMama Admin, on the web or in the "RestoMama Admin" Android app ("Users");
people who apply to open a RestoMama merchant account ("applicants"); and
people who send us an enquiry about RestoMama for their restaurant through one of our enquiry forms ("enquirers").

RestoMama for restaurants also includes RestoMama Displays, which shows a restaurant's menu boards on its screens, either through the "RestoMama Displays" app for Android TV or in a web browser on the screen. RestoMama Displays has no user accounts of its own: a User links each screen to the restaurant's account from RestoMama Admin ("pairing"). Section 3.1 describes the data a paired screen sends us.

This policy does not cover restaurant customers. Section 2 explains why.

1. The law that applies

The Digital Personal Data Protection Act, 2023 and the DPDP Rules, 2025 apply in phases; the substantive obligations and the Data Protection Board's complaint powers commence on 13 May 2027. Until then, personal data is handled under the Information Technology Act, 2000 (s.43A) and the IT (Reasonable Security Practices and Procedures and Sensitive Personal Data or Information) Rules, 2011. We already give you the rights described in section 10.

2. Our role, and the restaurant's role

2.1 Where we decide. For the personal data described in section 3, we decide why and how it is used. We are the data fiduciary for it.

2.2 Where the restaurant decides. A restaurant that uses RestoMama also keeps data in it about its own customers (for example names, phone numbers, addresses, orders, loyalty points, feedback and marketing preferences) and about its own staff (for example attendance, wages, payroll, cash advances, identity and certificate documents, and employment notes). For that data the restaurant is the data fiduciary and we are its data processor: we store and process it only to provide RestoMama to the restaurant, and we do not use it for our own purposes.

If you are a customer of a restaurant and have a question about your data, contact that restaurant. Its contact details and grievance officer are shown on its ordering website.
If you are a member of a restaurant's staff and have a question about your employment records, contact your employer.
If you order through the RestoMama marketplace, the RestoMama Privacy Policy explains how we handle your data as the marketplace operator.

Where a restaurant asks us to, we help it answer requests from its customers and staff.

3. The personal data we collect

3.1 Users of RestoMama Admin, and RestoMama Displays screens

Data	Where it comes from	Why we use it
Name, email address, mobile number, role, the locations you can access, and your organisation's Tenant ID	The owner or a User in your organisation who creates or edits your account; for the first owner, the application to join RestoMama	To create and run your account, show your organisation who you are, and control what you can see and do
Password	You	To sign you in. We store it only as a one-way hash; we cannot read it
Sign-in codes and password-reset codes	Created when you ask for one	To sign you in or reset your password. We keep a record of the phone number or email it was sent to, when it was sent, and the number of attempts. The code itself is stored only as a one-way hash
Sign-in and security records: failed sign-in attempts, temporary lockouts, and your active sessions	Created when you sign in	To protect your account, lock it after repeated failed attempts, and keep you signed in until you sign out. Session tokens are stored only as one-way hashes
Audit records of the changes you make, such as changes to menus, prices, staff, settings, payments and billing, with the time, your IP address and your browser or app details	Created when you act in RestoMama Admin	To keep a trustworthy record of who changed what, investigate problems and misuse, and resolve disputes
Crash reports from the Android app: the error log, app version, Android version and device model	Your device, after the app stops unexpectedly	To find and fix faults
Browser push notification subscription, if you allow notifications	Your browser	To alert you to new orders and other events
Bluetooth devices paired with a till (device name and hardware address), reported when a User scans for printers. The list can include paired devices that are not printers, such as phones	The till	To send receipts and kitchen tickets to the right printer
Support reports you send from the Support page, including screenshots you attach, and technical details attached automatically: the page you were on, the app version, your browser details, your screen size and up to 20 recent error messages, with email addresses and phone numbers removed	You, and the app you send the report from	To answer and fix the problem you report
Messages we send you, such as your sign-in details, billing reminders and alerts	Created by RestoMama	To run your account
Your device's location, only if you choose "Use Current Location" while adding a restaurant location in RestoMama Admin in a web browser	Your browser, after you allow it to share your location	To fill in the map position (latitude and longitude) of the location you are adding. We store only that position, as part of the location's details
For each screen paired with RestoMama Displays: the credential that links it to your organisation (kept on the screen; we store only a one-way hash of it), the screen's browser details (user-agent string, which can include the TV's model), when it was paired and by which User, whether it is online, when it was last seen and what it reports it is showing. The Android TV app also sends its version and build, the TV's make, model and Android version, a random identifier the app creates when it is installed, and, if the app has stopped before, why it last stopped (for example a crash, the TV running out of memory or someone closing the app) and when. At present our servers refuse these reports from the Android TV app and do not store what they contain	The screen, and the User who pairs it	To show your menu boards on the right screen, show your organisation which screens are working, and alert you when a screen goes offline
Server logs: the IP address and details of each request our servers receive, including requests from RestoMama Admin and from paired screens	Your device or screen, recorded by our servers and hosting providers	To keep RestoMama running and secure, and to investigate faults and misuse

On a till or phone, RestoMama Admin keeps your sign-in session on the device so that you stay signed in. It does not use advertising identifiers or third-party analytics.

3.2 Owners: billing and payouts

Data	Why we use it
Your plan, billing cycle, charges, credits, payments and the payment references our payment provider returns	To bill your organisation and record payments. Card and UPI details you enter at checkout go to the payment provider, not to us
The sign-in phone number or email of your organisation's first owner, recorded when a free trial starts	To make sure each person uses only one free trial
Wallet payout account: account holder name and either the bank account number and IFSC, or a UPI ID	To transfer your payouts. We keep these in full, and a copy with each payout record, because we need them to make and trace the transfer
UPI IDs your organisation adds to collect payments from its customers: the UPI ID, the payee name and a label	To show your customers where to pay when they pay you by UPI, for example in a UPI QR code, and to record which UPI ID a payment was made to
Bank and KYC details for split settlement: bank account number, IFSC, account holder name, PAN, account type, business type, contact email and contact phone	To have the payment provider verify your account so that your share of online payments can be settled straight to your bank (see section 3.3)

3.3 How we handle bank account numbers and PAN for split settlement

When a User submits bank and KYC details for split settlement, we pass them to our payment provider, which verifies them. We pass them only once we have switched split settlement on with our payment provider; until then we hold them as described below. Split settlement can be turned on for your organisation only after the payment provider has verified your details. We handle the full bank account number and the PAN as follows:

we keep them only in encrypted form, and only until the payment provider has accepted them;
we delete them in the same step in which we record that the payment provider has accepted them;
if we cannot pass them to the payment provider within 180 days, we delete them anyway and you will need to enter them again.

After that we keep only the last four digits of the account number, the IFSC, the account holder name, the account type, the business type, the contact email and phone, and the verification status and any reason for rejection that the payment provider reports to us.

3.4 Applicants

Data	Why we use it
Your name, mobile number (which we verify with a code sent by WhatsApp), email address and password (stored only as a one-way hash)	To create your applicant account and let you return to your application
Business details: business name, legal name, business type, address, city, state, PIN code, contact name, email and phone, the web address you would like, and the plan you are interested in	To assess your application and set up your restaurant's account
Documents and their details: PAN card and PAN number, GST certificate and GSTIN, FSSAI licence with its number and expiry date, bank account proof (such as a cancelled cheque or passbook page) and business address proof	To verify your business before we open an account. An FSSAI licence is required; the others are optional unless we ask for them
Our review notes and decisions, and the history of your application	To make and record a decision, and to explain it if you ask

Documents are kept in private storage that is not publicly accessible. If your application is approved, the owner account for your restaurant is created from your applicant details, and your application becomes part of your restaurant's account records. An owner can also upload updated business documents later, in RestoMama Admin under Account > Business Documents; we keep and use them in the same way.

3.5 Enquirers

When you send us an enquiry about RestoMama for your restaurant, we collect what you enter (such as your name, mobile number, email address, restaurant name, city, type of business, number of branches, what you need and your message), the page you sent it from, any campaign tags in the link you followed, the consent you gave on the form, your IP address and your browser details. We use it to contact you about your enquiry and to keep track of it. We may send you an acknowledgement on WhatsApp, and we alert our team on WhatsApp with your name, phone number, type of business, city and the page you used, so that someone can call you back.

4. Why we use personal data, and on what basis

We use the data described in section 3 only for the purposes stated there, which together are:

to provide RestoMama, run your account and give you support;
to keep RestoMama and your account secure, detect and prevent fraud and misuse, and keep records of changes;
to bill your organisation, collect payments and make payouts;
to verify your business and your payout accounts;
to handle enquiries and applications;
to find and fix faults and improve RestoMama; and
to comply with the law and respond to lawful requests from authorities.

We process this data on the basis of your consent, which you give when you provide it to us for these purposes, or where the law requires or permits us to process it without consent, for example to meet a legal obligation. Your password and your bank account and payment details are sensitive personal data under the IT (Reasonable Security Practices and Procedures and Sensitive Personal Data or Information) Rules, 2011. We use them only for the purposes described in section 3, and you give them to us for those purposes when you submit them. You may choose not to give us any data, but we may then be unable to provide RestoMama or the feature that needs it. From 13 May 2027, we process personal data on the basis of your consent or a legitimate use under sections 6 and 7 of the DPDP Act. We do not sell personal data, and we do not use it for advertising.

We share personal data only as follows:

Your organisation. People in your organisation with the right permissions can see your name, contact details, role and locations, and the changes you make in RestoMama Admin.
Payment providers. Our payment providers receive what they need to take your online billing payments and to verify the bank and KYC details you submit for split settlement. They handle this data under their own obligations as regulated payment businesses. The payment provider that verifies and keeps your bank and KYC details for split settlement is Cashfree Payments India Private Limited, Building No. 7, 10th Floor, Ecoworld, Sarjapur Marathalli Outer Ring Road, Bellandur, Bengaluru, Karnataka 560103, India; we pass your details to it once we have switched split settlement on with it, which is before split settlement can be turned on for your organisation (section 3.3). Online billing payments are taken by PhonePe Limited, Office-2, Floor 5, Wing A, Block A, Salarpuria Softzone, Bellandur Village, Varthur Hobli, Outer Ring Road, Bangalore South, Bengaluru, Karnataka 560103, India. We do not use a payment provider to transfer wallet payouts at present: we make each payout ourselves, by a bank or UPI transfer from our own bank account, and our bank receives the payout account details needed for that transfer. We will add the name and address of any payout provider to this policy before it receives your payout account details.
Messaging providers. Our SMS, WhatsApp and email providers receive your phone number or email address and the message, to deliver sign-in codes, account details, alerts and replies to enquiries.
Hosting and storage providers. Our cloud hosting, database and file-storage providers store and process data for us.
Font provider. A screen showing RestoMama Displays loads its fonts from Google Fonts, a service of Google LLC, which receives the screen's IP address and browser details when it does.
Artificial-intelligence model provider. Support reports, including attached screenshots and the technical details described in section 3.1, may be analysed with an AI model to help us diagnose and fix the problem, and passed to our software-development tools for the same purpose. When an AI feature is switched on for your organisation, the content that feature uses is sent to the AI provider.
Authorities. Courts, regulators, law enforcement and other authorities, where the law requires us to share data, or where it is needed to protect people's safety or rights.
A new owner of our business. If our business or part of it is transferred to another company, the data goes with it, under the protections in this policy.

Our service providers act on our instructions and are bound by written terms to protect the data. We will give you the current list of our providers on request.

6. Where your data is stored

Our service providers may store or process data outside India. We transfer personal data outside India only as Indian law permits. Where we transfer sensitive personal data outside India, we do so only where it is needed to provide RestoMama to you or you have agreed, and only to a recipient that protects it to at least the standard Indian law requires of us.

7. How long we keep it

Data	How long
Your User account (name, contact details, role, locations and password hash)	While your organisation's RestoMama account exists. If you are deactivated, your employer's account keeps your profile. If you ask us to delete your account, we delete your password straight away, and keep your name, mobile number and email address for 180 days after your account is deactivated or closed, as the law requires, and then delete them. Our page on closing or deleting a merchant account explains this
Audit records, failed sign-in and lockout records, records of sign-in codes, and sessions that have expired	While your organisation's RestoMama account exists, and for 180 days after it closes. From 13 May 2027, we also keep each record for at least one year from the activity it records. We then delete them
Active sessions	Until you sign out, the session is replaced, or your account is deactivated
Crash reports from the Android app	90 days
Full bank account number and PAN for split settlement	Until the payment provider accepts them, and never more than 180 days (see section 3.3)
The sign-in mobile number or email address of your organisation's first owner, linked to the record of its free trial	Three years after the trial ends, whether or not your organisation's account is still open; then deleted. We use it only to make sure each person takes only one free trial
Billing, payment and payout records	For as long as the law requires us to keep our accounting and tax records (see section 7.1)
Report files you ask RestoMama Admin to prepare for download	Available to download for 7 days. The file stays in our storage until your organisation's data is deleted
Applications that are approved	As part of your restaurant's account records
Applications that have been submitted and are waiting for our decision	Until we decide; then as stated in the row for approved or for rejected applications
Applications that are rejected, with the documents uploaded for them	180 days after the rejection; then deleted
Applications that are not completed, including an application we send back for changes that is not resubmitted, with the documents uploaded for them	180 days after the last activity on the application; then deleted
Your applicant account (name, mobile number, email address and password hash), unless your application is approved	We delete the password hash when we delete your application or, if you never started one, 180 days after the last activity on your applicant account. We keep your name, mobile number and email address for a further 180 days, as rule 3(1)(h) of the Information Technology (Intermediary Guidelines and Digital Media Ethics Code) Rules, 2021 requires; then deleted
Enquiries that do not lead to an account	180 days after the last activity on the enquiry; then deleted
Support reports	For as long as needed to resolve the problem and keep a record of the fix
Pairing codes shown on a screen before it is paired with RestoMama Displays, with the screen's browser details	They expire after 10 minutes and are deleted about an hour after that
Server logs	For our hosting provider's log-retention period; then deleted automatically
Everything else described in section 3	No longer than your organisation's RestoMama account exists; then as described in our page on closing or deleting a merchant account

7.1 Some records must be kept by law even after an account is closed. For example, the Central Goods and Services Tax Act, 2017 (section 36) requires accounts and records to be kept until 72 months after the due date of the annual return for the year they relate to, and the Companies Act, 2013 (section 128(5)) requires books of account and the vouchers behind them to be kept for eight financial years. We keep such records only for as long as the law requires, and use them only for that purpose. We may also keep records needed for a dispute, claim or investigation that is open or reasonably expected, until it is resolved.

8. How we protect it

We do not hold IS/ISO/IEC 27001 or any other security certification. We protect personal data with these safeguards:

connections to RestoMama are encrypted (HTTPS);
passwords, session tokens, sign-in codes and the credentials of paired screens are stored on our servers only as one-way hashes;
full bank account numbers and PAN held for split settlement are encrypted, and deleted once the payment provider accepts them, or after 180 days at most;
application documents are kept in private storage that is not publicly accessible;
sign-in is locked for a period after repeated failed attempts;
each User sees only what their role and location access allow; and
changes are recorded in audit records.

No system is completely secure. If a personal data breach affects you, we will tell you and the authorities as the law requires.

9. Children

RestoMama Admin is a workplace tool for people aged 18 or over. We do not knowingly collect personal data from children for our own purposes. If a restaurant adds a staff member under 18, the restaurant must obtain the consent of that person's parent or lawful guardian where the law requires it.

10. Your rights

For the personal data described in section 3, you can:

ask for a summary of the personal data we hold about you and how we use it, and the identities of those we have shared it with;
ask us to correct, complete or update it. You can change your own password in RestoMama Admin, and a User with staff-management permission in your organisation can correct your name and contact details;
ask us to erase it, where we no longer need it for the purpose it was collected for and the law does not require us to keep it. Section 7 explains the records we must keep;
withdraw consent you have given, which will not affect what we did before. If you withdraw consent to data we need to run your account, we may not be able to keep providing RestoMama to you;
nominate another person to exercise these rights for you if you die or become unable to; and
complain to our Grievance Officer (section 11).

To exercise a right, email admin@priorityqueues.com from the email address on your account, or tell us your registered phone number so that we can verify you. We acknowledge requests within 24 hours and respond within 15 days. Some requests affect data your employer controls; in that case we will pass your request to your employer or tell you to contact them. Our page on closing or deleting a merchant account explains how accounts are closed.

11. Grievance Officer


Name	Leo Johny
Designation	Director, Priority Queues Private Limited
Email	admin@priorityqueues.com
Phone	+91 97477 47702
Address	Door No. 463, Thayyil House, Vazhukakkode, Anjumoorthy, Palakkad, Kerala 678682, India
Hours	Monday to Saturday, 9:30 am – 6:30 pm IST

We acknowledge a grievance within 24 hours and resolve it within 15 days. If you are not satisfied with our answer, you may complain to the Data Protection Board of India once its complaint powers commence on 13 May 2027. You must first use our grievance process (section 13(3) of the DPDP Act).

12. Changes to this policy

We may update this policy. If a change affects how we use your personal data in a significant way, we will tell you in RestoMama Admin or by email before it takes effect. The "Last updated" date below shows when this policy last changed.

13. Contact

Priority Queues Private Limited, Door No. 463, Thayyil House, Vazhukakkode, Anjumoorthy, Palakkad, Kerala 678682, India. Email: admin@priorityqueues.com. Phone: +91 97477 47702 (Monday to Saturday, 9:30 am – 6:30 pm IST).

Effective date: 30 September 2026 Last updated: 30 September 2026