Skip to content
foodoseGet my numbers
Legal

Privacy policy

Last updated October 7, 2026

There are two Foodose products and they handle data very differently, so this policy is in two parts.

The website has no account and no login. When you ask for your plan, the calculator sends your answers to our server, which uses them for that one request and keeps nothing.

The iPhone app does have an account, because your logs have to reach your next phone. It stores what you record, in a row only you can read, and deletes all of it the moment you ask.

The long version follows, because "we take your privacy seriously" is not a policy.

1. Who we are

foodose is operated from India. If you want to reach a person about anything on this page, write to ceo@foodose.co and one will answer.

2. What the calculator does with your answers

The questions are answered on the page, and nothing is sent while you answer them. When you press the button that builds your plan, your weight, height, age, medication, dose, cycle, symptoms, food preferences and safety answers are sent to our server over an encrypted connection. The server works out your numbers and your three days of food, sends them back, and keeps nothing: your answers are not written to a database or a log, and there is no account to attach them to. On your device they are kept in this tab's session storage, so a refresh or the back button does not lose your place, and they are cleared when you close the tab.

This is not a promise about how carefully we guard your data. It is a statement that we do not keep it.

The answers the homepage card carries into the calculator travel after a # in the address, which your browser does not send to any server, and are removed from the address as soon as the calculator has read them.

3. The PDF

"Print or save as PDF" under your plan uses your browser's own print, which sends nothing to us.

There is also a PDF endpoint, /api/plan, which our agent tools and older links use. It builds a document on our server from answers carried in the address of the request. Our server uses them to build the document, returns it, and does not write them down. We keep no copy of your plan and no log tying a set of answers to a person. The address itself may appear in ordinary server request logs kept by our hosting provider for operational and security purposes, and those are retained for a short period and then discarded.

The two open endpoints, /api/glp1-target and /api/foods, and our MCP server for AI assistants are anonymous and take everything they need in the request. For /api/glp1-target and the MCP server we record which endpoint or tool was called, the medication and dose asked about, any search words, and the name the calling software gives itself, so we know how they are used. We never record the weight, height or age sent with a request.

4. If you give us your email

The only thing on this site that asks for personal information is the newsletter form. If you enter your address:

  • We store it, and nothing else about you, in a database run by Supabase.
  • We use it to send the weekly email and for nothing else.
  • Every email carries an unsubscribe link that works in one click.
  • Ask us to delete it and we will, within 30 days, and confirm when it is done.

We do not sell it, rent it, share it with advertisers, or use it to build a profile of you.

5. Analytics on the website

We measure how the site is used with our own analytics, kept in our own database (run by Supabase), alongside page counts from Vercel Analytics.

What is recorded about a visit:

  • the page and the time, the site that linked you here (its domain only), and any campaign tag in the link (utm_source, utm_medium, utm_campaign);
  • your approximate location (country, region and city, which our hosting provider works out from your IP address), your device type, operating system and version, browser and language;
  • how the page was used: active time on the page, how far you scrolled, the last section heading you reached, which links you followed, whether you copied text (its length only, never the text), printed, or opened a question, plus page speed and script errors;
  • in the calculator, which question you reached and whether you finished, never your answers. When a plan is built we record whether its food had to come from every region and how many days fell short of protein, and nothing about you;
  • in the recipe finder, the food words you searched and the filters you chose.

Your IP address is not stored. To count a visitor once a day without a cookie, we combine your IP address and browser details with a random value that changes every day and is then deleted, and keep only the result. It cannot be turned back into your IP address or linked to your visits on another day. Nothing is stored on your device for analytics: no cookies and no local storage. (The one exception is a setting we use on our own devices to stop counting ourselves.) Detailed records are deleted after 90 days; daily totals are kept.

Automated visitors, such as search engine and AI crawlers, link previews and scripts, are recorded with their IP address and user agent, so we can check they are who they claim to be.

We do not use Google Analytics, advertising pixels or any cross-site tracking on this website, and we do not sell or share this data.

6. Cookies

We set no cookies that identify you. There is no consent banner because there is nothing to consent to.

This part applies only if you install the app. Nothing here changes what happens on the website.

7. Your account

You sign in with Apple or Google. We receive a user identifier and, unless you choose to hide it, an email address. We never see your Apple or Google password.

The account exists so that your history survives a lost or replaced phone.

8. What the app stores

