Privacy policy
Last updated 2 November 2026 · Provantic Technologies Private Limited, Bengaluru, India
EETS® is a registered trademark. EETS Partner is provided by Provantic Technologies Private Limited ("we").
1. What we collect from restaurants
| Data | Why |
|---|---|
| Mobile number of the owner and invited staff | Sign-in by one-time code; staff invites |
| Restaurant data you enter: name, address, GSTIN, FSSAI number, UPI ID, menu, tables, orders, KOTs, bills, payments, customers on credit, expenses, staff, PINs (stored only as a one-way hash), attendance and the anti-theft log | To run billing, the kitchen display, QR ordering and reports across your devices |
| Phone model and a random device id | To count devices against your plan and let you sign one out |
| Check-in selfie and one location reading (only when a staff member taps check in) | Attendance proof for the owner. Deleted after 60 days. No background tracking. |
| Plan payments: the mobile number paid for, the plan, amount, time and the order and payment reference from Razorpay (never card, UPI or bank details) | To switch your plan on, show it in the app, and handle refunds |
| Activation codes: the mobile number a code was made for, the plan and months, and when it was used | To give free months to the right number only once |
2. What we collect from guests who order by QR
Only what the guest sends to the restaurant: the dishes, a note to the kitchen, the number of guests and requests such as "call waiter". The guest may also give a first name and a mobile number; both are optional and there is no sign-in or OTP. They tell the staff whose order is whose, and staff see only the last 4 digits of the mobile. So that one phone at a time orders for a table, the guest page keeps a random id on the guest's phone; it is not linked to the phone's identity and the table is freed when the bill is settled, when staff release it or after 6 hours. We do not ask for payment details, and we do not use cookies for tracking. The guest page keeps the guest's cart on their own phone. UPI payments go from the guest's UPI app straight to the restaurant; we never see them.
3. Who processes it
| Service | Role | Where |
|---|---|---|
| Supabase | Database, sign-in, file storage | Mumbai, India (AWS ap-south-1) |
| PowerSync | Live sync between your devices | India region |
| Hostinger | Hosts eets.in and the guest QR page | Hostinger |
| Razorpay | Plan payments on eets.in/pay | India |
| SMS provider | Sends sign-in codes | India |
4. Who can see your data
You and the staff you add, each limited by the role you give them (manager, cashier, captain). A QR guest sees only your menu, their own order status and their table's bill amount. EETS support can see account, plan and device details to help you, but not your bills, customers or menu.
5. Security
Encrypted in transit and at rest. Row-level rules on the server keep each restaurant's data apart. Entries in the anti-theft log cannot be changed or deleted by anyone.
6. How long we keep it
While your account is open. If you delete your account, cloud data and sign-in are erased 7 days later. Unaccepted guest orders expire after 30 minutes. Records we must keep by law are kept only as long as the law requires.
7. Your rights
You can see, correct and export your data, withdraw consent and delete your account at any time (how). You can also complain to the Data Protection Board of India.
8. Children
EETS Partner is a business tool for people 18 and over.
9. Changes
We will show important changes in the app before they apply.
Contact and grievance officer
Grievance officer under the Digital Personal Data Protection Act, 2023 and the IT Rules, 2021: Provantic Technologies Private Limited, Bengaluru, Karnataka, India. Email provantict@gmail.com. We acknowledge within 48 hours and reply within 7 working days.