Legal

Data Processing Agreement

Last updated: 20 November 2026

The terms on which FoodPilot processes your guests' and staff personal data for your restaurant, written for the GDPR and UK GDPR and used for other countries' laws too. In short: you decide, we follow your instructions, keep the data secure and confidential, tell you about breaches, and return or delete it when you leave.

1.Scope and how this agreement applies

This Data Processing Agreement (“DPA”) is between Priya Arora (trading as FoodPilot), 185, Canal Road, Kichha, Udham Singh Nagar, Uttarakhand 263148 (“FoodPilot”, “we”), and the business that uses FoodPilot under our Terms of Service (“Customer”, “you”). It forms part of the Terms and applies whenever we process personal data on your behalf in Customer Data, as defined in the Terms.

It is written to meet article 28 of the EU General Data Protection Regulation (GDPR) and the UK GDPR, and it also applies to processing under other data protection laws (see section 13). For restaurants in India, the data processing terms in the Terms already form our processor contract under the DPDP Act, 2023; this DPA adds to them and never reduces them.

You accept this DPA when you accept the Terms; no signature is needed. If you need a countersigned copy for your records, write to privacy@foodpilot.org. If this DPA and the Terms differ about personal data, this DPA applies.

2.Roles

  • You are the controller of the personal data you or your team record in FoodPilot about your guests, staff and other people, and of the personal data your guests give through the pages we host for you (table QR ordering and payment, online store, table booking, rewards, e-bills).
  • We are your processor. We process that data only to provide FoodPilot to you.
  • For our own customers' account data (owners and team members as our users, billing and support), we are a separate controller, as described in our Privacy Policy.

3.Details of the processing (Annex 1)

ItemDetails
Subject matter and durationProviding FoodPilot under the Terms, for as long as you use it, and afterwards until the data is deleted as set out in section 10
Nature and purposeHosting, storing, syncing between your devices, displaying, computing (bills, stock, reports, forecasts, AI answers you ask for), sending the messages you set up (e-bills, booking and loyalty messages, reports), backing up, supporting you when you grant access, and deleting
Categories of peopleYour guests and customers; your staff and team members; suppliers' contact people; anyone else you record
Categories of personal dataNames, mobile numbers, emails, delivery addresses; orders, bills, visit and spend history, loyalty points, wallet and gift card balances, referral codes, feedback, birthdays and anniversaries, marketing consent, notes and custom fields; for staff: designation, pay, attendance, shifts, tips and payroll figures, emergency contacts, and (only if you turn them on) attendance photos and clock-in location. The full list is in section 3 of our Privacy Policy
Special categoriesGuests' allergies, if you record them, can be health data. Record only what you need to serve the guest safely. FoodPilot is not designed for other special category data: don't record it
FrequencyContinuous, while you use FoodPilot
WhereStored in India (Supabase, AWS Mumbai). Processed by the sub-processors in Annex 3, in the countries shown there. A working copy is also kept on your own devices for offline use

4.Your instructions

We process the personal data only on your documented instructions, including for transfers to other countries, unless a law that applies to us requires otherwise; in that case we will tell you before processing, unless that law forbids it. Your instructions are these Terms and this DPA, how you set up and use FoodPilot, and any other written instructions you give us that we agree are consistent with them.

We will tell you at once if we think an instruction breaks the GDPR or another data protection law. You are responsible for having a lawful basis for the processing and for giving the people concerned the notices the law requires.

5.Confidentiality and our staff

Everyone at FoodPilot who can access the personal data is committed to confidentiality. Our staff can see a restaurant's data only through a support grant the owner gives in the app (1 to 72 hours, read-only, can be withdrawn at any time) or, to help a restaurant that has lost its sign-in, the backup recovery access in Annex 2. Every action they take is recorded.

6.Security

We apply the technical and organisational measures in Annex 2, appropriate to the risk, as GDPR article 32 requires. We may improve them over time, but will not lower the overall level of protection. Each device you use keeps a working copy of your data for offline use; securing those devices (screen locks, updates, removing devices you no longer use) is your responsibility.

7.Sub-processors

You give us general authorisation to use the sub-processors listed in the service providers table of our Privacy Policy (Annex 3). We put each of them under data protection terms that give at least the protection of this DPA, and we remain responsible to you for their work.

Before a new sub-processor receives your guests' or staff data, we will tell the restaurant owner by email or in the app. You can object on reasonable data protection grounds within 14 days of the notice. We will then try to find a reasonable solution; if we can't, you may end the affected service or your subscription by telling us, and we will refund any fees you paid in advance for the period after it ends.