What you record, which may include:

  • Food, water, weight and the targets calculated for you.
  • Your dose, whether you took or skipped it, and the injection site.
  • Symptoms and their severity, how you are feeling, and any notes you write.
  • If you use the cycle features, period dates, flow and cycle symptoms.
  • Your profile: age, sex, height, weight, goal weight, activity, medication and dose.
  • Your messages to the coach, and its replies.
  • Whether your subscription is active.

This is health information. It is stored in Supabase (Postgres, hosted in the United States), in rows that only your signed-in account can read, and is also held on your device so the app works without a signal.

9. The coach

When you send a message to the coach, that message and a summary of your current context, such as your targets, your dose and what you have logged today, are sent to OpenAI to generate the reply. Those messages are not used to train models, ours or anyone else's. Do not type anything into the coach you would not want leaving your phone.

10. Apple Health

Only with your permission, and each permission is separate:

  • The app reads your step count, and your cycle if you record it in Apple Health.
  • The app writes the weight and the mood you log in Foodose back to Apple Health.

Refuse any of it and the app still works. Apple Health data is never sold, never used for advertising and never sent to an advertising network.

11. Analytics in the app

The app records product events, such as an app open or a completed onboarding step, so we can see what to fix. These go to our own database and, where it is enabled, to PostHog. Health values are never attached to them.

The app also includes Meta's SDK, used for one purpose: measuring which ads led to installs and subscriptions. It is configured with tracking switched off: no advertising identifier is collected, no App Tracking Transparency prompt appears, and the app does not follow you across other apps and websites.

12. Payment

Subscriptions are sold by Apple through the App Store. Apple takes the payment and tells the app whether your subscription is active. We never see your card, your billing address or your Apple ID.

13. Deleting what we hold

In the app, You, then Delete All My Data, removes your account and every row attached to it, on the server and on the phone. It cannot be undone.

Signing out is not deletion: it ends the session on that device and leaves your data where it is, ready for the next sign-in.

You can also write to ceo@foodose.co and ask us to do it for you.

14. What we never do, on either product

  • We do not sell your data.
  • We do not share it with advertisers or data brokers.
  • We do not train models on your coach messages or your logs.
  • We do not use health information to target advertising.

15. How long we keep it

  • Newsletter email: until you unsubscribe, which is one click in every email.
  • App account and logs: for as long as your account exists.
  • After you delete your account: removed from our active systems within 30 days, and from encrypted backups within 90 days.
  • Coach messages: stored with your account so you can read them back, and deleted on the same schedule.
  • Crash and performance data, product events: up to 180 days.

The website keeps nothing to delete: your calculator answers are used for the request that builds your plan and then discarded.

16. Security

Data in transit is encrypted with TLS. Data at rest is encrypted in our database. Sign-in uses standard tokens issued by Apple or Google; we never see or store your password.

No internet-connected system is perfectly secure and we will not pretend otherwise. We design on the assumption that any piece of data could leak, which is why we hold as little as we can, for as short as we can. If a breach ever affects your data we will tell you as soon as the law requires, and sooner if we can.

17. Your rights

Depending on where you live you may have the right to access, correct, export or delete what we hold, and to object to processing. On the website there is usually nothing to act on, because the only personal data we hold is a newsletter address you gave us on purpose. In the app, deletion is a button (You, then Delete All My Data), and the rest you can ask us for. Write to ceo@foodose.co and we will answer within 30 days.

Under the California Consumer Privacy Act, we do not sell or share personal information as those terms are defined.

18. Who else is involved

  • Vercel hosts foodose.co and provides the website analytics described above.
  • Supabase stores newsletter email addresses, and the app's accounts and logs.
  • Apple and Google provide sign-in for the app; Apple also handles subscriptions.
  • OpenAI generates the coach's replies.
  • PostHog receives app product events where enabled.
  • Meta receives install and subscription events from the app for ad measurement, without an advertising identifier.
  • Google Fonts files are served from our own domain rather than Google's, so your browser does not contact Google when you load a page here.

19. Children

Foodose is written for adults and is not directed at anyone under 18. We do not knowingly collect information from children.

20. International transfers

We operate from India and our providers are based primarily in the United States and the European Union, so your data may cross borders. We rely on standard contractual clauses and equivalent safeguards where required.

21. Changes

If this policy changes in a way that matters, we will update the date at the top and, if you are on the newsletter or using the app, tell you there.

22. Contact

ceo@foodose.co. A real person reads every email.