Privacy Policy
Last updated: 8 October 2026
This policy explains what information the RestoPay Android app, the RestoPay web app and restopay.in (“RestoPay”, “we”) collect, why, and how it is protected. RestoPay is used by restaurants (“customers”) and their staff; guests of those restaurants may use table QR codes.
Information we collect
- Staff accounts: mobile number (used for OTP login), name and role (owner, counter, captain, kitchen).
- Restaurant data: restaurant details, floors and tables, menu, menu photos, orders, KOTs, bills, payments recorded in the app and bill settings such as GST details and logo.
- Customer mobile numbers on bills: restaurant staff may choose to record a customer’s mobile number on a bill (for example for delivery or takeaway). It is stored with that restaurant’s orders and is only visible to that restaurant.
- Device data: a push notification token so staff phones can receive table alerts, and the printer connections you set up.
- Guests using a table QR: we do not ask for a name, phone number or login. We record the request or order (for example “Call Captain” or the dishes ordered for Table 4) and a one-way hash of the IP address, used only to prevent spam.
App permissions
- Camera and photos: only when you choose to take or attach a photo for a menu item or bill logo. The photo is uploaded to your restaurant’s menu.
- Microphone and speech recognition: only when you tap AI Quick Add. Your phone’s speech service turns the spoken order into text; we do not store the audio.
- Bluetooth and nearby devices: to find and connect to thermal printers. On Android 11 and older, Android requires location permission for Bluetooth scanning; RestoPay does not read, collect or store your location.
- Notifications: to alert staff about table requests and orders.
AI features
AI Quick Add sends the order text and the restaurant’s menu item names to Google Gemini to match dishes. AI ingredient estimates, when turned on by the owner, send dish names to Google Gemini. No staff, customer or guest personal details are sent to Gemini.
How we use it
- To run the service: show tables and orders, send KOTs, print bills and deliver table alerts.
- To show the restaurant its own sales insights.
- To keep accounts and QR codes secure and to prevent abuse.
- To provide support when a restaurant asks for it.
We do not sell personal data and we do not use it for advertising.
Where data is stored
RestoPay runs on Google Firebase. Restaurant data is stored in Google Cloud’s Mumbai region (asia-south1), encrypted in transit and at rest, and protected by access rules so each restaurant’s staff can only see their own restaurant’s data.
Sharing
Restaurant data is visible to that restaurant’s owner and staff. We share data with service providers only as needed to run RestoPay: Google Firebase (hosting, database, storage and notifications), Google Gemini (AI features described above) and 2Factor.in (login OTP SMS). We also share data when required by law.
Retention and deletion
Data is kept while the restaurant uses RestoPay. A restaurant owner can ask us to export or delete their restaurant’s data. Staff can ask for their account and mobile number to be deleted, and customers can ask a restaurant or us to remove their mobile number from bills, by emailing yuvraj.mane@yahoo.com. We may ask you to confirm the request from the registered mobile number. We complete deletion requests within 30 days, except records we must keep by law (such as GST invoices).
Children
RestoPay is a business tool for restaurants and is not meant for children under 13.
Changes to this policy
We may update this policy as RestoPay changes. We will change the “last updated” date above, and for significant changes we will notify restaurant owners in the app or by message.
Contact
Questions or requests: yuvraj.mane@yahoo.com.