MenuSnapp iconMenuSnapp

Privacy Policy

Effective date: July 6, 2026

This Privacy Policy explains what information the MenuSnapp iOS app and the menusnapp.com website (the "Service") collect, how it is used, and the choices you have. The short version: we collect the minimum needed to translate menus and run Premium features, we don't run ads, we don't sell your data, and we don't track you across other apps or websites.

1. Information we collect

Menu photos

When you scan a menu, the photos you take are compressed on your device and uploaded to our backend so they can be analyzed. Photos are used only to extract and translate menu content. Please photograph only menus — not people or personal documents.

Location

If you grant location permission, your approximate location at the moment of a scan is used to identify the restaurant you are in (via Google Places) and to convert prices into the right currencies. Location is optional — scanning works without it; you just won't get restaurant detection. We do not track your location in the background.

Account information

Scanning does not require an account. If you sign in (needed for Premium and purchases), we receive a basic profile from Sign in with Apple or Google: a unique user identifier and, depending on your choices, your email address and name. Authentication is handled by Supabase Auth.

Purchase and entitlement data

Purchases are processed by Apple. We (via RevenueCat) receive transaction metadata — product identifier, purchase and expiry dates, and an anonymized transaction identifier — to verify your subscription or credits. We never receive your payment card details.

Usage and history

Your scan history (restaurants, menus, dishes, which menus you have unlocked) is stored on your device and, when you are signed in, associated with your account so your entitlements and history follow you.

Diagnostics

The app reports crashes and errors to Sentry so we can fix problems. These reports include device model, OS version, app version, and — if you are signed in — your account identifier only. They never include your email, name, photos, or location.

2. How we use information

  • To provide the core service: read, translate, and structure the menus you scan, and convert prices.
  • To identify the restaurant and fetch its details, photos, and review snippets for Premium content.
  • To generate Premium content: AI meal analysis, dietary tags, and dish images.
  • To verify purchases and apply your credits or subscription.
  • To keep your history and entitlements in sync across sessions.
  • To diagnose and fix crashes and errors.

We do not use your data for advertising, we do not sell or rent it, and we do not use your photos to identify people.

3. Caching and shared results

To avoid re-analyzing identical content, translated menus and enriched dish information (descriptions, tags, generated images) are cached on our backend and may be reused when another user scans the same menu or dish. This cache is keyed to the menu and dish content — it contains no information about you and cannot be linked back to your account by other users.

4. Service providers

We share data with a small set of processors, strictly to operate the Service:

  • Supabase — hosting, database, file storage, and authentication.
  • Anthropic — AI analysis of menu photos and dish text (Claude models).
  • Google (Places API) — restaurant identification, photos, and review snippets.
  • OpenAI or Google — generation of illustrative dish images.
  • An exchange-rate provider — currency conversion rates (no personal data is sent).
  • Apple — Sign in with Apple and In-App Purchases.
  • RevenueCat — purchase verification and entitlement management.
  • Sentry — crash and error reporting.

Each provider receives only what it needs for its function and is bound by its own data-processing terms. Some providers are located outside your country (including the United States); where required, transfers rely on appropriate safeguards such as standard contractual clauses.

5. Data retention

  • Menu photos are kept only as long as needed to process the scan and operate the cache described above.
  • Cached menu and dish content (translations, generated text and images) is retained so it can be reused; it is not personal data.
  • Account, history, and entitlement data is kept while your account exists.
  • Crash reports are retained by Sentry for a limited period, then deleted.

6. Your rights and choices

  • Permissions. Camera and location access can be granted or revoked at any time in iOS Settings.
  • History. You can delete scans from your history in the app.
  • Account deletion. You can request deletion of your account and associated personal data at any time by contacting us at the address below; we will complete the deletion within 30 days.
  • Access, correction, portability, objection. Depending on where you live (e.g., under the GDPR or the CCPA/CPRA), you may have rights to access, correct, export, restrict, or object to the processing of your personal data, and the right to complain to your local data-protection authority. Contact us to exercise them; we do not discriminate against you for doing so.

7. Security

Data is transmitted over encrypted connections (HTTPS/TLS). Access tokens and entitlements are stored on your device in the iOS secure keychain. Backend data is protected with row-level security so that your account data is accessible only to you.

8. Children

The Service is not directed at children under 13 (or the applicable minimum age of digital consent in your country), and we do not knowingly collect personal data from them. If you believe a child has provided us personal data, contact us and we will delete it.

9. Changes to this policy

We may update this Privacy Policy from time to time. Material changes will be announced in the app or on this page with a new effective date.

10. Contact

For privacy questions or requests: [email protected]