Legal
DPDP Act notice
Last updated: 17 November 2026
How FoodPilot meets India's Digital Personal Data Protection Act, 2023: who is responsible for which data, why we process it, your rights as a Data Principal and how to use them, and how to reach our Grievance Officer.
1.About this notice
This notice is given under the Digital Personal Data Protection Act, 2023 (the “DPDP Act”) and the rules made under it. It explains, in plain English, what personal data FoodPilot processes, why, and how you can exercise your rights. A short summary in Hindi is at the end of this page.
FoodPilot is provided by [Company legal name], [Registered office address]. Our Privacy Policy has the full detail, including every provider we use.
2.Our two roles
The DPDP Act calls whoever decides why and how personal data is processed the Data Fiduciary, and anyone processing it on their behalf a Data Processor. The person the data is about is the Data Principal.
| If you are… | Data Fiduciary | Contact first |
|---|---|---|
| A restaurant owner, or a team member with a FoodPilot sign-in | FoodPilot | privacy@foodpilot.org |
| Someone who visits our website or contacts FoodPilot support | FoodPilot | privacy@foodpilot.org |
| A guest of a restaurant (QR or online order, loyalty, e-bill, feedback) | The restaurant; FoodPilot is its Data Processor | The restaurant |
| An employee of a restaurant (staff records, attendance, payroll) | The restaurant; FoodPilot is its Data Processor | The restaurant |
Where we are a Data Processor, the restaurant decides what it collects, why and for how long. We process that data only to provide FoodPilot to the restaurant, on its instructions. If you send us a request about a restaurant's data, we will pass it to the restaurant and help it respond.
3.Personal data we process and why
As Data Fiduciary for our account holders:
| Personal data | Purpose |
|---|---|
| Name, email, mobile number (optional), Google account identifier (if you use Google) | Creating your account, signing you in, sending sign-in codes and service messages |
| Restaurant, outlets and your role | Giving you the right access to the right restaurant |
| Password hash, sign-in code hashes, two-step verification secrets | Keeping your account secure |
| Session records: time, browser, IP address, last used | Showing your sessions, detecting stolen sign-ins, preventing abuse |
| Billing name, GSTIN, billing email, invoices, payment status | Billing the subscription and keeping tax records |
| AI questions, dictated or typed captures, transcripts, uploaded bill or menu photos | Answering questions and preparing drafts you asked for |
| Linked Telegram chat or WhatsApp number, messages to and from the bot | Running the bots and sending the e-bills and reports you set up |
| Support tickets and messages | Helping you |
| Server request logs, including IP address | Security, abuse prevention and fixing faults |
We do not use personal data for advertising, we do not profile you for marketing and we do not sell personal data.
4.Legal basis
- Consent. When you create an account after reading this notice, you consent to the processing described in the table above for those purposes. Optional features, such as Sign in with Google, adding a mobile number, linking Telegram or WhatsApp and using AI capture, rely on the consent you give by turning them on.
- Legitimate uses. The DPDP Act also allows certain processing without separate consent, for example where you voluntarily give us data for a specific purpose (such as writing to support) and have not said you object, or where we must process data to comply with a law (such as keeping GST records) or a court order.
For restaurants. A restaurant relies on its own legal basis for its guests' and staff data: usually consent (for example, a guest agreeing to receive offers, recorded as marketing consent), data a guest gives for a specific purpose (such as a phone number to receive an e-bill), or, for staff, the legitimate use for employment purposes.
5.Your rights
As a Data Principal you have the right to:
- Access information: a summary of your personal data we process and the processing activities, the identities of other Data Fiduciaries and Data Processors we have shared it with, and a description of what was shared.
- Correction and erasure: have your personal data corrected, completed or updated, and erased when it is no longer needed for the purpose it was given for, unless the law requires us to keep it.
- Grievance redressal: have a complaint about our handling of your data addressed by us.
- Nominate: name another person to exercise your rights if you die or become unable to do so.
- Withdraw consent at any time, as easily as you gave it (see section 9).
The Act also asks Data Principals not to impersonate others, not to withhold material information when giving data for an official document, not to file false or frivolous complaints, and to give only verifiably authentic information when asking for a correction.
6.How to exercise your rights
- In the app: change and verify your email, add or change your mobile number, manage two-step verification and sign out sessions under Settings → Security. Restaurant owners can export their restaurant's data at any time.
- By email: write to privacy@foodpilot.org from the email address on your account, saying which right you want to use. For a complaint, write to the Grievance Officer at grievance@foodpilot.org.
- Support ticket: signed-in users can also open a ticket in the app under Help & support.
- To nominate someone: email us the nominee's name and contact details from your account email.
To protect your account, we may ask you to confirm your identity, for example with a code sent to your registered email or mobile number, before acting on a request.
Guests and staff of a restaurant: contact the restaurant, which controls your data. If you write to us, we will forward your request to the restaurant promptly and help it respond.
7.Response timelines
| What | When |
|---|---|
| We acknowledge your request or grievance | Within [7 days] |
| We complete a request or resolve a grievance | Within [30 days], and in any case within the maximum period set by the DPDP Rules |
| We pass a request about a restaurant's data to the restaurant | Promptly after we receive it |
| Personal data breach: intimation to the Data Protection Board and affected Data Principals | Without delay after we become aware of it (see section 12) |
| Personal data breach: detailed report to the Data Protection Board | Within 72 hours of becoming aware, or longer if the Board allows |
If a request will take longer, we will tell you why and when to expect an answer.
8.Grievance Officer and the Data Protection Board
Our Grievance Officer answers questions and complaints about how FoodPilot processes personal data:
[Grievance Officer name], Grievance Officer
[Company legal name], [Registered office address]
Email: grievance@foodpilot.org · Phone: [Grievance Officer phone]
If you are not satisfied with how we resolve your grievance, you can complain to the Data Protection Board of India, which the DPDP Act set up for this purpose. The Act expects you to use our grievance process first.
9.Consent, withdrawal and Consent Managers
Where we rely on consent, it must be free, specific, informed, unconditional and unambiguous, given by a clear action. You can withdraw it at any time:
- unlink Telegram or WhatsApp in the app (Settings → Integrations → Messaging, or by sending /unlink to the bot);
- remove an optional mobile number or other details, or ask us to close your account, by writing to privacy@foodpilot.org.
Withdrawal does not affect processing that happened before it. After you withdraw, we stop the processing and erase the data within a reasonable time, unless the law requires us to keep it. Some features, or the whole service if you withdraw consent for your account, may then stop working.
Consent Managers. The DPDP Act lets you give, manage, review and withdraw consent through a Consent Manager registered with the Data Protection Board. FoodPilot is not yet connected to any Consent Manager. When registered Consent Managers become available and we connect to one, we will update this notice; until then, use the options above.
Guests of restaurants can withdraw consent, such as for marketing messages, by telling the restaurant, which can update the guest's marketing consent in FoodPilot.
10.Children's data
Under the DPDP Act, a child is anyone under 18. FoodPilot accounts are for adults acting for a business; we do not knowingly create accounts for children.
- FoodPilot does no tracking or behavioural monitoring of children and no advertising targeted at children. It has no advertising or analytics trackers at all.
- A restaurant that records personal data of a guest under 18 (for example, in its loyalty programme) must first obtain verifiable consent from the child's parent or lawful guardian, as the Act requires, and must not use the data in a way likely to harm the child.
- If you believe a child's data has been given to us without that consent, write to grievance@foodpilot.org and we will help remove it.
11.Data retention
We keep personal data only as long as it is needed for the purpose it was collected for, or as long as the law requires:
- sign-in codes become unusable after 10 minutes (email) or 5 minutes (phone); refresh tokens expire after 30 days;
- account and restaurant data are kept while the account is active, and for [90 days] after it is closed so it can be exported, then deleted or anonymised;
- records the law requires us to keep, such as GST invoices, are kept for the period the law sets.
Restaurants decide how long they keep guest and staff records and can delete them in FoodPilot. The full table is in our Privacy Policy.
12.Personal data breaches
We use reasonable security safeguards to prevent personal data breaches, described in our Privacy Policy. If a breach happens anyway:
- we will inform the Data Protection Board of India without delay, and send it a detailed report within 72 hours of becoming aware of the breach (or a longer period if the Board allows);
- we will inform each affected Data Principal without delay, in plain language: what happened, when, the likely consequences, what we are doing about it, what you can do to protect yourself, and who to contact;
- where the breach affects data we process for a restaurant, we will tell the restaurant without delay and give it the information it needs to notify the Board and the people affected.
13.Cross-border transfer
Your personal data is stored and processed outside India. The FoodPilot Cloud database is hosted by Supabase on AWS in Tokyo, Japan (ap-northeast-1), and our API runs on Vercel in Tokyo. Cloudflare (including Workers AI), Resend, Google and, when enabled, Anthropic process some data in other countries, including the United States.
The DPDP Act permits transfers outside India except to countries the Central Government restricts by notification. We will comply with any such restriction and with any conditions the DPDP Rules set for transfers.
14.Our commitments to restaurants as Data Processor
- We process guests' and staff data only to provide FoodPilot to the restaurant, as set out in our Terms of Service.
- We keep it separate from other restaurants' data and protect it with the safeguards in our Privacy Policy.
- Our staff can view it only through a time-limited support grant from the restaurant owner, and their actions are logged.
- We use only the sub-processors listed in our Privacy Policy and tell restaurants when that list changes.
- We help the restaurant answer Data Principals' requests and notify breaches.
- When the restaurant's account ends, we delete or anonymise its data as described in the Terms.
15.सारांश (हिन्दी में)
FoodPilot अपने खाताधारकों (रेस्टोरेंट मालिक और उनकी टीम) के व्यक्तिगत डेटा के लिए डेटा फ़िड्यूशियरी है। रेस्टोरेंट अपने ग्राहकों और कर्मचारियों के बारे में जो डेटा FoodPilot में रखते हैं, उसके लिए रेस्टोरेंट डेटा फ़िड्यूशियरी है और हम केवल डेटा प्रोसेसर हैं। हम डेटा का उपयोग सिर्फ़ सेवा चलाने, सुरक्षा और कानूनी दायित्वों के लिए करते हैं; विज्ञापन के लिए नहीं, और हम डेटा बेचते नहीं हैं। हमारा डेटाबेस भारत के बाहर, टोक्यो (जापान) में है।
आप अपने डेटा की जानकारी पाने, उसे सुधारने या मिटाने, सहमति वापस लेने और नॉमिनी चुनने का अनुरोध privacy@foodpilot.org पर कर सकते हैं। शिकायत के लिए हमारे शिकायत अधिकारी को grievance@foodpilot.org पर लिखें। समाधान से संतुष्ट न होने पर आप भारतीय डेटा संरक्षण बोर्ड (Data Protection Board of India) से शिकायत कर सकते हैं। यह सारांश केवल सुविधा के लिए है; किसी अंतर की स्थिति में अंग्रेज़ी संस्करण मान्य होगा।
16.Changes to this notice
We will update this notice when our processing or the law changes, and change the date at the top. If a change affects what you have consented to, we will tell you and, where needed, ask for your consent again.