Privacy Policy

Last updated: August 2026

In short

The only information we require is your email address, which comes from signing in. Everything else — health conditions, dietary preferences, family details — is optional and stored only if you choose to enter it. Questions you ask are sent to the AI providers listed in section 5 so they can generate an answer. We do not sell your data, share it with data brokers, or use it for advertising.

1. Information we collect

Required

Email address. Provided when you sign in with Google, an email link, or an email and password. It identifies your account. Authentication is handled by Firebase (Google) — we never receive or store your password.
Display name and profile picture, only if your sign-in provider supplies them.

Optional — collected only if you enter it

Profile and personalisation details: date of birth or age, gender, height, weight, location, dietary preferences, health conditions, health goals, and family members you add (including children's ages and any dietary preferences or health conditions you record for them).
Source preferences: saved search filters, trust-score overrides, and sources you have chosen to hide.

AllNutrition works without any of these. Leaving them blank only makes answers less tailored to you. You can view, change, or clear them at any time in Settings.

Created as you use the service

Questions and answers: the text of questions you ask, a summary of the answer, and which sources were cited.
Saved sessions: Ask and Panorama sessions you create in the web app, and any pages you explicitly choose to share.
API keys and connected apps: the name you give them, creation and last-used dates, and request counts.
Feedback you submit on an answer.

We do not collect payment information — the service is free. We do not use advertising trackers.

2. How we use it

To answer your questions: find relevant research and generate a cited answer.
To personalise answers, where you have supplied optional details. Some of those details filter and rank which sources are used; some (such as the ages of children you are asking about) are included in the prompt sent to our AI provider.
To run your account: authentication, your daily request allowance, API keys, and connected apps.
To improve quality — ranking, trust scoring, and evaluation — in aggregate.
To send transactional email, and the newsletter if you opted in.
To keep the service secure and prevent abuse.

We do not sell your personal information, share it with data brokers, or use it to target advertising.

3. Using AllNutrition inside ChatGPT, Claude, or another AI assistant

You can connect AllNutrition to an AI assistant that supports MCP connectors. Connecting uses OAuth: you sign in on our site and approve the connection, and the assistant receives an access token. The assistant never sees your password.

What the assistant sends us

Only the question or search query, plus optional search settings (a published_after date, and a result count). Nothing else is transmitted from your conversation.

What we return to the assistant — the complete list

ask_nutrition returns: question, answer, evidence_strength, consensus_level, last_updated, deep_research, sources[]
search_references returns: query, count, results[]
Each source or result contains: id, title, url, publisher, publisher_short_name, evidence_level, trust_score, published_at, passage

These fields hold bibliographic and research data only. No field returned to the assistant contains personal data — no name, email address, profile details, account identifier, session identifier, or link to your account. Responses are filtered to exactly the list above before they leave our servers, so nothing beyond it can be returned. The one exception is your own input: if you type personal details into a question, they appear in the echoed question field and may be referenced in the answer.

What a connected assistant cannot do

It cannot read your AllNutrition profile, health conditions, or saved history. Answers requested through a connector are not personalised.
It cannot create public shareable pages, and it cannot read your Ask history — saving a question there (see below) is one-way from the assistant's side.
It cannot change your account, keys, or settings.

What we store from connector use

Questions you ask through a connector are saved to your own private Ask history by default — the question and its answer — so you can revisit them in the app, badged as an API/MCP session. This history is visible only to your account; we never share it with anyone, and connected assistants cannot read it back. You can turn saving off at any time under Settings → API keys (or per request with save_session: false).

Separately, we store the question text, a summary of the answer, and the cited source identifiers, linked to your account — this is what your daily allowance is counted against. Access and refresh tokens for the connection are stored only as irreversible hashes.

Approving a connection grants the assistant permission to ask nutrition questions as you and to use your daily allowance — nothing more. You can disconnect at any time under Settings → Connected apps, which immediately revokes its tokens.

4. Sharing with the AI providers that generate answers

Answering a question requires sending its text to a large-language-model provider (see section 5). Where you use a personalised surface and have supplied optional profile details, some of those details may be included in that prompt. These providers process the data to return an answer to us; their handling is also governed by their own privacy terms. If you would rather not have particular information leave our systems, do not include it in a question and leave the optional profile fields blank.

5. Service providers we share data with

Provider	What it processes	Purpose
Google Firebase Authentication	Email address, sign-in credentials	Signs you in and verifies your email. We never see or store your password.
Google (Gemini API)	Your question text; profile details only when you have provided them and are using a personalised surface	Generates the written answer and computes search embeddings.
OpenRouter	Your question text	Fallback answer generation when the primary model is unavailable.
Neon (PostgreSQL, US region)	All stored account data	Our primary database.
Google Cloud (Cloud Run, Cloud Storage — US)	Requests in transit; source documents	Application hosting and storage of the research library.
Google BigQuery	Account-creation events	Aggregate product analytics.
Resend	Email address	Transactional email and, if you opt in, the newsletter.
Deepgram	Audio you record	Voice input — web app only, and only while you use the microphone.

These providers act as our processors. We may also disclose information where legally required, or to protect the rights and safety of our users. If AllNutrition is ever involved in a merger or acquisition, we will give notice before your information becomes subject to a different policy. We do not sell personal information or share it with advertisers or data brokers.

6. How long we keep it

Account and profile: until you delete your account.
Ask and Panorama sessions: until you delete them individually, or until you delete your account.
API keys and connected apps: until you revoke them. Revoked entries are retained so past usage stays visible to you, and are removed with your account.
OAuth tokens: access tokens expire after 1 hour, refresh tokens after 90 days. Disconnecting an app revokes both immediately.
Question logs: retained while your account exists. When you delete your account they are de-identified — permanently unlinked from you — and the remaining text is kept only to measure and improve answer quality.
Pages you chose to share publicly: remain public until you delete them, or ask us to remove them.

7. Your choices and rights

View, edit, or clear any optional profile detail in Settings.
Delete individual sessions, or hide API and connector sessions from your history.
Revoke API keys and disconnect apps in Settings.
Delete your account from Settings → Account management. This removes your profile, saved sessions, chats, API keys, and connections, and deletes your Firebase sign-in record; question logs are de-identified as described above.
Export your data — email us and we will provide it.
Depending on where you live (including the EEA, UK, and California) you may have rights to access, correct, delete, port, or object to the processing of your personal data, and to withdraw consent. Contact us and we will honour these. We do not sell personal information, so there is nothing to opt out of in that respect.

8. Security

Traffic is encrypted with TLS. API keys and OAuth tokens are stored only as SHA-256 digests, never in a readable form, so a database leak would not expose usable credentials. Passwords are held by Firebase and never reach our servers. No system is perfectly secure, but we work to protect your information and will notify you of a breach affecting your personal data as required by law.

9. Children

AllNutrition is intended for adults and is not directed at children under 13, and we do not knowingly collect their personal information. Adults may record details about family members, including children, to get more relevant answers; that information belongs to the adult's account and is deleted with it.

10. Where your data is processed

Our database and application servers are located in the United States. If you use AllNutrition from outside the US, your information is transferred to and processed there.

11. Medical disclaimer

AllNutrition provides educational information drawn from published research. It is not medical advice and does not replace a qualified clinician.

12. Changes to this policy

We will update the date at the top when this policy changes, and give prominent notice in the app of material changes before they take effect.

13. Contact

Questions, requests, or complaints: support@allnutrition.info.