Providers that you connect yourself (your payment gateway, card machines, partner apps and systems using your API keys or webhooks) are your own processors or partners, not our sub-processors.

8.Helping you with people's rights and your duties

FoodPilot gives you tools to answer requests from your guests and staff: search, view and correct their records, export everything (Settings → Your data → Export everything) and erase a guest (Customers → the guest → Privacy → Erase customer). If we receive a request meant for you, we will pass it to you without undue delay and not answer it ourselves unless you ask us to.

Taking into account what we know about the processing, we will reasonably help you with data protection impact assessments, consultations with supervisory authorities and your other duties under GDPR articles 32 to 36, mainly by giving you the information in this DPA and our Privacy Policy and answering your reasonable questions.

9.Personal data breaches

If we become aware of a personal data breach affecting your data, we will tell the restaurant owner without undue delay, and we aim to do so within 48 hours. As far as we know them at the time (and in stages if needed), we will tell you:

  • what happened, when, and the categories and approximate number of people and records affected;
  • the likely consequences;
  • what we have done or propose to do, including to limit possible harm;
  • who at FoodPilot you can contact for more information.

We will help you notify your supervisory authority and the people affected where the law requires it. Telling you about a breach is not an admission of fault. For restaurants in India, the breach duties in our DPDP Act notice also apply.

10.Deletion or return at the end

You choose whether your data is returned or deleted:

  • Return. You can export all your data at any time, including after your subscription ends and while your account is read-only (Settings → Your data → Export everything).
  • Deletion. The owner can delete the restaurant at any time (Settings → Your data → Delete restaurant). You have 30 days to change your mind; after that we permanently delete the data. You can also ask us in writing at privacy@foodpilot.org to delete it.
  • If you do neither when your subscription ends, we keep the data read-only for at least 90 days so you can export it or come back, and we email the owner at least 30 days before we delete it.

We keep only what a law that applies to us requires: issued invoices and credit notes are kept for 8 financial years with guest and staff details removed. Deleted data can remain in backups for a short time until they roll over: usually up to 7 days in our database provider's backups, and in the nightly encrypted copies until they are replaced (the newest 2 are kept, never more than 30 days old), which are removed when the restaurant is deleted. Copies on your own devices and in your own Google Drive are under your control.

11.Information and audits

We will make available the information you reasonably need to show that this DPA is met, and allow for and contribute to audits, including inspections, by you or an independent auditor you appoint who is bound by confidentiality. Unless a supervisory authority requires it or there has been a personal data breach affecting your data, audits take place at most once a year, on at least 30 days' written notice, at your cost, first by written questions and documents, and in a way that doesn't expose other customers' data or our security.

12.International transfers

Your data is stored in India. The FoodPilot Cloud database is hosted by Supabase in Mumbai, India, and our API runs in Mumbai. India has no adequacy decision from the European Commission or the UK.

Where you are in the EU or EEA and your use of FoodPilot sends personal data to us in India, the Standard Contractual Clauses adopted by the European Commission in Decision (EU) 2021/914 (“SCCs”) are incorporated into this DPA by reference, as follows: Module 2 (controller to processor) applies, with you as data exporter and FoodPilot as data importer; the optional clause 7 does not apply; under clause 9(a), option 2 (general authorisation) applies, with the notice period in section 7; the optional wording in clause 11(a) does not apply; under clause 13, the competent supervisory authority is the one that applies under that clause to you as exporter; under clauses 17 and 18 the SCCs are governed by the law and courts of [[OWNER: EU member state whose law and courts govern the SCCs (clauses 17 and 18), e.g. Ireland]]. Annexes I and II of the SCCs are completed by Annex 1 and Annex 2 of this DPA, and Annex III by Annex 3.

Where you are in the UK, the International Data Transfer Addendum to the SCCs issued by the UK Information Commissioner applies in the same way, and where you are in Switzerland, the SCCs apply with the changes needed for the Swiss Federal Act on Data Protection.

When we send personal data on to a sub-processor in another country, we use the SCCs (Module 3, processor to processor) or another transfer mechanism the law recognises, through that provider's data processing terms.

If a public authority asks us for your personal data, we will tell you (unless the law forbids it), check whether the request is lawful, challenge it where there are grounds to, and disclose no more than is required.

13.Other countries' laws

