Legal
Privacy Policy
Last updated: 17 November 2026
This policy explains what personal data FoodPilot collects, why, who helps us process it, where it is stored and how long we keep it. In short: we use data to run the service, never for advertising, and we do not sell it.
1.Who we are and what this covers
FoodPilot is an AI-first restaurant operating system provided by [Company legal name] (CIN [CIN]), registered office at [Registered office address] (“FoodPilot”, “we”, “us”).
This policy covers the website at foodpilot.org, the web app at foodpilot.org/app, the FoodPilot Cloud API, guest pages we host for restaurants (QR table ordering, online store, rewards and e-bill links) and the FoodPilot Telegram and WhatsApp bots.
We handle personal data in two different roles:
- For our own customers. For restaurant owners, their team members who sign in, and anyone who contacts us, we decide why and how the data is used. Under India's Digital Personal Data Protection Act, 2023 (DPDP Act) we are the Data Fiduciary.
- For restaurants. A restaurant using FoodPilot decides what it records about its guests and staff. We store and process that data only on the restaurant's instructions, so the restaurant is the Data Fiduciary and we are its Data Processor. If you are a guest or employee of a restaurant, please contact the restaurant first; we will help it answer you.
Our DPDP Act notice explains these roles and your rights in more detail.
2.The offline demo
You can open the live demo without an account. The demo restaurant is generated in your browser and everything you do in it is saved only in your browser's local storage on that device. It is not sent to us. Clearing your browser's site data, or using “Reset demo data” in Settings, removes it.
Two demo features talk to other services directly from your browser:
- Voice input uses your browser's built-in speech recognition. Depending on the browser, the browser maker may process the audio (for example, Google Chrome sends it to Google). We do not receive the audio.
- Demand forecast weather is fetched from Open-Meteo (open-meteo.com) for the outlet location set in the app. Like any website, Open-Meteo receives your IP address with the request.
3.Personal data we collect
Your account and sign-in
- Your name, email address and, if you add one, your mobile number.
- Your restaurant's name, outlets, GSTIN (optional) and your role in the restaurant (owner, manager, cashier, chef and so on).
- If you set a password, a one-way scrypt hash of it, never the password itself.
- If you use Sign in with Google: the Google account identifier, name and verified email address in the token Google gives us. We do not receive your Google password, and we do not store your Google profile photo.
- One-time sign-in codes sent by email or SMS. We keep only a keyed hash of each code; email codes expire after 10 minutes and phone codes after 5 minutes.
- If you turn on two-step verification, an encrypted authenticator secret and hashed single-use recovery codes.
Sessions and devices
For each sign-in we record the time, the browser's user-agent string, the IP address and when the session was last used, so you can review your sessions and sign out devices you don't recognise. Access tokens last 1 hour; refresh tokens rotate on every use and expire after 30 days. Devices that sync with FoodPilot Cloud are registered to your restaurant.
Restaurant operating data
Orders, bills and GST invoices, menus and recipes, stock and purchases, suppliers, expenses, reports and the restaurant's audit trail (who did what, and when). This is mostly business data, but it can include names of staff and guests.
Data restaurants record about their guests
When a restaurant uses the guest and loyalty features, it may record a guest's name, mobile number, email, visit and spend history, loyalty points, wallet balance, referral codes, allergies, birthday or anniversary, marketing consent, feedback and any custom fields it adds. Guests who order through a table QR or a restaurant's online store give their name and mobile number. A digital bill (e-bill) is sent to the number or address the restaurant enters, and the bill page shows the guest's name with a masked phone number.
Data restaurants record about their staff
Name, phone, designation, department, pay type and salary or hourly rate, joining date, skills, emergency contact, shifts, attendance, tips and payroll figures. Kiosk PINs are stored only as salted hashes. If the restaurant turns them on (both are off by default), attendance can also record a small photo and the device's location when someone clocks in or out, to confirm they are on site.
Subscription and billing
Your plan, FoodPilot invoices, billing name, GSTIN, state and billing email, and payment status. When you pay online, the payment is handled by our payment gateway (for example, Razorpay). We do not receive or store card numbers, UPI PINs or bank passwords.
AI, voice and photo capture
Questions you ask the AI assistant; text you type or dictate to capture purchases, expenses or orders; transcripts of voice notes; and photos or PDFs of supplier bills or menus that you ask FoodPilot to read. We store the text, the transcript and the draft the AI produced; we do not keep the uploaded photo, PDF or audio after it has been read. See section 5.
Messaging channels
If you link FoodPilot's Telegram bot or WhatsApp number to your account: your chat ID or WhatsApp number, display name, the messages you send to the bot, and a log of messages FoodPilot sends (such as e-bills and scheduled reports) with their recipient and status.
Support
Support tickets and replies. If a restaurant owner grants FoodPilot support temporary access (between 1 and 72 hours, read-only, revocable at any time), our support staff can view that restaurant's data to help, and every action they take is recorded in our internal audit log.
Server logs
Our API servers log each request (time, method, address, response status and the requesting IP address) for security, abuse prevention and debugging. Login tokens are removed from these logs, and sign-in codes are never written to them in production.
What we do not collect
We do not use advertising or analytics trackers, we do not build advertising profiles and we do not sell personal data. See the Cookie Policy for what is stored on your device.
4.How we use personal data
- To provide FoodPilot: sign you in, keep devices in sync, run billing, kitchen, stock and reports, deliver e-bills and scheduled reports you ask for, and host the restaurant's guest pages.
- To run AI features you use: answer questions, prepare drafts from voice, text or photos, and calculate forecasts and insights.
- To bill for the subscription and keep tax records.
- To support you when you open a ticket or grant support access.
- To keep FoodPilot secure: rate-limit sign-in attempts, detect stolen refresh tokens, keep audit trails and investigate abuse.
- To meet legal obligations, such as GST record keeping or a lawful request from an authority.
- To send service messages, such as sign-in codes, invoices and important changes to the service.
We do not use personal data for advertising. If we want to send you product news in future, we will ask for your consent first, and you can withdraw it at any time. We process data that restaurants record about guests and staff only to provide FoodPilot to that restaurant.
The legal basis for each use under the DPDP Act (consent or a legitimate use) is set out in our DPDP Act notice.
5.AI features
FoodPilot's AI drafts and explains; a person always confirms. Nothing an AI drafts reaches the books, stock or the kitchen until someone approves it, and the assistant cannot change prices, issue refunds, approve purchases, edit payroll or send messages.
Depending on how FoodPilot Cloud is configured, AI requests are answered by:
- Cloudflare Workers AI (the default), running on Cloudflare's global network;
- Anthropic Claude, when enabled, processed in the United States; or
- FoodPilot's built-in rules engine, which sends nothing to a third party.
To answer a question, the AI receives the question and the business figures it needs: for example sales summaries, dish performance, stock levels, expenses, staff-level discount and void anomalies (with staff names), and a short list of regular guests who haven't returned (name, visits, lifetime spend and marketing consent; not phone numbers). Photo and document reading sends the image or PDF, and voice notes from Telegram or WhatsApp are sent for speech-to-text. AI providers process this data only to return an answer to us. We do not use your data to train AI models.
7.Where your data is stored
Your data is stored outside India. The FoodPilot Cloud database is hosted by Supabase in Tokyo, Japan, and our API runs in Tokyo. Some providers listed above process data in other countries, including the United States.
The DPDP Act allows personal data to be transferred outside India except to countries the Central Government restricts by notification. We will follow any such restriction, and we choose providers that commit to protecting the data they process for us. If we move storage to India, we will update this policy.
8.How we protect data
- Connections to FoodPilot use HTTPS.
- Each restaurant's data is separated by row-level security in the database, so one restaurant cannot read another's records even through an application bug.
- Permissions by role are enforced on the server; refunds, price changes and purchase approvals need the right role.
- Passwords (scrypt), sign-in codes, API keys and kiosk PINs are stored only as hashes; authenticator secrets are encrypted.
- Refresh tokens rotate on every use, and reusing an old one signs that user out everywhere.
- Two-step verification is available to every account and is mandatory for FoodPilot staff.
- The audit trail of sensitive actions is append-only.
- FoodPilot staff can see a restaurant's data only through a time-limited grant from the owner, and their actions are logged.
No system is perfectly secure. If a personal data breach happens, we will notify as described in our DPDP Act notice.
9.How long we keep data
| Data | How long |
|---|---|
| Email sign-in codes | 10 minutes, then unusable |
| Phone sign-in codes | 5 minutes, then unusable |
| Access tokens / refresh tokens | 1 hour / up to 30 days |
| Session history (device, IP, last used) | While your account is active, so you can review past sign-ins |
| Account and restaurant data, including guest and staff records | While the account is active; after it is closed, [90 days] so it can be exported, then deleted or anonymised |
| Invoices and records we must keep by law (for example GST) | For the period the law requires |
| Emailed report download links | 30 days |
| Demo workspace | In your browser until you reset it or clear site data |
Restaurants decide how long they keep their guests' and staff records within FoodPilot and can delete them. Deleted records may remain in backups for a limited time before they are overwritten.
10.Your rights and choices
Under the DPDP Act you can ask for a summary of your personal data and how it is processed, have it corrected, completed, updated or erased, withdraw consent, nominate someone to act for you, and have a grievance addressed. You can:
- change and verify your email, add or change your mobile number, manage two-step verification and sign out other sessions in the app under Settings → Security;
- as a restaurant owner, export your restaurant's data from the app at any time;
- write to privacy@foodpilot.org for anything else, including closing your account.
If you are a restaurant's guest or employee, contact the restaurant; if you write to us instead, we will pass your request to the restaurant and help it respond. How requests work, response times and how to complain are in our DPDP Act notice.
11.Children
FoodPilot is a service for businesses. Account holders must be at least 18 years old. We do not knowingly collect children's personal data for our own purposes, and we never track, behaviourally monitor or target advertising at children.
If a restaurant records personal data of a guest under 18 (for example in its loyalty programme), the restaurant must obtain verifiable consent from the child's parent or lawful guardian as the DPDP Act requires.
12.Changes to this policy
We will update the date at the top of this page when we change this policy. If a change is significant, we will also tell account holders by email or in the app before it takes effect.
13.Contact and grievances
[Company legal name], [Registered office address].
- Privacy questions and requests: privacy@foodpilot.org
- Grievance Officer: [Grievance Officer name], grievance@foodpilot.org, [Grievance Officer phone]
- Product support: support@foodpilot.org
If you are not satisfied with our response, you can complain to the Data Protection Board of India.