Privacy Policy
Last updated: 18 OCT 2026
This Privacy Policy explains how SAEVE.APP ("Saeve", "we", "us", or "our"), operating the website and services at saeve.app, saeve.in, menu.saeve.in and the Saeve mobile apps for Android and iOS (together, the "Service"), collects, uses, shares and protects personal data. Saeve is offered to users internationally.
The Saeve mobile apps are for Restaurant Owners only. What the apps collect is summarised in our Mobile App Privacy Policy, which forms part of this Policy.
We act as the controller (a "Data Fiduciary" under Indian law) of the personal data described below. We aim to comply with applicable data protection laws, including India's Digital Personal Data Protection Act, 2023 and Rules, 2025 ("DPDP"); the EU and UK General Data Protection Regulation ("GDPR") where it applies to users in those regions; and the California Consumer Privacy Act / CPRA ("CCPA") where it applies to California residents.
By using the Service you acknowledge you have read this Policy. Where we rely on your consent, we ask for it separately and clearly.
1. Who this Policy covers
Saeve is a digital restaurant QR menu platform used by two kinds of people:
- Restaurant Owners / Admins — businesses and individuals who create an account, build menus, and manage them through our web dashboard or mobile apps. We collect the most data from this group.
- Diners — people who scan a QR code or open a link to view a restaurant's public menu. Diners do not create accounts, and we collect only limited technical and usage data from them (see Section 2 and Section 3).
This Policy applies to both groups. Where a section applies to only one, we say so.
2. Personal data we collect
From Restaurant Owners / Admins:
- Account and identity data: name, email address, phone number, business name, and password (stored only as a secure hash).
- Google sign-in data: if you sign in with Google, we receive your name, email address, email-verified status, and a Google account identifier ("sub"). We do not receive your Google password.
- Business and menu content: restaurant details, country, menu items, descriptions, prices, categories, images, logos and branding you upload or enter (see the "Menu content" note below).
- Uploaded menu files: photos or PDFs of physical menus you upload for our automated import feature.
- Billing data: subscription/purchase plan, currency, billing contact, and payment records — including your plan, its status, renewal and expiry dates, and which store it was bought through. Card and payment-instrument details are handled by Paddle (website purchases) or Google Play (Android purchases) and are not stored by us.
- Product usage data: pages and screens you visit in the dashboard and apps, features you use, and actions you complete (for example, saving a menu item), linked to your account. This includes session recordings of the dashboard and apps — see Section 3.
- Support and communications: messages and feedback you send us, and our correspondence with you.
From Diners (when viewing a public menu):
- Visit data: the menu requested, the date and time, whether you arrived by scanning a QR code or through a shared link, and the website that referred you (for example, instagram.com), if any.
- Device data: device type, operating system, browser (including in-app browsers such as Instagram's), and preferred language, read from your browser's standard request headers.
- Approximate location: country, region and city, and coordinates rounded to roughly 1 km, derived from your IP address by our hosting provider. We do not store your IP address in our own systems. We use it only at the moment of your visit to derive this approximate location and the anonymous visitor count described below. Our analytics provider also receives it, to locate aggregate page-view counts (see Section 6).
- Menu interactions: which sections and dishes appeared on your screen, how far down the menu you scrolled, how long the menu was open, which dishes and photos you opened, which categories you tapped, words you typed into the menu's search box, and whether you tapped the restaurant's call, WhatsApp, Instagram, website, directions, review or share buttons.
To count unique diners, we combine your IP address and browser details with a random value that we discard every day and store only the resulting one-way code. That code cannot be reversed, and it cannot connect your visits on different days, or link you to a person.
Note on menu content: Menu items, prices, images and branding are the restaurant's business content, not personal data of diners. If a Restaurant Owner includes personal data of any third party in their content, the Restaurant Owner is responsible for having a lawful basis to do so, and acts as the controller for that content.
3. How we use personal data, and our legal basis
| Purpose | Legal basis (GDPR terms, where applicable) |
|---|---|
| --- | --- |
| Create and secure your account; build, host and display menus; generate QR codes | Performance of a contract; consent under DPDP |
| Show Restaurant Owners analytics about their own menu (see below) | Legitimate interests (ours and the restaurant's) |
| Run the automated menu-import feature (see Section 5) | Consent / your request to use the feature |
| Take payments and manage subscriptions and one-time purchases | Performance of a contract |
| Security, fraud prevention and service integrity | Legitimate interests; legal obligation |
| Product analytics, session recordings and Service improvement (Restaurant Owners) | Legitimate interests; consent where required |
| Marketing (Restaurant Owners only) | Consent (see Section 4) |
We use personal data only for the purposes for which it was collected, or a compatible purpose, in line with the purpose-limitation principle.
Menu analytics for Restaurant Owners. The diner data in Section 2 is used to give each restaurant a report about its own menu — for example, how many people viewed it, at what times, which dishes were looked at and opened, what diners searched for, and how many tapped to call or get directions. Restaurants see aggregated figures only: they do not see any individual diner's visit, device, location or identity. Visits by the restaurant's own signed-in staff are excluded from these figures.
Session recordings (Restaurant Owners only). To find and fix problems in the dashboard and apps, we record how pages and screens are used — a visual replay of what appeared and what was tapped or clicked. Password fields are always masked. Recordings may show other information visible on screen at the time, such as your name, email address and menu content. Public menu pages are never recorded.
4. Marketing communications
First-party marketing. With your consent, we may use your contact information to send you updates, offers, tips and promotional messages about Saeve and its features. You give this consent through a separate opt-in when you sign up or in your account settings — it is not bundled into your acceptance of these terms.
Associated products. Separately, and only if you give distinct, specific consent, we may send you information about other products and services associated with Saeve. We will identify what these are, and if any are operated by a third party we will tell you before sharing your contact details.
Your control. You can withdraw marketing consent at any time — every marketing email contains an unsubscribe link, and you can also change your preferences in account settings or by contacting us. Withdrawing consent is as easy as giving it, and does not affect the core Service.
We do not send marketing to Diners, and we do not use Diner data for advertising.
5. Automated menu import and third-party AI processing
When you use our menu-import feature, the photos or PDFs of menus you upload are processed using automated systems, including third-party artificial-intelligence providers (for example, OpenAI and Anthropic), solely to extract menu structure (items, categories, prices) into a draft that you review before publishing. We do not auto-publish this output.
- To run this feature, your uploaded content is transmitted to these AI providers and may be processed on their infrastructure, which may be located outside your country (see Section 8).
- We use these providers under their business/API terms and data-processing agreements. Under those terms, content submitted through their APIs is not used to train the providers' AI models by default, and we do not authorise such training. Where available, we use retention-minimising controls (such as zero-data-retention arrangements).
- We rely on these providers' contractual commitments and are not otherwise responsible for their independent conduct.
- By using the menu-import feature, you acknowledge and consent to this third-party AI processing. If you do not want your content processed this way, do not use the feature.
6. How we share personal data
We do not sell your personal data, and we do not share it for targeted advertising. We share it only with the following.
Service providers (processors), who act on our instructions and are bound to protect the data:
- Hosting and infrastructure providers — including Vercel (website hosting, IP-based approximate location, and privacy-friendly page-view measurement) and our cloud database and server hosts.
- Product analytics and session recording — PostHog, for Restaurant Owners' use of the dashboard and apps, and for counting public-menu page views and shares. For those counts PostHog receives the diner's IP address to derive an approximate location, under a random identifier that is not linked to any profile.
- Email delivery providers.
- Payments and subscriptions — Paddle (Paddle.com), the Merchant of Record for purchases on our website, which processes your payment and billing details under its own privacy policy; Google Play, for purchases in the Android app; and RevenueCat, which manages subscription status across the website and apps. RevenueCat receives your Saeve account identifier, the email address you give at checkout, and records of your purchases, but not your card details.
Others:
- Restaurant Owners — aggregated analytics about their own menu only, as described in Section 3. No individual diner's data is shared with restaurants.
- AI providers — OpenAI, Anthropic and/or similar, for the menu-import feature (see Section 5).
- Authentication providers — Google, when you choose Google sign-in.
- Legal and safety — where required by law, regulation, legal process, or to protect our rights, users, or the public.
- Business transfers — in connection with a merger, acquisition or sale of assets, subject to this Policy.
7. Cookies and similar technologies
Dashboard and website (Restaurant Owners and visitors to saeve.app). We use cookies and similar technologies to:
- keep you signed in securely (our dashboard uses secure, httpOnly authentication cookies);
- remember preferences; and
- measure and improve usage (product analytics and session recordings, as described in Section 3).
Public menu pages (Diners). Public menu pages place no cookies and store nothing on your device — no local storage and no tracking identifiers. The menu analytics in Section 2 are recorded by our own servers, and the short-lived identifier that groups the events of a single visit exists only in the open page's memory and disappears when the page is closed.
You can control cookies through your browser settings.
8. International data transfers
Saeve operates globally, and our providers may process data in India, the United States, the European Union, and other countries. This means your personal data may be transferred to, and processed in, a country other than the one you live in, which may have different data-protection laws.
Where we transfer personal data internationally, we take steps to ensure it remains protected.
9. Your rights
Subject to applicable law, you have the right to access, correct, and erase your personal data, to withdraw consent you previously gave, and to complain to us or a regulator.
- India (DPDP): you also have the right to nominate another person to exercise your rights, and to grievance redressal via our Grievance Officer, with escalation to the Data Protection Board of India.
- EEA / UK (GDPR): you also have the rights to restrict or object to processing, to data portability, and to lodge a complaint with your local supervisory authority. Where processing is based on consent, withdrawal does not affect prior processing.
- California (CCPA/CPRA): you have the rights to know, delete, and correct personal information, and to opt out of "sale" or "sharing" — note that we do not sell or share personal data. We will not discriminate against you for exercising these rights.
Diners: because we do not keep your IP address or any identifier that persists beyond a single day, we generally cannot connect stored menu analytics back to you, and so may be unable to locate data about you specifically. You can still contact us with any request.
To exercise any right, contact us using Section 12. We will respond within the timelines required by the law that applies to you.
10. Account deletion and data retention
Deleting your account (Restaurant Owners). You can ask us to delete your account at any time at saeve.app/delete-account: sign in, confirm your account email, and submit the request. If you cannot sign in, email us from the address registered on your account, using the contacts in Section 12, with the subject "Delete my account". We will confirm the request by email and delete your account within 30 days. Deleting your account deletes your restaurants, menus, menu content, images and their menu analytics. We may keep limited records where the law requires (for example, payment and tax records), and for no longer than that law requires. You can also delete an individual restaurant yourself from its settings.
Retention. We keep personal data only as long as necessary for the purposes in Section 3:
- Account and menu data — for as long as your account is active, then deleted as described above.
- Diner menu analytics — kept with the restaurant's menu for as long as that restaurant exists on Saeve, and deleted when the restaurant is deleted. They contain no IP address or persistent identifier.
- Product analytics and session recordings — kept for the retention period of our analytics provider, after which they are deleted automatically.
- Backups — overwritten on a rolling basis.
When data is no longer needed, we delete or anonymise it.
11. Security, and children
We use reasonable technical and organisational measures — including hashed passwords, encrypted connections, access controls and secure hosting — to protect personal data. No system is perfectly secure, but we work to protect your data and will notify affected users and the authorities of a personal-data breach where required by law.
Restaurant Owner accounts are for users aged 18 or over. We do not knowingly create accounts for children. Where we become aware that we hold a child's personal data without verifiable parental consent, we will delete it. Public menus can be viewed by anyone; we do not collect any data that identifies a diner, whatever their age.
12. Contact
For any privacy question, request, or complaint, contact:
Email: saeveapp(at)gmail(dot)com / hello(at)dexocode(dot)com
13. Changes to this Policy
We may update this Policy from time to time. We will post the updated version here with a new "Last updated" date and, for material changes, notify Restaurant Owners by email or in-app. Continued use of the Service after changes take effect means you accept the updated Policy.