The same commitments apply when other data protection laws cover the processing, including:

  • United States state privacy laws (such as the CCPA as amended by the CPRA): we act as your service provider or processor. We will not sell or share the personal data; not keep, use or disclose it for any purpose other than providing FoodPilot to you, or outside our direct business relationship with you; not combine it with personal data from other sources except as those laws allow; and comply with those laws and give the same level of privacy protection. We will tell you if we can no longer meet these duties, and you may then take reasonable steps to stop and fix unauthorised use.
  • UAE (Federal Decree-Law No. 45 of 2021), Singapore (PDPA 2012), Australia (Privacy Act 1988) and Canada (PIPEDA): we process the data only on your instructions, protect it as set out here, tell you about breaches as in section 9, and help you meet your duties under those laws.
  • India (DPDP Act, 2023): the data processing terms in our Terms of Service and our DPDP Act notice.

14.Liability, term and changes

Each party's liability under this DPA is subject to the limits in the Terms, except where the law does not allow it to be limited, and except that nothing limits the rights the SCCs give to the people the data is about. This DPA lasts as long as we process personal data for you. We may update it to reflect changes in the law or our sub-processors; we will give you notice of material changes as the Terms set out, and we will not reduce the protection it gives you during a period you have paid for.

Questions: privacy@foodpilot.org. Priya Arora (trading as FoodPilot), 185, Canal Road, Kichha, Udham Singh Nagar, Uttarakhand 263148.

15.Annex 2: Security measures

Where data lives and how it travels

  • FoodPilot Cloud data is stored by Supabase (PostgreSQL on AWS, Mumbai, India); the API runs on Vercel in Mumbai. Our database provider encrypts stored data and backups.
  • Every connection to FoodPilot uses HTTPS (encryption in transit).

Separating restaurants and controlling access

  • Each restaurant's data is kept apart by row-level security in the database, so one restaurant cannot read another's records even through an application bug.
  • Role-based permissions are checked on the server; refunds, price changes and purchase approvals need the right role.
  • Two-step verification is available to every account and is required for FoodPilot staff.
  • FoodPilot staff see a restaurant's data only through the owner's time-limited, read-only support grant (1 to 72 hours, withdrawable), and every action is logged.

Credentials and secrets

  • Passwords are stored only as scrypt hashes; sign-in codes, API keys and kiosk PINs only as hashes (PINs as salted PBKDF2-SHA256 hashes).
  • Authenticator secrets and payment provider keys are encrypted with AES-256-GCM.
  • Access tokens last 1 hour. Refresh tokens change on every use and expire after 30 days; reusing an old one signs the user out everywhere.
  • Sign-in attempts are rate-limited. Sign-in codes expire after 10 minutes (email) or 5 minutes (phone).

Records and monitoring

  • The restaurant's audit trail of sensitive actions is append-only.
  • API logs record no request bodies, headers or IP addresses, and replace phone numbers, emails, codes and tokens with “[redacted]”.
  • Error reports (Sentry, EU region) have personal data removed before they leave the device or server.

Backups and recovery

  • Every FoodPilot backup is encrypted with its own AES-256-GCM key, sealed with HMAC-SHA256 against changes, and its key is wrapped with RSA-OAEP-3072. A backup opens only in FoodPilot, for the owner of that restaurant.
  • FoodPilot holds a separate recovery key so it can help a restaurant that has lost its sign-in. Each use needs a super administrator signed in with two-step verification, a written reason and the owner's support grant (or a separately recorded emergency access); it is recorded in the restaurant's audit log and the owner is emailed every time.
  • Nightly encrypted cloud copies are kept in a private bucket; download links last 5 minutes.

Devices and offline use

  • Devices that sync are registered to the restaurant and can be revoked by the owner (Settings → Security → Devices), which signs the device out.
  • Offline billing runs under a signed (Ed25519) device licence; a device that hasn't connected for 21 days can no longer start new bills.
  • Offline manager approvals lock for 15 minutes after 5 wrong PINs, and each one is flagged for the owner to review.

AI

  • Nothing an AI drafts reaches the books, stock or kitchen until a person approves it. AI providers process requests only to return an answer, and we choose providers whose terms do not allow training on your data.

16.Annex 3: Sub-processors

The current list, with what each provider does and where, is the service providers table in our Privacy Policy. It includes Supabase, Vercel, Cloudflare, Resend, Google, Razorpay, Meta (WhatsApp), Telegram, the SMS provider, Anthropic (when turned on), Sentry, Google Firebase, Microsoft Clarity and Google LLC for Google Tag Manager and Google Analytics 4 (public website only, no restaurant data, no advertising) and UptimeRobot (no personal data).