Regent
Consumer Health Data Privacy Policy
This policy is published by KoyoteByte, LLC. (“KoyoteByte, LLC.,” “we,” “us,” or “our”), an Arizona company, for the Regent Fitness mobile application (also branded as “Regent”) and related services (the “Services”). It applies to consumer health data as defined by Washington’s My Health My Data Act (chapter 19.373 RCW) and similar U.S. state health-data laws, including Nevada’s consumer health data law and Connecticut’s consumer health data provisions. It is a standalone notice. Our general Privacy Policy covers other personal information.
KoyoteByte, LLC. is not a HIPAA covered entity or business associate. This policy is not a Notice of Privacy Practices under HIPAA.
The Services are for people 18 or older. We do not knowingly collect consumer health data from anyone under 18.
1. Categories of consumer health data we collect, and why
When you use Regent, we collect the following categories of consumer health data, only to provide the logging, targets, backup, optional Health connection, and optional estimate features you request, to secure the account, and to comply with law:
- Body measurements and status you enter — sex, age, height, weight, activity level, whether you strength train, start weight, weigh-ins, and goals
- Diet and intake — foods, meals, recipes, leftovers, water, day notes, calorie and nutrient totals derived from that log
- Supplements — products, doses, schedule, and doses you mark taken
- Media you submit to estimate a meal or read a label — photos, text, or voice you choose to send, low-resolution camera frames while Live is on in the meal camera (not stored), and a meal description typed on the welcome screen before an account exists
- Ask my Regent submissions — questions you ask, the summary from your log used to answer them (including your activity level, whether you strength train, seven-day workout totals, your weigh-ins, and your goal weight), and short notes Ask my Regent keeps while its memory is on
- Connected health-repository data (optional) — if you connect Apple Health or Health Connect and grant the relevant permissions, Regent may read weight, body-fat percentage, lean mass, steps, workouts, sleep, resting heart rate, and active energy, and on Apple Health your date of birth, used only to keep your age current (Regent saves your age and most recent birthday, not a separate birth-date field). On iPhone, if you allow it, Regent also writes to Apple Health each food you mark eaten (its name, calories, and nutrients), the nutrients in supplement doses you check off, and each day’s water, and updates entries from the last 30 days when you edit or delete them. What Regent wrote stays in Apple Health until you delete it there. The Health Connect connection is read-only
We use this data to:
- Show your diary, targets, and on-device analysis, including a protein target sized from your latest body composition and, on a lose-fat-keep-muscle plan, a weekly calorie change held while your body-fat readings trend down
- Back up and restore the dataset you save on devices you sign in on. Imported weigh-ins become ordinary Regent weigh-ins and may be included; connected movement, recovery, body-composition, and active-energy snapshots stay on-device
- Run optional AI estimates, label reading, or Ask my Regent responses you start
- Keep optional Health connections in sync
- Provide support you request and protect the Services
Apple Watch, where offered, shows information already on the paired iPhone. It does not collect a separate consumer-health stream.
Connected-health snapshots otherwise stay on your device. An Ask my Regent answer can use a summary from your log, which may include today’s calorie target, your weigh-ins, your goal weight, and your number of workouts and workout minutes over the last seven days, but raw connected-health samples are not sent. Ask my Regent saves a change to your diary or plan only after you confirm it and does not write to Apple Health or Health Connect itself; a confirmed diary change reaches Apple Health like any other entry when saving is on. Its memory notes can be reviewed, deleted, or turned off in Settings → Ask my Regent → Memory.
We do not collect genetic data, diagnoses, prescribed-medication records, reproductive or gender-affirming care records, precise GPS, or biometric identifier templates. Device Face ID or similar unlock, if you use it, is handled by the operating system; we do not receive that template. We do not infer a medical diagnosis from your log, including an eating disorder. We do not use consumer health data for advertising, and we do not sell it. Connected-health snapshots are not copied to your Regent cloud backup. Android system backup is turned off. An iPhone backup you turn on can still include that on-device store.
2. Sources
- You (onboarding, diary, stack, settings, support email, and optional camera, photos, or microphone)
- Apple or Google, only if you sign in with them (account identifiers — not Health data unless you later connect a Health repository)
- Apple Health or Health Connect, only if you grant that permission
- Our processors, when they return an estimate or Ask my Regent response, or store a backup you requested
3. Categories we share, and with whom
We do not sell consumer health data. We have no affiliates. We do not “share” consumer health data with third parties or affiliates as those terms are defined in chapter 19.373 RCW.
We disclose consumer health data to processors under contract, only as needed to provide the Services you requested. That disclosure is not a “sale” or “share” under that chapter when it is made to a processor for the purpose you asked for:
- Supabase — authentication and cloud backup of the dataset you save, encrypted in transit and at rest, hosted in the United States
- OpenAI — AI processing for photo, voice, typed, recipe, and Live estimates and Ask my Regent questions, only after you allow it in the app
Public food catalogs (USDA FoodData Central, Open Food Facts, NIH DSLD) receive a search or barcode, not your diary or Health data. Apple and Google receive Health or sign-in data only as you direct in their permission sheets.
We may disclose consumer health data if we believe in good faith we must, to meet a legal process or to protect rights and safety. On request we will provide a current list of processors that handle consumer health data and a way to contact them.
4. Your rights (RCW 19.373.040 and similar state laws)
If this policy applies to you, you may:
- Confirm and access. Ask whether we collect, share, or sell consumer health data about you, and access that data, including a list of third parties and affiliates (if any) with whom we have shared or sold it and a way to contact them
- Withdraw consent to future collection or sharing
- Delete consumer health data about you. We will delete it from production systems and tell processors to delete it. Copies on archived backup media may take up to six months after we authenticate the request
How to request. Email regent@koyotebyte.com with the subject “Health data request,” or use Settings → Delete account and all data in the app to delete the account and backup. You do not need to create a new account to make a request. We may need to verify you (for example by emailing the address on the account). Up to two free requests per year; we may decline or charge a reasonable fee only for requests that are manifestly unfounded, excessive, or repetitive.
We will respond within 45 days of receiving the request (one extension of 45 days if reasonably necessary, with notice). To appeal a refusal, reply to our decision. We will answer the appeal in writing within 45 days. If we deny the appeal, you may complain to the Washington Attorney General or your state attorney general.
We will not unlawfully discriminate against you for exercising these rights.
5. Geofencing
We do not use a geofence around a facility that provides in-person health care services.
6. Contact
KoyoteByte, LLC.
4539 N. 22nd St., Ste. B
Phoenix, AZ 85016, United States
regent@koyotebyte.com