Tableside Privacy Policy

Effective 21 October 2026 · Applies to Tableside on the Apple App Store (iPhone and iPad) and on Google Play (Android)

Tableside estimates the calories and macronutrients of restaurant dishes from a photo of the menu or of the plate, and lets you keep a food log. This policy explains what data the app handles, where it goes and why. It covers both the iOS app and the Android app, which work the same way. Where they differ, we say so.

In this policy, “we”, “us” and “our” mean the developer of Tableside. You can reach us at sifatullahshah27@gmail.com.

The short version

1. Data we collect and why

Menu and plate photos you choose to read

You photograph a menu (up to four pages) or a plate, or pick a photo with the system photo picker. Nothing is sent while you frame the shot. When you tap Read, the line beside that button tells you where the photo goes. The app then shrinks the photo (at most 1600 pixels on the long side) and sends it over an encrypted connection to our server (Google Cloud Functions, in the United States).

Our server passes the photo to Anthropic, whose Claude AI model reads it. If Claude is busy or does not answer in time, the server passes it to Google's Gemini API instead. Only the photo and our fixed instructions to the model are sent. Your name, email, account ID, weight, targets and food log are never sent to either AI provider. The dish names and calorie estimates come back to your phone.

We do not store the photo on our servers: it is held in memory while it is read and then discarded. The reading results are not stored on our servers either. Our server logs record that a reading happened, which model answered, how long it took and any error code. They never contain the image or the results. Under Anthropic's commercial terms and the Gemini API terms for paid use, neither company uses these photos to train its models. Each keeps API data only for a limited period, for safety and abuse monitoring, and then deletes it.

Please photograph the menu or the food only, without people or documents in the frame.

Dish confirmations

When you confirm a dish on a plate reading, the app sends that confirmation to our server: the ID of the reading and of the item, the dish name, and the time. We keep these to improve the accuracy of future readings. A confirmation record does not contain your name, email, account ID or photo.

Usage statistics (Firebase Analytics)

The version of the app downloaded from the stores records a fixed list of events: for example that onboarding moved to the next step, a reading started, succeeded or failed, a meal was logged, a weigh-in was saved, or the paywall was shown. Events can include the type of reading, the number of dishes found, the meal slot, a streak length or the plan selected. Firebase also collects standard information: a random app-instance ID, device model, operating system and app version, language, and an approximate country or region derived from your IP address. On iOS, Firebase also records in-app purchase events automatically.

Before any event leaves your phone, the app removes your weight, your age, calorie figures, your goal, your activity level and restaurant names. No event contains a photo, a dish you ate or anything you typed. Analytics is not linked to your account, and we do not set a user ID in it. We use it only to see which features are used and what to fix. There is no in-app switch for analytics. Development builds send nothing.

Crash reports (Firebase Crashlytics)

If the app crashes, Crashlytics sends a diagnostic report: the stack trace, device model, OS version, app version and an installation ID. We use these reports only to fix bugs. They are not linked to your account.

App integrity checks (Firebase App Check)

Every request to our server carries a token from Apple App Attest or DeviceCheck (iOS) or Google Play Integrity (Android). It proves the request comes from a genuine copy of Tableside and keeps the service available for everyone. It identifies the app, not you.

Purchases and subscriptions

Tableside Premium is sold and billed by Apple (App Store) or Google (Google Play). We never see your payment card or billing details.

Notifications

All of Tableside's notifications are created on your phone. If you allow them, the app can remind you before dinner, send a weekly summary, tell you when a menu saved while you were offline has been read, and tell you before a free trial ends. You choose which reminders you get under You → Reminders. No push service is used, and nothing about your notifications is sent to us.

2. If you sign in (optional)

Signing in exists so that your history, targets and subscription can be restored after a reinstall or on another phone. You can sign in with Apple (iOS) or Google (iOS and Android), through Firebase Authentication. When you do, we store the following under your account:

Signing out keeps everything on your phone and stops the backup. It deletes nothing. If a phone already holds data from no account or from another account, the app asks whether to add it to your account or start fresh.

3. Data that stays on your device

If you do not sign in, the following never leave your phone, and we cannot see them: your profile and body measurements, targets, logged meals, weigh-ins, saved dishes, menu readings, streak and meal photos. They are stored in the app's own database on your device, and deleting the app deletes them.

4. Health information

Your meals, calorie and macronutrient figures, weight, height, age, sex, goal, activity level and dietary choices are health information. We treat it with extra care:

Residents of Washington, Nevada and other US states with consumer health data laws can read our Consumer Health Data Privacy Policy.

5. Device permissions

PermissionWhyIf you decline
CameraTo photograph a menu or a plate. Nothing is sent while you frame the shot.You can pick a photo instead, or type what you ate.
PhotosNot requested. The system photo picker hands the app only the photo you choose.—
NotificationsOptional reminders, all created on your phone.Nothing else changes.

On Android the app also uses internet access, network status (to hold readings while you are offline), Google Play Billing, and permission to re-arm your reminders after the phone restarts. Tableside does not request your location, contacts, microphone or any other permission, and it does not use the advertising identifier on either platform.

6. What we do not do

7. Who processes data for us

ProviderWhat forPolicy
Google (Firebase: Authentication, Cloud Functions, Firestore, Cloud Storage, Analytics, Crashlytics, App Check)Hosting our server, sign-in, account backup, usage statistics, crash reports, integrity checksFirebase privacy · Google Privacy Policy
Anthropic (Claude API)Reading menu and plate photos (first choice)Anthropic Privacy Policy
Google (Gemini API)Reading menu and plate photos (backup)Gemini API Terms · Google Privacy Policy
AppleSign in with Apple, App Store subscriptions, App Attest and DeviceCheckApple Privacy Policy
Google PlayGoogle sign-in, Play subscriptions, Play IntegrityGoogle Privacy Policy

These providers act on our behalf, under their own terms and security measures. Nobody else receives your data.

8. How long data is kept

DataKept
Photo sent for readingNot stored by us. Held briefly by the AI provider under its API terms, then deleted.
Your account, food log, profile and meal photosUntil you delete your account. A meal you delete is marked deleted so the deletion reaches your other phones, and is removed for good when the account is deleted.
Dish confirmationsKept to improve readings. Not linked to you.
Android subscription check recordsAs long as needed to support the subscription and handle disputes, including after account deletion, because the store keeps billing independently of your account.
Server logs (no images)Up to 30 days
Usage statisticsUp to 14 months
Crash reportsUp to 90 days
Data on your deviceUntil you delete it or uninstall the app

9. Your rights and choices

Depending on where you live (for example the EU, the UK, Switzerland or a US state with a privacy law), you may also have the right to access, correct, delete or export your personal data, to restrict or object to its processing, to withdraw consent, and to complain to your data-protection authority. Email sifatullahshah27@gmail.com. We reply within 30 days, and we will not treat you differently for using your rights. Deleting your data does not cancel a subscription: cancel it in the App Store or Google Play.

10. Legal bases (EEA, UK and Switzerland)

We process your data to provide the service you ask for (reading the photos you send, keeping and backing up your log, checking your subscription), on our legitimate interest in keeping the app secure, reliable and improving (integrity checks, crash reports, usage statistics, dish confirmations), and to meet legal obligations (purchase records). Health information is processed only with your explicit consent, which you give by entering it and, if you sign in, by choosing to back it up. You can withdraw that consent at any time by deleting your data.

11. US state privacy laws

We do not sell personal information or share it for cross-context behavioural advertising, and we have done neither in the past 12 months. We use sensitive personal information, such as health information, only to provide the app. You can exercise your rights through the in-app tools above or by email. See also our Consumer Health Data Privacy Policy.

12. International transfers

Our servers and our providers' servers are mainly in the United States, so your data may be processed outside your country. Where the law requires it, these transfers are covered by the providers' standard contractual clauses and, where they participate, the EU-US Data Privacy Framework.

13. Security

All traffic between the app and our server is encrypted with HTTPS. Our server only accepts requests that pass App Check, and account requests also need a valid sign-in token. The database and photo storage are closed to direct access: only our server code can read or write them. The AI provider keys are kept on the server and never ship in the app.

14. Children

Tableside is for adults. The app asks your age during setup and does not continue for anyone under 18. It is not directed at children, and we do not knowingly collect data from anyone under 18. If you believe a child has used Tableside with an account, email us and we will delete it.

15. Not medical advice

Calorie and nutrition figures in Tableside are AI estimates from a menu's wording or a photo of a plate. They can be wrong, and they are not medical, dietary or allergy advice. Tableside does not detect allergens. If you have an allergy or a medical condition, check with the restaurant or a professional.

16. Changes to this policy

If we change how the app handles data, we will update this page and its effective date before the change ships, and summarise significant changes in the app's release notes.

17. Contact

Questions, requests or complaints: sifatullahshah27@gmail.com