Draft. Pending review. Not final.

Privacy policy

Effective 5 October 2026. This draft describes what AI Fitcopilot does today. It is not a finished policy.

What we collect

We collect the email address you use to sign up. Supabase Auth stores a hash of your password. The app does not store the password itself.

If you save a nutrition profile, we store sex, age, height, weight, training days, goal, diet, and whether supplements are on. We also store kidney disease, which is the only medical condition the app records. You can add a clothing waist, a body-fat percentage you state, chosen calories and protein, and a meal pattern: meals per day, an eating window, usual training time, and whether you want pre-sleep protein.

We store what you type and save: chat messages, recipes and their versions, line choices, meals, day templates, and day logs. The server also stores meal reviews, balance proposals, servings estimates, provisional nutrition estimates, and a row each time a model call is reserved. A balance proposal stops being usable after about an hour. The row stays until you delete the account.

If you add your own photo of a recipe or meal, your browser shrinks it before it is sent, and we store that smaller copy without its location or camera details. Only you can open it, unless you publish that recipe. Publishing shows the recipe and its photo to anyone, including search engines. Making it private again removes that public page. AI photos are different: each is a generic picture of a dish, made from its name and ingredients, and the same picture is reused for everyone who saves that dish. It contains nothing from your account. The app does not send your photos to an AI model. Deleting the recipe, the meal, or your account deletes your own photo. A shared AI picture stays in the library.

Some ingredient lines can be saved in a shared nutrition cache. If you delete your account, your name is removed from that cache. The cached food stays so other people can still use it.

Where it goes

Supabase holds the database and your account. Vercel runs the website, so your requests are handled there.

When a feature calls a model, the request goes through the AI Gateway to the configured model. Chat sends the conversation. Calculate, Balance, meal review, the servings estimate, and the provisional estimate send the recipe, meal, or ingredient text that step needs. An AI photo sends only the recipe or meal name, its description, and the names of what is in it, to an image model. Profile facts are used to compute targets. We do not paste those prompts into this page.

If something fails in production, Sentry can receive an event. That happens only in production, and only when error monitoring is turned on. The event keeps a user id, an area, a code, a route name, and an error class. Emails, chat, prompts, profiles, and meal text are removed before the event is sent. Local development and preview deployments send nothing.

We do not sell it

We do not sell personal information. The app has no advertising and no separate analytics product.

How long we keep it

There is no general expiry. Your account, profile, chat, recipes, meals, days, and the related rows stay until you delete the account.

The site uses the sign-in cookies Supabase sets. There are no marketing cookies.

How to delete it

Sign in, open Account from the sidebar, and use Delete account. Enter your current password and type delete. That removes the auth account and the rows that belong to you. Shared cache foods stay, without your account id. So does our record of what your past AI requests cost: the feature, the model, the number of tokens or images, and the price, with nothing you wrote and no account id.