Consumer Health Data Privacy Policy
Interim version — in effect while review by a licensed Texas attorney completes. Prepared with AI assistance; updates will be posted here. Questions: legal@tidbix.com
Version: 0.3 (interim) · Effective date: July 19, 2026 · Tidbix LLC · legal@tidbix.com
This policy supplements our Privacy Policy for residents of Washington (My Health My Data Act, RCW 19.373) and Nevada (SB 370), and applies to "consumer health data" we collect.
This is an interim version, in effect while attorney review is completed. It was prepared with AI assistance; a revised version may replace it.
1. Consumer health data we collect
All of it is supplied by you, in two groups with different legal footing:
With your opt-in consent (the separate health-data toggle — Section 6):
As necessary to provide the service you request (no toggle — the planner's safety guardrails cannot work without them, and they are used only for that):
We do not collect biometric samples, raw test results or images, precise geolocation, or health data from any source other than you. We do not use geofencing anywhere in the Service.
2. Why we collect it (purposes)
Solely to provide the Service you asked for: planning your household's meals, building grocery lists, applying allergy/avoid guardrails, and showing progress you track. Processing steps are described in Privacy Policy §§4–6 (including the filtered AI-planning digest sent to Anthropic as our processor).
3. Sources
You (and household information you enter about family members, with the authority described in Terms §1.3).
4. Sharing; no selling
We do not sell consumer health data, do not use it to train artificial-intelligence models (and would not without your separate, explicit opt-in consent — no such program exists today), and will not share it with third parties for their own purposes. It is disclosed only to the processors that run the Service — Anthropic (AI planning, filtered digest only, and only while your health-data toggle is on for food lists), Vercel (hosting), and Supabase (database, once server accounts launch — nothing is stored there today) — each bound by contract to process it only on our instructions. The full list, and what each receives, is in Privacy Policy §7. Any future change would require your prior, separate opt-in authorization as WA/NV law requires — and none is planned.
5. Your rights
Washington and Nevada residents may: access their consumer health data (including the list of third parties it was disclosed to); withdraw consent (which stops new collection and stops food lists from being used in AI planning — Section 6); and delete it — either health data alone (Household → Privacy & your data → Delete health data) or everything (Delete everything). Exercise these in-app (export, consent toggle, deletion controls) or by emailing legal@tidbix.com. We respond within the statutory time, and you may appeal a refusal by replying to our response; if the appeal fails you may contact the Washington or Nevada Attorney General.
6. Consent mechanics
We ask for opt-in consent before collecting the consent-based categories in Section 1, separately from the Terms of Service (no bundled consent): a distinct, default-off health-data toggle during onboarding — its description names what is collected and that food lists are shared with our AI processor (Anthropic) to build plans — changeable any time under Household → Privacy & your data. Declining leaves the rest of the app usable without those features (food-list imports and edits, wellness check-ins, and weigh-in tracking are disabled, and food lists are not used in AI planning while off).
7. Changes and contact
Material changes require fresh consent where the law demands it. Contact: Tidbix LLC, Tarrant County, Texas (registered address available on request), legal@tidbix.com.