Privacy Policy

Effective November 14, 2026 · Version 2026-11-14-draft

Who we are

NutritionDictionary (nutritiondictionary.com) is run by [OWNER LEGAL NAME] ("we", "us"). We decide how your personal data is used, which makes us its "controller" under the GDPR. Postal address: [OWNER POSTAL ADDRESS, IF REQUIRED]. Email: privacy@nutritiondictionary.com.

Data that could say something about your health, such as your diet goals and saved plans, has its own policy too: our Consumer Health Data Privacy Policy.

What we collect

If you don't have an account

• What you type or upload to use a feature. Food searches, the foods and goals you send to the planner, and recipe text or photos you ask us to read. Our server uses them to answer that request and doesn't save them.
• What stays in your browser. Your planner, last plan, recent recipes and recent searches are kept in your browser's storage, not on our servers. See Cookies and browser storage.
• Technical data. Like any website, our hosting receives your IP address and the pages and files your browser asks for. We use it to deliver the site and to stop abuse. Our application logs don't record IP addresses or email addresses. The recipe reader counts requests per IP address in server memory, for up to 24 hours, to stop one visitor using it all up. Amazon CloudFront's firewall can also limit requests per IP address.

Without an account we set no cookies, unless you start signing in.

If you have an account

• Your email address, which is how you sign in. There are no passwords.
• A display name, if you add one.
• If you sign in with Google: the name, email address, profile picture link and Google account ID that Google sends us, and the sign-in tokens Google issues. We don't get your Google password or contacts.
• Your history, which is recorded only while you're signed in:
  • foods you open (the food, its calories per typical serving and what it's rich in);
  • recipes you analyze (the title, ingredients and nutrition per serving);
  • plans you make (the foods, amounts, limits and nutrition goals, any recipes in them, and a summary).
  We keep up to 500 of each and remove the oldest after that. What you did before signing in is added only if you press Save to my account.
• Your agreements: which versions of our Terms and policies you agreed to, when, and that you confirmed your age. We don't record your IP address or device with them.
• Sign-in records: a session token and when it expires, and a one-time sign-in link stored only as a hash. Sessions don't record your IP address or device.
• Abuse counters: short-lived counts of requests, mostly stored under a scrambled (keyed hash) form of your IP address, email address or account ID. One exception: the sign-in system's own counters use your IP address as it is, for up to 5 minutes.

If you subscribe to Plus

Payments are handled by Stripe on its own pages. You give your card details to Stripe, not to us, and we never see or store your card number. Stripe tells us your customer ID, which plan you have, whether it's active or in a trial, and when it renews or ends. Stripe keeps payment records as financial and tax law requires.

What we don't collect

We don't ask for your weight, height, age, sex, pregnancy or medical conditions. We don't use advertising, analytics or social-media trackers, and we don't collect your precise location. Photos are resized in your browser before upload, and the server removes the metadata from JPEG photos (which can include the GPS location) before an AI reads them.

Why we use it

• To run the features you ask for: food lookup, contaminant meters, the planner and the recipe reader.
• To keep your account: signing you in, and showing your foods, recipes and plans on any device.
• To run Plus, if you subscribe: checking your plan and limits, and letting you manage it.
• To send the emails you ask for, such as sign-in links. We don't send marketing email.
• To keep the site secure and working: rate limits, error logs and preventing abuse.
• To keep a record of what you agreed to, and to meet legal obligations.

We don't use your data for advertising, we don't sell it, and we don't use it to train AI models.

Recipe photos, text and AI

When you upload a recipe photo, or paste a recipe our built-in reader isn't sure about, we send it to Amazon Bedrock, an AWS service, to read the ingredients. Bedrock runs Anthropic's Claude models, and Amazon Nova when Claude isn't available. AI reads can be wrong, so the page asks you to check every ingredient.

• We don't save your photo. It's held in memory while it's read and then discarded. Under our retention rules, an uploaded photo is never kept longer than 1 day.
• It isn't used for training. The Amazon Bedrock FAQ says your content "is not used to improve the base models and is not shared with any model providers", and that AWS and the third-party model providers "will not use any inputs to or outputs from Amazon Bedrock to train" their models. AWS's Bedrock data protection page adds that model providers "don't have access to Amazon Bedrock logs or to customer prompts and completions".
• Bedrock's model-invocation logging is off, so Bedrock doesn't keep a copy of the prompt or photo for us.
• Our logs record only the model used, the time taken, the token count and the cost, never the recipe or the photo.
• If you're signed in, the analyzed recipe (title, ingredients, nutrition) is saved to your history so you can reopen it. The photo isn't.

Who processes it

These companies process data for us, under their own privacy terms. We don't share your data with anyone else for their own use.

We don't use Cloudflare or any other third-party script, font service or analytics. The site's font is served from our own hosting. Privacy terms: AWS, Google, Stripe.

We may disclose data if the law requires it, for example in response to a valid court order, and we'll tell you when the law allows.

How long we keep it

Backups. Our database keeps continuous backups (DynamoDB point-in-time recovery) for 35 days, so we can recover from mistakes. When you delete your account or an item, it's removed from the live database straight away, but copies stay in those backups until they age out, within 35 days. We don't restore deleted data from backups except to recover from a failure, and if we ever do, we delete your data again.

Short-lived records such as sessions and counters expire automatically. The database removes expired records in the background, usually within a few days, and they can't be used once expired.

Your rights

Wherever you live, you can:

• See and export your data: on your account page, press Export my data to download everything we hold about you, including your agreements, as a file.
• Delete it: remove single history items on your history page, or press Delete my account on your account page to delete everything. Backups age out within 35 days, as explained above.
• Correct it: change your display name on your account page. To change your email address, email us.
• Withdraw consent: deleting your account withdraws it and removes the data. You can also email us.
• Clear this browser: signing out clears the planner, recipes and searches stored in this browser. Your browser's settings can clear it too.

Or email privacy@nutritiondictionary.com from the address on your account. We'll answer within one month, sooner if your local law requires it, and we won't treat you differently for using your rights. If we can't do what you ask, we'll explain why, and you can appeal by replying to that email with "Appeal"; we'll answer the appeal within the time your law allows. You can send a request through someone you authorize; we may ask them for proof.

EU and UK (GDPR)

The site is available worldwide, so if you're in the European Economic Area or the UK, the GDPR or the UK GDPR gives you the rights to access, correct, delete, restrict and object to the use of your data, to receive it in a portable format, and to withdraw consent at any time without affecting what happened before. Here is the legal basis for each use:

You can complain to your local data protection authority (in the EU, listed by the European Data Protection Board; in the UK, the ICO), though we'd like the chance to help first. Our representative in the EU and UK: [EU AND UK REPRESENTATIVE, IF REQUIRED].

California (CCPA/CPRA)

If you live in California, the California Consumer Privacy Act, as amended by the CPRA, gives you the right to know what we collect and why, to delete it, to correct it, to opt out of its sale or sharing, to limit the use of sensitive personal information, and not to be discriminated against for using these rights. We give these rights to everyone, whether or not the law applies to us.

• What we collect (the last 12 months): identifiers (email, name, account ID, IP address); sensitive personal information (diet goals and history that could relate to health); internet activity on our site (the foods, recipes and plans you keep); and, for Plus, commercial information (your plan and its status).
• Sources: you, your browser, Google if you sign in with it, and Stripe if you subscribe.
• Purposes and disclosures: as described above. We disclose data only to the service providers listed in Who processes it.
• No sale or sharing. We don't sell personal information or share it for cross-context behavioral advertising, and we haven't in the last 12 months. We don't knowingly sell or share the data of anyone under 16.
• Sensitive personal information is used only to provide the features you ask for, never to infer things about you.
• Global Privacy Control: because we don't sell or share personal information, there's nothing for a GPC signal to opt you out of.

Other US states

Residents of states with consumer privacy laws, such as Virginia, Colorado, Connecticut, Utah, Texas, Oregon, Montana, Iowa, Delaware, New Hampshire, New Jersey, Nebraska, Tennessee, Minnesota, Maryland, Indiana, Kentucky and Rhode Island, have similar rights to access, correct, delete and port their data, to opt out of sale, targeted advertising and profiling, and to appeal a refusal. We don't sell data, run targeted advertising or profile people in ways that have legal or similar effects. Use the steps in Your rights. If we deny your appeal, you can contact your state attorney general.

Washington, Nevada and Connecticut have specific rules for health data. Our Consumer Health Data Privacy Policy covers them.

Cookies and browser storage

We use only first-party cookies that are needed for signing in. There are no advertising, analytics or third-party cookies, so there's nothing to opt out of.

The site also keeps these items in your browser's local storage. They never leave your device unless you use a feature that sends them, such as making a plan. Items marked "personal" are cleared when you sign out, delete your account, or someone else signs in on the same browser; the theme stays, because it belongs to the device.

Children

NutritionDictionary isn't for children. You must be 13 or older to create an account, and we ask you to confirm it. We don't knowingly collect personal data from children under 13. If you think a child has given us their data, email privacy@nutritiondictionary.com and we'll delete it.

International transfers

Our servers are in the United States (AWS us-east-1, in Virginia). Bedrock may process an AI read in another US region. If you use the site from outside the US, your data is transferred to the US, where privacy laws may differ from yours. For transfers from the EEA, UK and Switzerland we rely on [TRANSFER MECHANISM: e.g. the EU-U.S. Data Privacy Framework certifications of our providers, or Standard Contractual Clauses].

Security

• The site uses HTTPS, and signing in works only over HTTPS.
• There are no passwords to steal. Sign-in links are random, work once, expire after 15 minutes and are stored only as a hash.
• The session cookie can't be read by scripts and is sent only over HTTPS on the live site. Every change to your account must come from our own pages, which blocks forged requests from other sites.
• DynamoDB, where accounts live, encrypts all data at rest by default (AWS documentation).
• Our logs identify people only by a scrambled code, never by email or IP address.
• Every account request is checked against the signed-in account, so no one can read another person's data by changing a link.

No system is perfectly secure. If a breach affects your data, we'll tell you and the authorities as the law requires (for example, the FTC's Health Breach Notification Rule and state breach laws).

Changes to this policy

When we change this policy we'll update the version and date at the top. If you have an account, we'll ask you to review and agree to a changed version the next time you sign in. We won't use data already collected in a materially different way without your consent.

Contact

Questions or requests: privacy@nutritiondictionary.com. Postal: [OWNER LEGAL NAME], [OWNER POSTAL ADDRESS, IF REQUIRED].

See also: Consumer Health Data Privacy Policy · Terms of Use. Questions: privacy@nutritiondictionary.com.