DishBinder Consumer Health Data Privacy Policy

Effective date: 2026-11-04

This policy is for people in Washington State (under the My Health My Data Act), Nevada, Connecticut and any other US state where a similar law applies. DishBinder is intended for people in the United States who are 18 or older. It explains the consumer health data that DishBinder, made by Duskfield Studios LLC, collects, why, who receives it, and how to use your rights. Our Privacy Policy covers everything else.

1. The consumer health data we collect

• Your food log: what you eat and drink and when, its nutrition (including AI estimates), notes, meal type, a restaurant name if you add one, and any meal or leftover photo.
• Data from your phone’s health app (Apple Health or Health Connect), only if you connect it and allow it in the system prompt: weight, body fat, active and resting energy, exercise minutes, steps and water, and the day’s nutrition totals other apps recorded (calories, macronutrients, sugars, fiber, sodium, caffeine, water, vitamins and minerals). We never read the individual foods other apps logged, or which app logged them.
• Body measurements you enter in the targets calculator: age, sex, weight, height, activity level, goal and goal weight.
• Nutrition goals: your calorie, protein, carbohydrate, fat, fiber, water and other nutrient goals.
• Allergies and diets: the allergies, diet styles and dietary restrictions you enter.
• Settings about these features, such as which health numbers Home shows, whether exercise calories count, and the reminders and nudges you turn on.
• What we work out from it: calories and nutrients left today, trends, reports, and which nutrient you’re short on.

Chef chat questions and the photos and text you ask the AI to read can also contain health information if you put it there. We don’t store Chef chat on our servers.

2. Where it comes from

• From you, when you log food, enter goals, measurements, allergies or diets, or take a photo.
• From your phone’s health app, only after you connect it and allow it. On Android this can run in the background.
• From our own calculations and from AI estimates of the food you log.

We don’t buy health data or get it from data brokers.

3. Why we collect and use it

Only to provide what you use DishBinder for:

• to count your calories and nutrients and show what’s left today;
• to plan meals and suggest recipes that fit your goals and avoid what you’ve told it to avoid;
• to show trends and reports;
• to send the reminders and nudges you turn on;
• to run the AI features you use (section 4);
• to write the nutrition and water you log back to your phone’s health app, if you allow it.

We collect it only with your consent: a separate checkbox, not part of the Terms. We never sell consumer health data, and we never use it for advertising.

4. Who receives it

We share consumer health data only with these service providers, who process it for us and only for the purpose shown, and with nobody else unless the law requires it. We have no affiliates that receive it.

• Groq, Inc. (Chef chat) — your Chef chat conversation, with your dietary restrictions and disliked ingredients. DeepInfra, Inc. receives the same if Groq is unavailable. Neither trains on our data; Groq keeps requests only in reliability and abuse logs, for up to 30 days, and DeepInfra holds them in memory only. Groq · DeepInfra.
• Google LLC (Gemini, every other AI feature) — the food photos, meal text and receipts you ask it to read, and the allergies, diets, dislikes, calorie and nutrient goals, what’s left today and pantry items used to plan meals and suggest recipes. If Gemini is unavailable, the same request goes to DeepInfra (and, for text only, Groq). We use Google’s paid API, so what we send isn’t used to train Google’s models or reviewed by people. Google.
• USDA FoodData Central, Open Food Facts and FatSecret — the names and barcodes of foods being looked up, never your identity.
• Expo (650 Industries), Apple and Google — the text of the push notifications you turn on. By default they show no calorie or nutrient numbers; they do only if you turn on “Show numbers in notifications” in the app.
• Railway (our servers and database, in the United States) and Cloudflare (storage of meal photos, served only through short-lived signed links).
• Sentry (error reports) — we configure it not to receive your food log, health data, chat text or request contents.

Your food log and health data are visible only to you, not to the other members of your household. A DishBinder widget you add to your home screen shows calories and macros left and your next meal.

5. How long we keep it

• While your account is open and your consent stands.
• A food-log entry and its photos go as soon as you delete the entry.
• A meal photo you took for an estimate but didn’t log: 2 days.
• Withdraw consent and we delete it (section 6). Delete your account and it goes with it within 7 days.
• An account nobody uses for two years is deleted, after one email 30 days before (signing in keeps it), and its health data with it.
• Deleted data can remain in our host’s database backups for up to 90 days, until they expire.

6. Your rights, and how to use them

• Know and access it: Settings → Your data → Export my data gives you a file of everything, including your health data. This page lists every company that receives it.
• Withdraw consent and delete it: Settings → Your data → Withdraw & delete. That deletes your food log and its photos, everything synced from your phone’s health app, your body measurements, goals, allergies and diets, and the settings above, right away. If you withdraw from an older version of the app (store app 1.0.5 or earlier, or a web page opened before 2026-11-04), which didn’t say it would delete anything, we delete the same data 30 days later unless you agree again first.
• Delete your account: Settings → Danger zone → Delete account, or these steps.
• Entries DishBinder wrote to your phone’s health app stay there until you delete them in that app.
• You won’t be treated differently for using these rights.

You can also email support@duskfieldstudios.com from your account’s address. We answer within 45 days (we may extend that once by 45 days when needed, and will tell you why). An authorised agent can ask for you; we confirm the request with the account’s email.

7. Appealing a decision

If we refuse a request, you can appeal: reply to our answer, or email support@duskfieldstudios.com with “Appeal” in the subject. Someone who didn’t make the first decision reviews it, and we tell you the result and why within 45 days. If you disagree with the result, you can contact the Washington State Attorney General (or your own state’s attorney general).

8. Contact

Duskfield Studios LLC, 2108 N St Ste N, Sacramento, CA 95816 · support@duskfieldstudios.com

9. Changes

If we change how we collect, use or share consumer health data, we update this page first and ask for your consent again in the app.