Consumer Health Data Privacy Policy
Last Updated: November 4, 2026
Effective September 8, 20261.Scope
This is the consumer health data privacy policy of Bodydex, operated by Daniel Bobunov, for the purposes of the Washington My Health My Data Act, Nevada SB 370, and the Connecticut Data Privacy Act. It applies to everyone who uses the Bodydex app. "Consumer health data" means personal information that is linked or reasonably linkable to you and that identifies your past, present, or future physical or mental health status. Our general Privacy Policy describes everything else about how the app handles your information; where this page refers to a numbered section, it means a section of that policy.
The free tools on our website, such as the Peptide Reconstitution Calculator, do not collect consumer health data: what you type into them stays in your browser unless you copy or share it yourself, and is not sent to us (Section 14.1).
2.Categories of consumer health data collected, and why
- Stored on your device for tracking: body measurements (weight, height, body measurements, progress photos), food and water intake, workouts, medication, supplement, and peptide records including recorded doses, schedules, adherence and injection sites, the lab results — the ones you enter yourself and the ones read from your own report that you chose to import, whether you photographed it or chose its PDF — with their dates, the lab, and the reference range printed on that report, and the notes you write. If you connect Apple Health or Google Health Connect, this also includes the values the app imports into those logs (a weigh-in, a drink) and, from a workout recorded by another app, a summary of it — when it was, how long, which muscles, an activity type and an energy figure where the platform supplies one — used for the muscle-recovery view rather than added to your workout history. Purpose: to provide the tracking features you use. Selected records and summaries from these categories are also processed through the online features described next.
- Read from a health platform on demand and not stored: the vitals readings listed in Privacy Policy Section 5.1 — resting heart rate, heart rate, heart rate variability, blood pressure, blood glucose, blood oxygen, respiratory rate, sleep, body fat and lean body mass. Each is requested for the dates a chart or a question covers and shown to you in the app; it is not written into your logs. Purpose: to chart a vital alongside the doses you recorded. Your daily steps and active energy are read the same way, when a screen shows them, and are not written into your logs; the home-screen widget keeps only today's two totals on your device, replaced each time it refreshes. Purpose: to show your activity.
- Received transiently by our server proxy and sent to an AI provider, only when you use the feature: food photos, voice clips, voice transcripts, and vocabulary hints derived from your tracked item names (food scanning and voice logging); and, for the Bodydex Assistant only with your explicit consent, the categories listed in Privacy Policy Section 6.2 — with every message, your current weight and recent readings, nutrition totals and averages, and active medication, supplement and peptide names with the doses you recorded; and, for some questions, dated nutrition and water history, dated weight measurements, protocol schedules, adherence and supply summaries including the next dose recorded in your schedule, dose history with injection sites, workouts, reminder settings, and logging streaks and badges; and, only if you tick the health-vitals option yourself, readings from Apple Health or Google Health Connect (the vitals listed above, and daily steps and active energy) for the dates your question is about; and, only if you tick the lab-results option yourself, the lab results you recorded with their dates, the lab, and the reference range from your own report — whether you entered them yourself or imported them from that report, as a photo or as a PDF — read for the question you asked and no other. Purpose: to produce the estimate or answer you asked for. We do not maintain a synchronized server copy of your tracking database, and none of this is added to a profile or health record of yours held by us; we retain the operational records described in the Privacy Policy. What our own server keeps in the course of running these features, and what the AI providers may retain under their own terms, are described in Privacy Policy Sections 6, 6.6 and 9 — read those for the periods, because this page states only what the Washington, Nevada and Connecticut health-data laws require it to.
- Received transiently by our server proxy and sent to an AI provider when you import a document: what you chose — one or more photos of a lab report or of a medication, supplement or peptide label, or the PDF your lab sent you — and the text read from it; for a report, the marker names, values, units and the reference range printed on it. Purpose: to transcribe what is printed so you do not have to type it. The app asks for your separate, explicit consent before your first import and shows a notice before every import; you can withdraw it at Profile › Legal & Data › Document import. The extractor is instructed never to return the identifiers a report or label carries — name, date of birth, address, record or prescription number, prescriber — and our server rebuilds its result from a fixed list of fields. We restrict returned fields and instruct the model to omit identifiers; these measures cannot guarantee removal. We store neither what you sent nor the transcription; what the AI provider may retain under its own terms is described in Privacy Policy Sections 6.6 and 6.7. Nothing is added to your records until you review it and save it yourself.
- Received when you submit feedback: anything you choose to type or screenshot (Privacy Policy Section 3.3), including any photos of a product label you attach to a report of incorrect food data; and a scan photo you choose to send with a thumbs-down rating (Privacy Policy Section 6.1). These report photos are retained with the report as those sections describe. If you granted notification permission, your push notification token is used to tell you when we reply. From app version 1.2.6 this includes a message sent from the sign-in screen's "Trouble signing in?" form, with the email address you type there; such a message is normally gone from our support system within 30 days (Privacy Policy Sections 3.3 and 9). Email you send to one of our addresses, with any attachments, is kept as Privacy Policy Sections 3.3 and 9 describe. Purpose: support.
- Install message to Meta (app versions before 1.2.6): app versions before 1.2.6 send one install message per installation through our server the first time the app is opened: that the app was installed, the time our server handled the message, the platform, the app's name and version, a random code made for that message and, on Android, the Google Play install referrer when it shows that the installation came from one of our Meta ads. Source: the app on your device and Google Play. Purpose: to measure whether our own ads work. Those versions ask no question about it. It is shared with Meta (below). It does not include health measurements, logged records or anything you entered, but it does tell Meta that you installed Bodydex. From app version 1.2.6 the app sends no install message (Privacy Policy Section 8.2).
- Ad measurement (from app version 1.2.6, only if you agree): if ad measurement is switched on for new installs and you agree on the "Ad measurement" screen during setup, tools from Meta, Tenjin and, on iPhone, Google Analytics send, during setup and briefly afterward, that the app was installed and a trial or plan started during setup with its price, with your advertising and device IDs, IP address and phone details. Source: the app on your device. Purpose: to measure whether our own ads work. It includes no health measurements, logged records or anything you entered, but it does tell those companies that you installed Bodydex and whether you started a trial or plan. We do not start these tools for people we detect are in Washington, Nevada or New Jersey, and once we detect it on a phone they stay off there. If you live in one of these states, please choose "Don't allow" (Privacy Policy Section 8.1).
Setup screen counts (from app version 1.2.6). During setup the app also adds to counts of how often each setup screen is reached. The counts carry no account or installation identifier; after the birthday question a request may include a one-use app pass. Our server keeps only running totals; the IP address of each request is used by Cloudflare to deliver it and apply a rate limit, and is not stored with the counts (Privacy Policy Section 3.2).
Genuine-app check (from app version 1.2.6). During setup, after the birthday question, the app contacts our server at attest.bodydex.app so that it can show it is a genuine copy of Bodydex. If that check is switched on, the app asks Apple (App Attest) or Google (Play Integrity) to confirm it, and our server hands the app a few one-use app passes; one can travel with a setup-counts request. On iPhone the check uses a key identifier that Apple creates for the installation; our server uses it and does not store it, and keeps a counter under a one-way code that changes every day, normally removed within about two days. The check carries no health measurements, logged records or account identifier (Privacy Policy Section 3.2).
If the App Store or Google Play reports that the account on a device belongs to someone under 13, the app switches that installation to local-only mode, which blocks new online-feature requests. A request to delete the records our server and our subscription processor hold under that account may still be sent, on Android the app asks Google to delete its push-notification registration, and a subscription session already started may continue until the app closes. Your tracking records stay on the device (Privacy Policy Section 12).
3.Sources
You (what you enter, photograph, say, or choose as a file), your device sensors and camera when you use them, Apple HealthKit / Google Health Connect when you grant access, the app itself for the install message of app versions before 1.2.6 and for ad measurement, and, on Android, Google Play (the install referrer that goes with them). Those are our sources. We do not obtain consumer health data from data brokers.
4.Categories shared, and with whom
These recipients receive the information described for each. Their purposes, and what each may do with it, differ: OpenAI (Bodydex Assistant — the Privacy Policy Section 6.2 categories; voice-log transcript text), under its API terms, which state that API content is not used to train its models by default; Google (food photos and nutrition-label and menu scans, scan corrections and recipe text, which may be sent to Google's Gemini API on its unpaid tier, under whose terms Google may use both what is sent and what the model returns to improve its products and human reviewers may read it); Cloudflare (voice clips, transcribed by Cloudflare Workers AI, which states that it does not use customer content to train models or improve its services without explicit consent; Cloudflare also operates our proxy, stores a scan photo you choose to send with a thumbs-down rating, and receives email you send to our addresses, holding a copy until our internal support system collects it, normally within minutes, with a copy left there scheduled for deletion after 14 days); Google also hosts our mailbox (Gmail), where that email is delivered (Privacy Policy Section 3.3); Groq (voice clips, only if Cloudflare's transcription fails; Groq states that by default it does not retain them but may log them for up to 30 days to troubleshoot errors or investigate abuse). Data read from Apple HealthKit or Google Health Connect is not sent to any of these providers for model improvement: it can reach an AI provider only through the Bodydex Assistant (OpenAI). Google alone reads a document you choose to import — one or more photos of a lab report or of a product label, or a lab report's PDF — on its paid tier; the document reaches it through our proxy, and Google's terms govern what it may retain (Privacy Policy Section 6.6); and Supabase and the Telegram Bot API (feedback you submit, including attached screenshots; label photos stay with Supabase and our internal support tooling and are not sent to Telegram; from app version 1.2.6, a message from the "Trouble signing in?" form is stored with Supabase and is not sent to Telegram either); and Expo (650 Industries, Inc.), which relays our support-reply notification — who replied, the opening of the reply and a ticket reference — to Apple or Google, only if you chose to be notified of a reply and granted notification permission. Meta receives the install message of app versions before 1.2.6 described in Section 2: one message per installation, which may be retried with the same code, to measure whether our own ads work; those versions ask no question about it, and what Meta does with it is governed by Meta's own terms (Privacy Policy Section 8.2). From app version 1.2.6, if you agree to ad measurement (Section 2), Tenjin (our measurement processor), Meta, Google (iPhone only), TikTok and AppLovin receive the setup events described there (Privacy Policy Section 8.1). We do not give your health logs to advertising or measurement companies. We do not sell the health information in your logs and do not share it with data brokers. Ad measurement does not start for people we detect are in Washington, Nevada or New Jersey, and stays off for good on a phone once we detect it there. We do not use geofencing. Apple HealthKit and Google Health Connect are separate from the AI services described above; health-platform access is controlled through the permissions on your own device.
5.Consent
The app asks for your affirmative, separate consent before the Bodydex Assistant sends any health data, and before the first time it sends a lab report — photographed or as its PDF — or a photo of a product label to be read — a separate consent from the Assistant's, recorded against the version of the disclosure you read, repeated as a notice before every import, and withdrawable at Profile › Legal & Data › Document import. It asks for your device permission before reading a health platform. Scanning and voice features send the image, audio, or text used for the request, together with the feature-specific context and request metadata described in Privacy Policy Sections 6.1 and 6.3. From app version 1.2.6, ad measurement (Section 2) starts only after you agree on the "Ad measurement" screen during setup (on iPhone, also by allowing tracking when your iPhone asks); you can stop it as Privacy Policy Section 8.1 describes. The app asks no question before it sends the install message of app versions before 1.2.6 described in Sections 2 and 4, the setup screen counts or the genuine-app check; this page and the Privacy Policy are where we tell you about them. We will not collect or share categories of consumer health data, or use it for purposes, that are not described here without first asking for your consent.
6.Your rights and how to exercise them
You may confirm whether we are collecting, sharing, or selling your consumer health data and access it, including a list of the third parties it has been shared with; withdraw consent; and have it deleted. Because almost all of it lives only on your device, you can access it in the app at any time, export it (Profile → Export Data), withdraw Assistant consent (Profile → Bodydex Assistant → Withdraw consent; Privacy Policy Section 11.7), revoke health-platform access in your device's Settings, and delete it (Profile → Delete Account, confirmed as Delete All Data), which erases what is on your device. From app version 1.2.6, if you are signed in, it also asks our servers to delete what you sent us under your account, and any message sent from the "Trouble signing in?" form by this installation of the App; trial, usage and subscription records stay (Privacy Policy Section 11.2). If ad measurement ran on your phone, it also queues a deletion request for Tenjin, sent when possible. It waits on this phone, and the app retries when a retry is due while it is installed and open. Our server sends only a limited number of these requests, so one can wait for a later month. A request still not sent after 60 days ends unsent (from version 1.2.7, 180 days if our server held it back because of one of its limits), and the app then shows how to contact us. For ad measurement our servers keep nothing that can be linked to you apart from the pseudonymised deletion-request records and the monthly counts of deletion requests per internet address and per block of addresses, kept under a keyed hash to stop abuse until they expire one day after the end of that month (Privacy Policy Section 8.1). You can also ask us as below, or ask the other companies directly (Privacy Policy Section 8.1). Sending the install message to Meta cannot be undone. To ask what we hold about it or to request deletion, write to us as below: we will delete what we can identify in our systems, handle requests about recipients as the law that applies to you requires, and tell you what we need to find the record and any limits on what we can do (Privacy Policy Section 11.9). Our record of an install message is stored against a random code rather than your name or account.
6.1 How to submit a request
For the limited server-side records, or to obtain the list of recipients, email (or ) with "health data request" in the subject, and tell us which state you are a resident of and what you are asking for. We may ask you for additional information in order to authenticate the request — we will not ask you to create an account to make one, and if we cannot authenticate a request using commercially reasonable efforts we will tell you so rather than acting on it. Responding is free at least twice a year; we may charge a reasonable fee, or decline, only for a request that is manifestly unfounded, excessive or repetitive, and the burden of showing that is ours. We will not discriminate against you for exercising a right.
Initial deadlines. We respond without undue delay and in any case within 45 days of the request (Nevada: of authenticating it). We may extend that once by 45 further days where the complexity or number of your requests makes it reasonably necessary, and we will tell you of the extension and the reason for it inside the first 45 days. An authenticated Nevada deletion request is completed within 30 days, and we notify the processors and third parties named in Section 4 of deletion requests. If we decline to act on a request, we will tell you within the same 45 days, give our reasons, and explain how to appeal.
6.2 How to appeal, and what happens if we deny it
If we refuse to act on a request, you may appeal. Send your appeal to the same address — (or ) — with "health data appeal" in the subject, within a reasonable period after you receive our decision. You do not need to fill in any form, use any other channel, or provide anything beyond what the original request needed: the appeal route is deliberately the same route as the request. We will inform you in writing of any action taken or not taken in response to the appeal, including a written explanation of the reasons for the decision, within the period your law sets:
- Washington — within 45 days of receiving the appeal (RCW 19.373.040).
- Nevada — within 45 days of receiving the appeal (NRS 603A.520).
- Connecticut — within 60 days of receiving the appeal (Conn. Gen. Stat. § 42-518).
These are appeal deadlines. They are separate from, and run after, the 45-day deadline for the original request above.
If we deny your appeal, you may submit a complaint to your state Attorney General. We will repeat these routes in the denial itself, and they are:
- Washington — Office of the Attorney General complaint form: atg.wa.gov/file-complaint.
- Nevada — Office of the Attorney General complaint form: ag.nv.gov/Complaints/File_Complaint.
- Connecticut — Office of the Attorney General, data privacy complaints: portal.ct.gov/ag — Connecticut Data Privacy Act (general consumer complaints: portal.ct.gov/ag/complaint/consumer-complaints).
If you are in the EEA or the UK, the equivalent routes and deadlines are in Privacy Policy Section 11.6, and you may also complain to your own supervisory authority.
6.3 Which of these laws applies to you
Washington (My Health My Data Act) and Nevada (SB 370) apply to us by reference to the consumer health data we handle, not to our size, so we apply them in full. Connecticut reaches us on two independent routes, and we claim no exemption on either. Since July 1, 2026, the Connecticut Data Privacy Act applies to any person that "control[s] or process[es] consumers' sensitive data" — a trigger that carries no volume threshold and sits beside, not behind, the 35,000-consumer one (Conn. Gen. Stat. § 42-516(2), as amended by P.A. 25-113, § 6). The Act defines sensitive data to include consumer health data and data revealing a physical or mental health condition, diagnosis, disability or treatment (§ 42-515). Bodydex offers products and services to Connecticut residents through the app stores and processes exactly that data, so we treat the whole of §§ 42-515 to 42-525 as applying to us — not only the health-data parts — and none of the entity exemptions in § 42-517(a) covers us. Separately and additionally, § 42-526(a)(2) applies the consumer-health-data provisions notwithstanding § 42-516 to any person who conducts business in Connecticut or targets products or services to its residents. For consumer health data, what follows is the rights, the 45-day response deadline and the 60-day appeal deadline set out above. The general Connecticut rights that are not about health data — correction, portability and the three opt-outs — are in Privacy Policy Section 11.8.