Chomp Privacy Policy

Effective date: November 16, 2026 · Last updated: November 16, 2026

Chomp is made by Spill the Tea LLC, c/o Registered Agents Inc, 30 N. Gould St. Suite R, Sheridan, WY 82801, United States ("we", "us", "our"). This policy explains what information the Chomp app (the "app") uses, where it is kept, who else handles it, how long we keep it and the choices you have. Questions: contact@chompfit.com.

The short version

1. Information that stays on your device

WhatWhy we use it
Your plan answers: goal (lose fat, maintain, build muscle), sex (female, male or "prefer not to say"), birthday, height, weight, goal weight and pace, activity level, eating style, foods you'd rather skip, favorite chains, units (lb or kg)To calculate your calorie, protein, carb and fat targets for each meal and to rank meals for you. All of this math runs on your phone.
Saved meals: the meals you save — the restaurant, the meal and when you saved itSo you can find your go-to orders again. Their numbers and fit are worked out again from the menu each time you open them.
App settings: which setup questions you've answered, when you finished setup, whether we've already asked about location, and whether usage analytics are onTo resume setup where you left off, to avoid asking twice and to respect your analytics choice (section 10).
Your random app ID (see section 3)Sent with each request to our server and, while usage analytics are on, with each usage event (section 6).
Downloaded restaurant data: map areas and menusTo make the app fast and use less data. These files contain restaurant information, not information about you, although they reflect the areas you have looked at. Your phone may clear them at any time.
A location you type in, and up to 3 recent ones: a city or ZIP code you pick instead of your position, and the last ones you picked before itSo the map and lists center there until you choose "Use my location", and you can switch back to a recent one in one tap.

This information is kept in the app's private storage on your device. On iPhone, your plan answers and saved meals are not included in iCloud backups; on Android, the app opts out of Android's automatic cloud backup. It stays until you change it, delete it in the app (You › Privacy › Delete data on this phone) or delete the app.

2. Health and body information

The app asks for your height, weight, goal weight, birthday and sex because calorie needs depend on them. On your device, it uses a standard formula (Mifflin-St Jeor) to estimate how much energy you use, adjusts that for your activity level and goal, and splits it into a target for each meal.

3. What our server receives

To show restaurants and menus, the app asks our server for them. Every request includes:

We use this to answer the request and to prevent abuse — for example, a daily limit on how much of the map one network or one app installation can download. Most counters are in memory; the NYC menu-acquisition limit stores a salted daily rotating installation code, UTC day and restaurant IDs so a server restart does not reset the limit. We store the resulting restaurant-menu facts and acquisition jobs, not your body/goal inputs. Reports and explicit menu requests are also stored (section 5). Our server software does not store raw app IDs, IP addresses, search words or the rounded viewport in those database rows. Its application logs don't record them; when something goes wrong, it logs the type of request and the restaurant it was about, not who made it. One exception: a shortened network address of the first request after each server restart is logged, to check the server's setup. Our hosting provider (Railway) also keeps its own routine request logs, which can include your IP address, the address of the request (and so any search words and rounded location in it) and the user agent, for a limited time under its log-retention settings (section 9).

We never receive the plan answers listed in section 1, your exact GPS position, your contacts, your photos or anything else stored on your phone.

4. Location

5. Reports, menu requests and automatic NYC menu discovery

Report a problem. On a restaurant's page or a meal's page you can tell us that something looks wrong — calories or macros, a missing item, opening hours, a restaurant that has closed, its location, or the wrong menu. The app sends:

Get this menu. On a restaurant we don't have a menu for, "Get this menu" sends which restaurant you'd like us to add — nothing you type.

