DYLD

Consumer Health Data Privacy Policy

DYLD — Get Dialed Last updated: August 18, 2026

This policy is for residents of Washington State and is published under the My Health My Data Act (RCW 19.373). Residents of Nevada (SB 370) and Connecticut have substantially the same rights described here, and we honor them the same way.

It is a separate document on purpose. The law requires consumer health data to be described on its own, not folded into a general privacy notice. Our full Privacy Policy covers everything else and does not replace this one.


The short version

Almost all of your health data never leaves your phone. Your training, your food, your journal, your check-ins and your record are stored in a database on your device. We cannot see them, we have no copy, and no one here can retrieve them.

Three things you choose to do send health data off your device, and only while you are doing them: asking the AI coach a question, scanning a meal photo, and speaking a food log. Each exists for the length of a single request and is not stored — not by us, and not by the provider that processes it.

We have never sold consumer health data and we never will. We do not use it for advertising, we do not share it with data brokers, and we operate no geofence of any kind.


1. What counts as consumer health data here

The law defines consumer health data broadly. In DYLD, these categories qualify:

CategoryWhat it is in the app
Bodily measurementsBodyweight, age band, personal records, lifts, sets, reps, strength history
Exercise and fitness activityWorkouts, routines, training plans, completed sessions, your W–L record
Nutrition and food consumptionFood logs, meals, calories, macros, protein targets, barcode scans, meal photos
Mental and behavioral healthMIND check-ins, the state you pick, journal entries and free-writes, reflections
Health-related goalsWhat you tell us you are trying to change about your body or your habits
Data that could be inferredAnything about your physical or mental health reasonably derivable from the above

Faith content (WORD) is not health data, but we treat your decision to turn it on with the same care and it never leaves your device either.


2. Where it comes from

We collect consumer health data from exactly one source: you, typed, spoken, photographed or tapped into the app.


3. What stays on your device, and is therefore never collected by us

The following is written to a database on your phone and is never transmitted to us:

Your date of birth and age never reach our servers. There is no age column in our database.

If you delete the app, this is gone. We keep no backup and cannot restore it.


4. What we actually collect, why, and for how long

a. Health data sent for processing, and never stored

What is sentWhenWhyRetained?
Recent training, food numbers, MIND check-ins, journal entries from the last 7 days in your own words, goals, onboarding answers, and the coach's recent notes and messagesOnly when you ask the AI coach a questionSo the answer is about your actual life instead of generic adviceNo. Exists for one request, then gone
A photo of a mealOnly when you take one to scanTo estimate what is in itNo. One request, then gone
A transcript of what you said you ate (speech becomes text on your phone; the audio never leaves it)Only when you speak a food logTo estimate what you ateNo. One request, then gone
A barcode numberOnly when you scan oneFood lookup against a public databaseNo

If you never open the coach, never scan a meal and never speak a log, no consumer health data ever leaves your phone.

b. Health data you deliberately publish

Anything you type into Crew is a public post. If you write there about your training, your weight, your eating or your state of mind, you are publishing it to other members, and it is stored on our servers so the community works. Crew is 13+, so assume anything you post there can be read by a member who is a minor, and by every other member.

c. What we do not collect

d. How long we keep it


5. Who we share it with

We do not sell consumer health data. We have never sold it, we do not offer it for sale, and we will not sell it. A sale would require your separate written authorization under RCW 19.373.030. We have never asked for one and do not intend to.

We share consumer health data only with processors acting on our instructions, under contract, and only for the purposes below:

Third partyCategoryWhat it receivesPurpose
OpenRouterAI routingCoach questions with your numbers and recent journal entries; meal photos; spoken food transcriptsRoutes the request to a model
DeepInfra, ParasailUS compute providersThe same, to run the modelGenerates the answer or estimate
SupabaseCloud hostingYour account and anything you post in CrewHosts the community
Open Food FactsPublic food databaseBarcode numbers onlyFood lookup
ApplePlatformSign in with Apple, subscription statusSign-in and payment

We route only to US-hosted providers contractually barred from retaining your data or training on it, and this is enforced in code rather than only on paper — the provider allowlist and a deny-collection setting are pinned in the app's server code, so a change to that list is a change to this policy.

The AI model itself is an open-weight model developed in China (Qwen). It runs on servers in the United States. Your photos, questions and journal entries are not sent to China.

We have no affiliates. DYLD is operated by one person. If that changes, this policy is updated before it does.

We do not share consumer health data with advertisers, data brokers, or analytics vendors, and we do not use it for targeted advertising.


6. No geofencing

We do not, and will not, operate a geofence around any health care facility — or anywhere else. The app does not request location permission and collects no location data of any kind.


7. Your rights, and how to use them

You have the right to:

Two ways to exercise them:

Our timeline: we respond within 45 days. If we need more time we will tell you why inside those 45 days and take up to 45 more.

We will never charge you for this, and never treat you differently for asking.

If we say no, we will tell you why, and you may appeal by replying with the word "Appeal." A separate review is done and you get a written answer within 45 days. If we deny the appeal, we will give you a link to file a complaint with the Washington State Attorney General at atg.wa.gov/file-complaint.

Deleting your data ends your ability to use the parts of DYLD that depend on it. That is a consequence of the deletion, not a penalty for asking.


8. Security

Your account and Crew data sit behind row-level security policies, so one user's data is not reachable by another. Traffic is encrypted in transit. Server-side keys never ship inside the app. No system is perfectly secure, and we will not claim otherwise. If a breach affects your information, we will notify you and the appropriate authorities as the law requires.


9. Changes

If we change the categories of consumer health data we collect, who we share it with, or what we use it for, we will update this policy and obtain your affirmative consent before the new practice starts. We do not apply new uses to data already collected without asking first.


10. Contact

support@dyld.app

DYLD is operated by RJ Galasieski, San Diego, California, United States.


The legal terms in our Terms of Use — including arbitration and the class action waiver in section 13 — apply to disputes about this policy. Nothing in them waives a right this law gives you that cannot be waived, and exercising any right described here will never be held against you.