RestoFlow Captain: Privacy Policy
Last updated: 23 October 2026
RestoFlow Captain is the waiter app of the RestoFlow restaurant and bar billing system, made by BinaryFlow ("we", "us"). It lets a restaurant's waiters take orders on a phone. It works only for restaurants that use RestoFlow, with a login the restaurant gives its staff. This page explains what the app handles and why.
Who is responsible for which data
The restaurant that employs the waiter decides what is entered (orders, guest names and phone numbers) and owns that data. We run the service for the restaurant and keep the data on its behalf.
What the app handles
| Data | Why | Where it goes |
|---|---|---|
| Outlet code, username and password typed at login | To sign the waiter in | Sent to the RestoFlow server over HTTPS. The password is not kept on the phone. |
| A sign-in token | To keep the waiter signed in | Kept in the phone's secure storage (Android Keystore). Removed at logout. |
| Orders: tables, dishes, quantities, serving sizes, notes | To take and track orders, and send them to the kitchen and bar | The RestoFlow server and the restaurant's own billing computer |
| A guest's name and phone number, only if the waiter types them | To open a table and (if the guest agrees) send the bill and offers by WhatsApp | The restaurant's account on the RestoFlow server |
| The waiter's name and the table they serve | To show who looks after which table | The restaurant's account |
| The phone model name given at login | To tell sessions apart | The restaurant's account |
| Error reports: the error message, app version, phone platform | To find and fix faults | The RestoFlow server. Passwords, tokens and licence keys are removed before sending. Kept for 30 days. |
| A push-notification address (only when notifications are switched on) | To alert the waiter to a customer's call when the screen is off | The RestoFlow server and Google's Firebase Cloud Messaging |
What the app does not do
- No advertising and no ad or tracking SDKs.
- It does not read your location, contacts, photos, microphone or camera.
- We do not sell or rent data to anyone.
Security
All traffic uses HTTPS. Passwords are stored on the server only as salted hashes, sign-in tokens only as hashes. A waiter's access stops at once when the restaurant switches the account off. Repeated wrong passwords lock the login for a few minutes.
How long data is kept
Orders and guest details stay in the restaurant's account for as long as the restaurant uses RestoFlow, so it can keep its records. Error reports are deleted after 30 days. When a restaurant ends its subscription it can ask us to delete its data.
Your choices and requests
A waiter can log out at any time, which removes the stored sign-in from the phone. A guest who wants their name or number removed, or anyone who wants a copy of their data, should ask the restaurant first; the restaurant can also write to us at the address below and we will help within a reasonable time.
Children
The app is for restaurant staff and is not meant for children.
Changes
If this policy changes, the new version will be on this page with a new date.
Contact
BinaryFlow Technologies Private Limited
Email: contact@binaryflow.in
Address: 01, Navarathna Complex, Koppa T M Road, Koppa, Koppa, Chikkamagaluru - 577126, India