We store reports and menu requests with a one-way coded form of your app ID (a salted hash) — never the ID itself and never your IP address — so we can count requests and ignore duplicates. We use them to fix our data and to decide which menus to add next. Our usage analytics also note that a report or request was sent (unless you've turned them off), and for a report the kind of problem — never your message. Please don't include personal or medical information in your message — the form says so too. We keep reports and menu requests for as long as we need them to correct our data and decide which menus to add, and delete them sooner if you ask (section 10).

While you view NYC places in the foreground, the app can also request actual menus for nearby restaurants without a separate form submission. The server stores the restaurant IDs and a daily rotating, purpose-separated installation code and network code for request deduplication and the daily limit. Restaurant sites and the estimation provider receive public restaurant menu text only, without your app ID, viewport, body information or search words. Cached menus are shared restaurant facts. Local downloaded-menu and readiness caches are cleared by Delete data on this phone.

Automatic NYC demand/quota rows are kept for the current UTC day and removed at API startup and hourly after that day ends, including while acquisition is paused. A server outage can delay cleanup until restart. Reports and explicit legacy menu requests are kept as described above.

6. Service providers

We use these companies to run parts of the app. They handle information on our behalf, under terms that require them to protect it and use it only to provide their service to us.

ProviderWhat it does for usWhat it receives
AppleApp Store downloads, in-app purchases and subscriptions, and maps on iPhone (Apple Maps)Your purchase and payment details (we never see your card number or Apple ID) and map requests for the areas you view, under Apple's privacy policy
SuperwallShows the subscription screens, runs App Store purchases and Restore Purchases through Apple's StoreKit, and tells the app whether your subscription is activeYour App Store purchase and subscription records for this app (product, price, free trial or offer, transaction dates and renewal status); which subscription screens were shown and what you chose; app activity Superwall records on its own, such as app opens and sessions; device and app details such as model, iOS version, language, region, currency, time zone, app version and the identifier iOS gives apps from the same developer; and an identifier Superwall creates for the installation. If you came to the App Store from an Apple Search Ads ad, Superwall also receives the attribution token Apple provides, which tells it which ad campaign led to the download. We don't send Superwall your app ID, your plan answers, your location or anything else about you.
MixpanelUsage analytics — which features are used, where people stop during setup and how many start a trial or subscribe. You can turn this off (section 10).Events such as "setup step viewed", "plan shown", "location access allowed or not", "map viewed" (and whether it shows your area or the default one), "pin tapped", "menu opened" and "meal opened" (with whether the numbers are official or estimated), "order button tapped" (with which service), "Make it fit used" (with how many changes it suggested), "meal saved", "report sent" (with the kind of problem) and "menu requested"; and subscription events — "subscription screen shown" and how it ended, "free trial started", "subscription purchased" or "purchase not yet confirmed", and "restore result", with the plan (yearly or monthly). They are tied to your random app ID and to a random identifier Mixpanel creates on your phone. Mixpanel adds device and app details on its own — device model and maker, iOS version, screen size, the app's version and Mixpanel's own version — and records when it connects its identifier to your app ID and when usage analytics starts or is turned back on. We turn off Mixpanel's automatic tracking of app opens, sessions and purchases. Mixpanel receives your IP address with each upload, as any internet service does, and we tell it not to use the address to work out where you are. Not your body details, your answers, your targets, your location or your search words.
SentryCrash and error reports, and how often the app crashesWhen the app hits an error or crashes: what went wrong and where in the app's code, device details (model, iOS version, memory, screen size, language and time zone), the app version, and a short record of what the app did just before (for example, that a request to our server failed) — with search words, locations, the details in web addresses and anything about your body, plan or diet left out. To measure how often the app crashes, Sentry also receives a short record of each app session: when it started, how long it lasted and whether it crashed. These session records, and the reports Sentry's own iOS component makes itself (crashes in the app's native code, or the app not responding), carry a random identifier Sentry creates for this installation; those reports also carry a one-way code computed from the identifier iOS gives apps from the same developer, the device model and the app. Never your app ID, screenshots or screen recordings. Crash reports and session records are sent whether or not usage analytics are on. Sentry is set not to store IP addresses.
RailwayHosts our server in the United StatesThe requests described in section 3
SupabaseHosts our database in the United StatesReports and menu requests (section 5) and restaurant data
OpenAIHelps read restaurants' own published online menus so we can estimate their nutritionText from restaurants' websites only — never information about you

We may also disclose information if the law requires it, to protect the rights, property or safety of our users or others, or as part of a merger, acquisition or sale of our business, in which case this policy continues to apply to it.

7. Other apps and websites

The app can open other services: DoorDash and Uber Eats (a search for the restaurant's name), a restaurant's own website, and Apple Maps or Google Maps (directions to the restaurant). We pass only the restaurant's name, website or location — nothing about you. Once you leave the app, the other service's privacy policy applies. These are plain links: we don't receive commissions or tracking data from them. Our own Privacy Policy, Terms of Use and Support pages open in your browser too, and the app passes nothing about you to them.

8. What we don't do

9. How long we keep information

InformationWhereHow long
Plan answers, saved meals, settings and app IDYour phoneUntil you change them, delete the app's data (your Usage analytics choice stays) or delete the app
Downloaded restaurant dataYour phone (temporary files)Until your phone clears them or you delete the app
Location, search words and map areasServer memory; automatic NYC demand also stores nearby restaurant IDsRestaurant IDs reveal coarse areas within one UTC day; demand identifiers rotate daily and prior-day rows purge at startup/hourly. Raw coordinates and search words are not stored by the app server; our hosting provider's request logs may keep them for a limited time (below)
Fair-use counters (network address, app ID)Memory; NYC daily demand stores rotating pseudonymsIn-memory counters reset daily/restart. Durable NYC quota rows purge after their UTC day, at startup/hourly.
Request logs kept by our hosting providerRailwayFor the limited time Railway's log retention for our service keeps them, then deleted by Railway
Reports and menu requestsOur databaseAs long as we need them to correct our data and decide which menus to add; deleted sooner if you ask (section 10)
Usage analyticsMixpanelUntil Mixpanel deletes them under our project's data-retention setting
Crash reports and app-session recordsSentryUntil Sentry deletes them under our plan's data-retention period
Subscription records and subscription-screen activityApple, SuperwallAs long as needed to provide your subscription and as the law requires
Emails you send to supportOur email providerAs long as we need them to answer you and keep a record of the request

10. Your choices and rights

If you're in the EU, EEA or UK

Who is responsible. Spill the Tea LLC is the controller of the personal information described in this policy. You can reach us at contact@chompfit.com or at the address in section 15.

Why we use your information. Under the EU and UK General Data Protection Regulation (GDPR), we rely on these legal bases:

What we doLegal basis
Showing restaurants, menus and search results for the area you're viewing, and running the app's features (sections 3 and 4)Performing our agreement with you (the Terms of Use)
Selling and managing your subscription, with Apple and Superwall: purchases, Restore Purchases and checking whether it is active (section 6)Performing our agreement with you
Storing the reports and menu requests you send, and finding actual menus for nearby NYC restaurants while you use the app (section 5)Our legitimate interest in keeping the app's restaurant and menu data accurate and adding the menus people want
Preventing abuse and keeping the service secure: fair-use limits, and our hosting provider's request logs (sections 3 and 9)Our legitimate interest in protecting the app and its users
Crash reports and app-session records (Sentry, section 6)Our legitimate interest in finding and fixing crashes
Usage analytics (Mixpanel, section 6). They are on unless you turn them offOur legitimate interest in understanding how the app is used so we can improve it. You can object at any time by turning off Usage analytics (above)
Keeping records and answering lawful requests, where the law requires itComplying with a legal obligation

Your height, weight, birthday, goal and other plan answers stay on your phone and are never sent to us (sections 1 and 2), so we don't process that health information on our systems.

Your rights. You have the right to access the personal information we hold about you, to have it corrected or deleted, to restrict how we use it, to receive it in a portable format, and to object to our use of it where we rely on our legitimate interests. Where we rely on your consent, you can withdraw it at any time; that doesn't affect what we did before. To use these rights, email us as described under "Information we hold" above, with the Install ID shown at the bottom of You. We'll respond within one month, or within the longer period the law allows. You also have the right to complain to the data protection authority where you live or work, or where you believe a problem happened — in the UK, the Information Commissioner's Office (ICO).

International transfers. We are based in the United States, and our server, database, usage analytics and crash reports are processed there (section 13). When information about people in the EU, EEA or UK goes to the U.S. or another country without an adequacy decision, we rely on appropriate safeguards, such as the European Commission's Standard Contractual Clauses and the UK's equivalent, in our data processing terms with our service providers.

How long we keep it. As described in section 9.

11. Children

Chomp is not directed at children under 13, and we don't knowingly collect personal information from them. If you believe a child under 13 has given us personal information (for example, in a report), contact us at contact@chompfit.com and we will delete it.

12. Security

The app talks to our server over encrypted connections (HTTPS). Our server refuses requests that don't carry the app's key, our database stores app IDs only as salted hashes and isn't exposed through any public interface, and the account our server uses can add reports but can't read them back. We keep as little information as we can. No system is perfectly secure, but we work to protect what we hold.

13. Where information is processed

Our server and database are in the United States, and so are our usage analytics (Mixpanel) and crash reports (Sentry). Our service providers may process information in other countries under their own safeguards. For people in the EU, EEA or UK, see "International transfers" in section 10.

14. Changes to this policy

If we change this policy, we'll update the date at the top. If a change is significant, we'll tell you in the app before it takes effect.

15. Contact us

Spill the Tea LLC, c/o Registered Agents Inc, 30 N. Gould St. Suite R, Sheridan, WY 82801, United States · contact@chompfit.com