YYUHA
Training PlansRacesRun Clubs
Sign inSign up

Privacy Policy

Last updated: 18 November 2026  ·  Provider: YUHA HEALTH LLC (DBA Yuha)  ·  Registered: New Jersey, USA

YUHA is a personal health-coaching app operated by YUHA HEALTH LLC, a New Jersey limited liability company based in Jersey City, NJ ("YUHA," "we," "us," or "our"). It consolidates your fitness data from connected services and provides AI-driven insights. This policy explains what we collect, how we use it, and the choices you have. We try to keep this short and plain-English.

Short version: we only collect what we need to coach you. We don't sell your data. You can disconnect any source or delete your account at any time. YUHA's coaching is written by Anthropic's Claude from your own data (Google's Gemini stands in when Claude does not answer, never with Garmin data), and no model is trained on it (the AI Transparency Statement in section 2). If you join a run club, its members can see your name (if you choose) and whether you're going, and never your runs or your health data.

1. Who we are

YUHA is operated by YUHA HEALTH LLC, doing business as Yuha, a limited liability company organized under the laws of the State of New Jersey, with a principal place of business in Jersey City, New Jersey, USA ("YUHA," "we," "us," or "our"). You can reach us at hello@yuha.app for any privacy question, data export request, or deletion request.

2. Information we collect

AI Transparency Statement: how YUHA uses AI. YUHA's coaching is written by an AI model, Anthropic's Claude, from your own data.

  • What it reads: only your own data, from every source you connect, Garmin's included: your runs, sleep and daily numbers, your goals, plan and check-ins, what you write in chat, and the workouts read from the screenshots you attach there (section 4 says which model reads a screenshot itself). It never reads anything about another person.
  • What it writes, and why: your coaching, and nothing else: the words on your readiness and coach cards, run debriefs, training plans, chat answers and push notifications. What it writes is shown only to you.
  • No training: no AI model is trained on your data. YUHA trains none, and Anthropic does not train its models on what YUHA sends it.
  • Your consent for Garmin data: when you connect Garmin, the Connect Garmin screen asks for your consent to the coach reading your Garmin data, before any of it comes to YUHA. Tapping Continue to Garmin gives it, and we record when you did. If you connected Garmin with your Garmin password before Garmin's own sign-in opened in YUHA (section 2.4), you reconnect through Garmin's sign-in when the app asks you to, and the Connect Garmin screen asks for your consent then. Until you reconnect, the coach reads your Garmin data as it did before.
  • Withdrawing it, at any time: in Sources, tap Disconnect on Garmin and check "Also delete my Garmin data from YUHA", or, if Garmin is no longer connected, tap "Delete my Garmin data from YUHA" on its card. Once your Garmin data is deleted, the coach can no longer read it. What YUHA already wrote from that data stays. Disconnecting without deleting stops new Garmin data, but the coach still reads what YUHA already has. You can connect again later, and we will ask again.
  • Changes: if how YUHA uses AI changes, or the law or Garmin's rules change what this statement must say, we update it here and ask for your consent again when the change needs it.

2.1 Information you give us

  • Account info: name, email, hashed password (PBKDF2-SHA256, never stored in plaintext). If you sign up from one of our race pages, we note which page, so we learn which pages help runners.
  • Profile preferences: distance units, age, weight, training days, personal records.
  • Photos you choose: a profile picture, and any image you attach in chat. You pick each one yourself, from your camera or your photo library. YUHA receives only the image you select and never reads the rest of your library.
  • Health data you log manually: workouts, meals, mood, goals, custom notes.
  • Chat messages: what you write to the YUHA assistant, so we can keep context across the conversation.
  • Run club information: the clubs you create or join, your answers to club runs, the check-ins organizers record, the photos you add to a club, the posts, announcements, comments, high fives and poll votes you make in a club's feed and the photos you add to them, the clubmates you follow and who follows you, the high fives you give on a clubmate's club run, your club settings, and the reports and blocks you make (section 6).

2.2 Information from connected services

  • Strava (when you authorize the connection). Your activity history (distance, duration, pace, heart rate, route GPS, elevation, and the kudos and comment counts on your own activities; never who gave kudos or what anyone wrote), your athlete name and id, and basic account information per the OAuth scopes you grant (activity:read_all, profile:read_all, and activity:write only if you allow YUHA to add your planned workout to your activities).
  • Garmin Connect (when you connect through Garmin's own sign-in, section 2.4): activities (with the route your watch recorded, stored as recorded, never shown when it is shorter than 1 km, and trimmed at both ends on a share card you make, and the heart rate, power and elevation recorded along it, kept as a summary for its splits and charts), sleep (its stages and score, your average and lowest blood oxygen, and your breathing rate overnight), heart-rate variability, body battery, stress, VO2max, daily steps, calories, intensity minutes and floors climbed, resting heart rate, the body measurements you record (weight, BMI, body fat, body water, muscle and bone mass), and the name of the device that recorded an activity. If you connected Garmin with your Garmin password before Garmin's own sign-in opened in YUHA (section 2.4), we also keep what that connection stored, including Garmin's training load.
  • Google Health (Fitbit & Pixel) (if you connected it before September 2026; YUHA no longer offers this connection): activities, sleep, daily steps, heart rate, and related wellness metrics per the scopes you grant.
  • Apple Health (iOS app only, when you grant Health access): workouts, steps, sleep, heart rate, resting heart rate, heart-rate variability, VO2max, active energy, walking/running distance, and body measurements you choose to share. When you also allow Workout Routes, we read the workout routes your Apple Watch recorded (the GPS positions along an outdoor workout) together with that workout's heart rate, cadence and power over time, so its map, splits and charts can be drawn. A route is stored as your watch recorded it, a route shorter than 1 km is never shown, a share card or Flyover video you make leaves off the first and last stretch of an everyday run (at least 400 meters, or a tenth of the route when that is longer, at each end) so it does not point to where you live, while a race's public course is drawn whole, the raw points are not kept once the summary is made, and all of it is deleted with your account. This data is read on your iPhone via Apple's HealthKit framework and securely uploaded to your YUHA account. We use Apple Health data only to provide YUHA's features to you: your dashboard, readiness score, insights, and coaching. We never use HealthKit data for advertising or marketing, never sell it, never share it with third parties or data brokers, and never store it in iCloud. You can revoke access at any time in iOS Settings → Privacy & Security → Health, or disconnect Apple Health in the app's Sources screen.
  • Health Connect (Android app only, when you grant Health Connect access): workouts (with their heart rate, distance and elevation gained), steps, sleep, heart rate, resting heart rate, heart-rate variability, VO2max, and walking/running distance. When you allow it for a run on Health Connect's own route screen, we also read that run's route for its map, stored as your device recorded it, never shown when it is shorter than 1 km, and trimmed at both ends on a share card you make. Health Connect is Android's on-device health store; apps such as Fitbit, Samsung Health, Wear OS and Pixel write into it, and YUHA reads only the categories you approve on the Android permission screen. This data is read on your Android phone and securely uploaded to your YUHA account. YUHA only reads from Health Connect and never writes to it. We use Health Connect data only to provide YUHA's features to you: your dashboard, readiness score, insights, and coaching. We never use it for advertising or marketing, never sell it, and never share it with third parties or data brokers. You can revoke access at any time in Android Settings → Security & privacy → Privacy → Health Connect (or in the Health Connect app on older Android versions), or disconnect Health Connect in the app's Sources screen.
  • We do not receive credit card numbers, contact lists, or location data outside the GPS tracks attached to your activities.

2.3 Technical information

  • Cookies: four. yuha_session (HttpOnly) keeps you signed in for 30 days. yuha_login_device (HttpOnly) remembers for a year a browser or app you signed in from, so too many wrong guesses at your password by someone else never lock you out. yuha_appearance remembers your Light or OLED black choice for a year. yuha_market remembers for a year which of our home pages to show you, India or the United States, once you switch or open a link that picks one, and holds only that word. None is used for advertising.
  • Analytics (website only): on the YUHA website we use Google Analytics (GA4) to understand aggregate, anonymized usage (such as page views and which features are used) so we can improve YUHA. GA4 sets its own cookies (for example _ga) and processes this data under Google's terms; IP addresses are anonymized, Google signals and ad personalization are disabled, and we do not enable cross-site advertising profiles. The YUHA iOS and Android apps load no analytics at all. The apps contain no advertising or analytics SDK, never access your device's advertising identifier, and do not track you across other companies' apps or websites. We use no other third-party tracking SDKs anywhere.
  • Server logs: standard request logs (IP, timestamp, endpoint) retained for up to 30 days for security and debugging.

2.4 Garmin

  • How it connects: you connect Garmin on Garmin's own sign-in page, opened from the Connect Garmin screen in YUHA, which first asks for your consent (the AI Transparency Statement above). YUHA never sees your Garmin password: Garmin gives YUHA access tokens, which we keep encrypted (section 7). On Garmin's page you choose what YUHA may read and whether it may send workouts to your Garmin calendar, and you can change that later in your Garmin Connect account. Garmin sends YUHA new data when your watch syncs with Garmin Connect. YUHA stores only the kinds of data you allowed; turning one off stops new data of that kind and deletes nothing.
  • If you connected with your Garmin password: Garmin's own sign-in opened in YUHA on 7 November 2026. A connection made before then with your Garmin email and password keeps working until you reconnect through Garmin's sign-in or until 14 November 2026, whichever comes first. Then we delete your Garmin email, password and session from YUHA. The Garmin data YUHA already has stays.
  • What YUHA sends to Garmin: when you connect, you agree that YUHA puts your planned workouts on your Garmin calendar: the runs in your training plan and on your Workout Plan, including club runs you said you're going to. Each carries a name such as "YUHA · Tempo" (which can include its start time, your race and where its paces come from), its day, and its steps, with the distance or time and the pace or heart rate to aim for. YUHA sends nothing else: no readings, notes or chat, nothing an organizer wrote, and nothing about anyone else. YUHA changes or removes only the workouts it put there. Once a workout is in your Garmin account, Garmin holds it under its own terms and privacy notice and may use it, and it stays there if you disconnect or delete your YUHA account; you can delete it in Garmin Connect. To stop the sending, turn off workout sending for YUHA in your Garmin Connect account, or disconnect.
  • Only you see it: your Garmin data is shown only to you, inside your YUHA account; a card of your run goes to others only when you share it yourself. One Garmin account connects to one YUHA account. Your Garmin data is never sold, never used for advertising, never shown to the members of your run clubs (section 6.3), and never used to decide anything about your credit, insurance or work. The service providers in section 9 process it on our behalf and for nothing else.
  • Disconnecting: tap Disconnect on Garmin in Sources, or remove YUHA in your Garmin Connect account. Either way Garmin stops sending YUHA data and YUHA stops sending workouts. When you disconnect in YUHA, we also tell Garmin to end YUHA's access. The Garmin data YUHA already has stays in your account, so your history, trends and coaching keep it, unless you choose to delete it.
  • Deleting your Garmin data: in the Disconnect sheet, check "Also delete my Garmin data from YUHA", or, if Garmin is no longer connected, tap "Delete my Garmin data from YUHA" on its card in Sources. We then delete the Garmin data tied to your account: your activities with their routes and charts, sleep, heart-rate variability, daily numbers, VO2max, body measurements, training load, the deliveries from Garmin still waiting to be processed, and YUHA's records of the workouts it sent for days already past. What YUHA already wrote from that data stays. YUHA keeps its record of the workouts it put on your Garmin calendar for today and later, so reconnecting Garmin does not put them there twice; each record is deleted once its day has passed, unless you connect Garmin again before then. Deleting your YUHA account deletes all of it too. You can also ask for deletion at hello@yuha.app.
  • Garmin's own policies: your use of Garmin stays under Garmin's own terms, and Garmin handles your data under its privacy notice at garmin.com/privacy/connect.

3. How we use your information

  • To provide the core service: show your dashboard, generate insights, answer your questions, build training plans, and send the weekly digest email, which is on unless you turn it off.
  • To send you transactional emails (password resets, the weekly digest unless you turn it off, security notices). We do not send marketing emails.
  • To improve YUHA: diagnose bugs, identify patterns at an aggregated level. We do not build advertising profiles.

4. AI processing

YUHA's coaching is written by Anthropic's Claude, as the AI Transparency Statement in section 2 says. When Claude does not answer, Google's Gemini may write your readiness, session and coach cards and your push notifications instead, from the same information, but never for anyone with Garmin data in YUHA; chat answers and training plans are written only by Claude. Each request carries only the context that piece of coaching needs (for a chat reply: your message, your recent activities, goals and memory facts). It is only ever your own context: it never includes anything about another person, including the other members of your run clubs. When you attach a screenshot in chat to log a workout, the image and any note you type with it are sent to Anthropic (Claude) with YUHA's instructions for reading the workout from the picture and today's date, or to Google (Gemini) when Claude does not answer. Nothing else of yours goes with them, and no Garmin data. Anthropic and Google process these requests under their commercial API terms and do not use API content to train their models.

5. Strava-specific terms

Powered by Strava. YUHA reads your Strava data through the Strava API only to power the features you use inside YUHA, under Strava's API Agreement and API Policy.

  • What we read: your activities (distance, duration, pace, heart rate, route, elevation, and the kudos and comment counts on them) and your athlete name and id, per the scopes you grant. New activities arrive automatically through Strava's webhooks. We never read who gave you kudos or what anyone wrote, and we never store other athletes' data.
  • Only you see it: your Strava data is shown only to you, inside your YUHA account. It is never shown to other YUHA users, including the members of your run clubs (section 6.3), and it is never sold or shared. The service providers in section 9 process it on our behalf and for nothing else.
  • What we write to Strava: only if you allow it, YUHA adds the workout it planned to the title and description of the matching activity on Strava, for example "Tempo Run" and "Week 3 of 14, NYRR Abbott Dash 5K Training Plan". It never changes a title you typed or a description you wrote, never writes paces or health data, and never posts, creates or deletes an activity. Turn it off in Account, or undo it on the activity's page in YUHA.
  • Withdrawing consent: tap Disconnect on the Sources page in YUHA, or remove YUHA at strava.com/settings/apps. Either way YUHA stops reading your Strava data and stops writing to your Strava activities at once.
  • Deletion: when you disconnect, remove YUHA at Strava, or delete your YUHA account, we delete the Strava data tied to your account (activities, splits and heart-rate summaries, athlete stats, the summaries the coach wrote from them, the write-up records YUHA keeps, and the access tokens) and email you a confirmation when it is deleted. When you click Disconnect in YUHA, you choose whether that happens right away or after 30 days in case you reconnect; YUHA shows none of it meanwhile, and reconnecting within the 30 days keeps it. Undo is open for 24 hours after YUHA writes to an activity. For those 24 hours YUHA keeps the activity's earlier title, and its title and description as YUHA left them, then deletes them. The workout YUHA added stays on that activity's page in YUHA, and goes with the rest of your Strava data when you disconnect Strava or delete your account. You can also ask for deletion at hello@yuha.app. An activity you delete or make private on Strava is removed from YUHA within 48 hours.
  • Strava's own policies: your use of Strava stays governed by Strava's Privacy Policy, which controls over this section for Strava data if the two ever conflict. Strava may collect usage data about YUHA's use of its API, such as request volumes, under its own policies.

6. Run clubs

Run clubs let people organize group runs and meet in person. Creating or joining a club is optional, clubs are free, and they are for people 18 and older. This section explains what other people in a club can see about you, and what they never see. Clubs never change who can see your runs: those stay yours alone.

6.1 What other club members can see

  • Your name and profile picture, if you choose. When you ask to join a club, or say you're going to one of its runs before you're a member, the form asks whether to show your name and photo to club members. The box starts checked; uncheck it to keep them to the organizers. With it checked, members see your first name and the first letter of your last name (for example, "Amara K.") and your profile picture if you have one; unchecked, other members see you as "Club member". Your answer applies to that club, and you answer again for each club you join. You can change it at any time on the club's page, under More. Hiding your name also pauses following through that club (section 6.12). If you create a club, its members see your name as its Admin.
  • Your role in the club: Admin, Captain or member.
  • Whether you're going to a club run and, after it, whether the organizers checked you in, shown with your name or as "Club member" by the same choice.
  • The club runs you were checked in at, to the clubmates you let follow you. If you let a clubmate follow you, they see the club runs the organizers checked you in at, as section 6.12 says. You can choose that they see none.
  • Club photos, which may show you: the ones the club's Admin and Captains add, and the ones any member adds to a post in the club's feed, up to 4 a post (section 6.4).
  • Your posts, comments and high fives in the club's feed. Members see your posts and comments under your name, or as "Club member", by the same choice; the Admin and Captains see your name on them (section 6.2). A high five shows your name only if you show it to the club; otherwise it is only counted, for everyone. After you leave the club, your posts and comments show as "Former member".
  • Your votes in club polls. Polls are anonymous: nobody in the club, the organizers included, sees how you voted. People see how many votes each choice got, members once they have voted or the poll has closed.
  • Your comments on a club's runs. Members see them under your name, or as "Club member", by the same choice, on the run's page; the Admin and Captains see your name on them. After you leave the club, they show as "Former member". On a women-only run, only the people going and the club's Admin and Captains see its comments.
  • YUHA's own cards in the club's feed: a new run with the name of the organizer who posted it, a run cancelled or moved, how many people were checked in at a run, photos added to a run's album, last week's new members, and a member's 5th, 10th, 25th, 50th or 100th check-in in that club. A card names someone only if they show their name to the club: new members who don't are counted, and no check-in card is made for them.

6.2 What the club's Admin and Captains can see

The people who run a club need to know who is coming, so the Admin and Captains always see your name (first name and the first letter of your last name), whatever you chose in section 6.1:

  • on the member list, with your role and the date you joined;
  • on a request to join: your name, and whether you came by a link (the club's or a run's), by the club's QR code or by YUHA's invite, and "From your list" if your email is on a member list the club's Admin added (section 6.11). If you say you're going to a run before you're a member, they see you on that run's list marked "New";
  • on the run day list: who said they're going, who they checked in, anyone they added on the day, and whether you asked for no photos of you (section 6.4);
  • on your posts and comments in the club's feed and your comments on its runs;
  • after a run: who was checked in, who said they were going and was not checked in, the number checked in compared with the week before, and a file of that same list (name, whether you said you were going, whether you were checked in);
  • the club's Admin and Captains also see the requests waiting and the people declined.

Nobody in a club sees your email address (but see 6.11: an Admin who added your address learns it's yours when you ask to join), and nobody in a club sees anything from your runs or your health data.

6.3 What never leaves you

  • Your runs and health data. Nothing from your runs or your health is ever shown to anyone in a club: no pace, distance, time, heart rate, route, map, start or finish point, sleep, readiness or any other measure, whether it came from Strava, Garmin, Apple Health, Health Connect, the Ultrahuman Ring or anything else, or you logged it yourself. We never add up runs across a club or build a leaderboard.
  • Attendance comes only from the organizers' check-in. If YUHA finds a run of yours that looks like a club run, it asks you, and only you, whether to count it as the club run. Your answer, the "Club run" label on your activity and your own club-run milestones, counted across all your clubs, are shown to you alone. Separately, if you show your name to a club, its members see a card in the club's feed when the organizers have checked you in for your 5th, 10th, 25th, 50th or 100th run in that club. If you share a card of your own run, it can carry that label; sharing it is your choice. The club runs you were checked in at are seen by the club's Admin and Captains (6.2) and, unless you choose otherwise, by the clubmates you let follow you (6.12). Your own runs, and your answer to whether a run of yours was the club run, never are.
  • Your Workout Plan. When you say you're going, the run goes on your own Workout Plan, where only you see it. Your coach sees it as one of your own sessions with a fixed label such as "Club run · tempo". The coach never sees what an organizer wrote, and never sees anything about another member. One person's data never reaches another person's coaching. Nothing in a club's feed (posts, polls, comments, high fives or YUHA's cards) is ever seen by your coach or sent to our model provider (section 4).
  • Who invited whom. We don't record who invited whom, except that a club's member list records which Admin added it (6.11). We record only whether you joined by a link (the club's or a run's), by the club's QR code or by YUHA's invite.

6.4 Club photos

  • A club's Admin can set a cover photo and a logo, and the Admin and Captains can add photos to a run's album. Every member can also add up to 4 photos to a post in the club's feed. Club photos are shown only to the club's members, always through YUHA, which checks membership on every request; there are no public links to them. The one exception is a club's logo, which anyone can see (sections 6.5 and 6.9). A photo in a post is shown only while the post is up, and not to someone who blocked its author; a phone or browser that has already shown one may keep its own copy for up to 30 days.
  • Every photo is saved again when it is uploaded, which removes its location (GPS) and all the other details your phone writes into a photo.
  • "Please don't post photos of me" on your Account tells the Admin and Captains of every club you're in that you would rather not be photographed. They see it on the run day list. Members adding photos to a post see it too: the people going to the run the post is tagged with, or else the club's members. They see your name if you show it to the club, and otherwise only a count.
  • A photo and its files are deleted when it's removed, when its club closes, or when the person who added it deletes their account. A photo in a post is also deleted when its author deletes the post, and one added to a post that was never posted is deleted after 24 hours. When the club's Admin or Captains or YUHA remove a post, its photos are kept with it for YUHA's review. If a photo shows you and you want it removed, ask the club's Admin or report it (section 6.6).
  • Club photos are stored in Microsoft Azure, in private storage that only YUHA can read.

6.5 Club and run pages anyone with the link can open

  • Each club and each run has a page that anyone with its link can open, so organizers can share it. It shows what the organizers wrote (the club's name, description, rules and city, and its waiver if it has one; the run's name, time, meeting place, distance and notes), the club's logo if it has one, and how many people are going. It never shows who is going, anything from the club's feed, or a run's comments.
  • A club's cause. If a club runs for a cause, its name, its donation link and its logo are public like the club's name: they show on the club's page and its runs' pages, in Find a club and on YUHA's city pages, and on the share cards of runners who ran a club run for it. YUHA doesn't handle, hold or check donations: a donation happens on the site the link opens, under that site's terms, and YUHA never opens the link itself.
  • For a women-only run, that page shows only the area and the time, and no count. The exact meeting point and notes are shown only to the people going. To say you're going to a women-only run, you're asked once to confirm your gender, which is saved to your profile.
  • A club's page lists its runs by name, day and time only. A run's meeting place, distance, notes and the number going are on the run's own page.
  • A run's page asks search engines not to list it, and so does the page of a club that is not listed in Find a club (section 6.9). Search engines may show the page of a listed club. That page lists no women-only run. When someone shares a link in a messaging app, that app may fetch a preview with the club's name, its logo, and the run's time and place.
  • YUHA's city pages. YUHA also has a public page of run clubs for each city, such as yuha.app/run-clubs/jersey-city-nj, and search engines may show it. It lists the clubs listed in Find a club (section 6.9) with each club's name, logo, city and description, the days it runs and its next run, and the runs of the coming week with their day, time, length and meeting place. It never shows who is in a club or who is going, a member count, anything from the club's feed, or anything about a women-only run.

6.6 Reports, blocks and moderation

  • Reporting. You can report a club, its logo, a run, a post, a comment in a club's feed or on a run, a photo or a person. A report keeps the reason, your note if you write one, a copy of what you reported as it read then, and your account. YUHA's team reviews it. We don't tell the club or the person reported who made a report.
  • Blocking. You can block a person in a club. They then see your name nowhere in any club and can't join a club you're the Admin of, and you no longer see their posts and comments in any club's feed, or their comments on its runs. We don't tell them. Your blocks are listed on your Account, where you can undo them.
  • What YUHA can do. To keep clubs safe, YUHA's team can see club records, remove a run's words, a post, a photo, or a comment in the feed or on a run, cancel a run, hide a club (its runs still to come are then cancelled and everyone going is told), and stop an account from using clubs. The club's Admin and Captains can also remove someone's post or comment in the feed, or their comment on a run (a Captain can't remove the Admin's). A removed post or comment is kept, marked removed, for YUHA's review. YUHA's word filter checks the words of clubs, runs, posts and comments when they are saved.

6.7 Club messages

  • Clubs send push notifications: a new run (a women-only run only to members whose profile says female), "Going again?" after a weekly run, a run you're going to that moved to another day or start time or to a new meeting place, or that was cancelled (by its organizer: one run, the rest of a weekly run, or an end date moved earlier; or by YUHA when it hid the club), a run made women-only that took you off it, the answer to your request to join, a club that closed, and, for a club's Admin and Captains, a request to join and one evening push a day saying how many people are waiting, and, for a club's Admin, once, when Find a club began, a note that their club shows there and how to turn that off. Where a club has its feed, they also send the club's announcement, at most one a day, and comments on your post, at most one push an hour for each post. When a poll you voted in or made closes, they send a notification that it closed, with the number of votes for the person who made it, never its words. For a club's Admin and Captains, they also send comments on the club's runs, at most one push an hour for each run. If you follow clubmates, you also get a notification when a clubmate asks to follow you, when one approves your request, and when one gives your club run a high five; you can turn each of these off in your notification settings.
  • We email you about a club only when no push notification can reach you, and only five things: "You're in", a run you're going to that moved to another day or start time or to a new meeting place, a run you're going to that was cancelled, by its organizer or by YUHA when it hid a club, and that your club posted an announcement (never its words), and, if you're on a club's member list, its invite and one reminder (6.11).
  • Your weekly YUHA email also lists the club runs coming up that week.
  • You can mute a club on its page, or turn off "Run clubs" in your notification settings, or stop club invites from the invite itself.

6.8 How long we keep club data

  • When you leave a club, your membership ends and you come off its runs still to come. A run that has already happened is shown as the club stands now, so it no longer names you. Your posts and comments stay in the club's feed, shown as "Former member"; you can delete them before you leave.
  • When you delete your account, we delete your memberships, your answers to club runs and their check-ins, your club settings and your blocks, your posts (with the comments and high fives on them), your comments and your high fives, your follows, both the people you follow and your followers, and the high fives you gave or got on a clubmate's club run, and the photos you added, files first. Your votes in club polls stay in each poll's count, with no link to you. YUHA's cards that named you are taken off the feed, keeping no name and no account id. A club you were the Admin of passes to its longest-serving Captain, or closes if it has none. The words a club or a run was written with stay with the club, without your name. A club waiver you agreed to is kept as section 6.10 says.
  • A club's feed shows its last 6 months. Older posts, comments and photos are not deleted for their age and stay in our database. When a club closes, its whole feed and all its photos are deleted.
  • Comments on a run are shown for 6 months after the run. They are deleted when the club closes or when their writer deletes their account.
  • If you add your club runs to a calendar, YUHA makes you a private calendar link that holds the runs of the clubs you're in, as your club pages show them to you. Anyone who has the link can see those runs, so keep it to yourself. Make a new link turns the old one off. The link is deleted with your account.
  • Reports you made stay, without your name or your note, so YUHA can still act on them. Reports about you lose your name.
  • To stop spam, we count the follow requests you send each day; a day's count is deleted two days later.
  • We count, as totals with no names, how many times club links are opened and how many people say they're going, to improve how people join. YUHA's team also sees each club's weekly totals (members, people waiting to join, runs, people going and checked in) to keep clubs running well. They name no person.

6.9 Find a club

  • What signed-in YUHA runners see. Anyone signed in to YUHA can look for run clubs in the United States and India on the Run Clubs tab. For each club listed there, they see its name, logo, color, city, how far it is from them, how many members it has, and the day and time of its next run. For a listed club's runs in the next 7 days, they see each run's name, kind, day, time, length, how far away it is, and how many people are going.
  • What its lists never show. Find a club's lists never show who is in a club or who is going to a run, members' names or faces, cover photos or any other club photo other than its logo, a run's exact meeting point or notes, anything from the club's feed, or anything about a women-only run. Find a club is not open to people who aren't signed in, and search engines can't see it.
  • Opening a club or a run. Tapping a club or a run in Find a club opens its page, the same page anyone with its link can open (section 6.5). That page shows what the organizers wrote, including the meeting place, except for a women-only run.
  • Every club is listed unless its Admin turns that off. A club's Admin can turn off "List this club in Find a club and on YUHA's city pages" in Club settings; the club is then reached only through its link, and it leaves YUHA's city pages (section 6.5). Asking to join from Find a club works as it does from a link: the club's Admin or its Captains approve everyone who joins. A club YUHA has hidden, a closed club, and a club whose Admin blocked you are never listed to you.
  • Your city. To put the nearest clubs first, Find a club uses the city you pick there, or else the city on your profile. A city you pick there is kept as one of your club settings, is used for nothing else, and is deleted with your account (section 6.8). You can change it at any time.

6.10 Club waivers

  • A club may ask you to agree to its waiver. A club's Admin can ask new members to agree to the club's waiver when they ask to join, and again every 12 months when they say they're going to a run. The waiver's words are the club's, not YUHA's.
  • What we keep. When you agree, we keep a copy of the exact words you agreed to, your full name as it is on your YUHA account, the date, and the date it renews.
  • Who sees it. Only the club's Admin sees that you agreed, with your full name, the date and the words. Captains and other members don't.
  • How long. We keep each agreement for 3 years after it ends: after its 12 months pass, after you leave the club, or after you delete your account, whichever comes first. Then we delete it. If you delete your account, the record keeps your name, the date and the words, but no longer links to your account.

6.11 Bringing a club's members to YUHA

  • A club's Admin can add a list of their club's members' email addresses, for example from Heylo. YUHA reads only the email addresses. The rest of the file, such as names, stays on the Admin's device.
  • If the Admin asks YUHA to invite them, YUHA sends each address at most one invite and one reminder from that club: by email, or, if the address belongs to a YUHA account a push notification can reach, by push notification. Every invite lets you stop club invites from YUHA: a link in the email, or "Not your club? Stop club invites" in the app.
  • The Admin sees only how many people on the list joined or asked to join since the list was added, how many haven't yet, and how many opted out. The Admin never sees who has a YUHA account or how anyone was invited. If you're on the list and ask to join, the club's Admin and Captains see that you're from the club's list, so the Admin learns that the address they added is yours.
  • We keep the list until the Admin deletes it or the club closes. For a year after each invite we keep a record that it was sent, with a one-way code of the address instead of the address, so a club can't invite you twice. When an address stops club invites, bounces or reports an invite as spam, we delete it from every club's list at once and keep its one-way code, so YUHA never invites it again. When you delete your YUHA account, your email comes off every club's list.
  • We use the list only to invite those people to that club, as described here.

6.12 Following clubmates

  • Who can follow you. Only a member of a club you're both in, while both of you show your name in that club (6.1), the club's Admin leaves following on, and neither of you has blocked the other. Someone who sees you as "Club member" can't follow you, and nobody can follow you from outside your clubs.
  • Private or public. Your profile is private to start: you approve each request to follow you. If you make it public, a clubmate who can follow you does so without asking. Either way, only your followers see your club runs, and nobody but you sees which you chose.
  • What a follower sees. Your name, and the clubs you share where your name shows. Then, unless you choose "Nothing" under "What followers see", the club runs the organizers checked you in at in the last 4 weeks, only from clubs you share with that follower where both your names show: the club, the run's name, its day and time of day, the distance the organizer set, and the route the organizer planned. A women-only run, a cancelled run and a run still to finish are never shown. A follower never sees anything from your own runs, your trackers or your health, and never a count of your followers.
  • High fives. A follower can give a high five on a club run they see. You see who gave it, by first name; nobody else does, and nobody sees a count. A high five shows only in a club where its sender shows their name.
  • Your choices. On the Following screen you can approve or decline a request, remove a follower, unfollow someone, choose who can follow you and what your followers see, and see your profile as your followers see it. We don't tell anyone that you declined their request, removed them or unfollowed them. A new request from someone you declined or removed is held for 30 days and never reaches you.
  • When a follow pauses. If the two of you no longer share a club where both your names show, because one of you left, hid your name or was removed, the club closed, or its Admin turned following off, the follow pauses: your follower sees nothing of you until you share such a club again. A block ends the follow both ways, and the high fives between you are deleted.
  • Limits. A member can send up to 20 follow requests a day and follow up to 300 people. A request no one answers lapses after 30 days.

7. How we store and protect your data

  • Storage: MongoDB Atlas, encrypted at rest. Hosted in regions disclosed by Atlas.
  • Transit: all API traffic uses TLS (HTTPS).
  • Multi-tenant isolation, every record carries your user_id; queries always filter by it. Other users cannot see your data, except what you share in a run club as section 6 describes.
  • Passwords: stored only as a one-way hash (PBKDF2-SHA256, 600,000 rounds). We cannot see or recover your password; a reset lets you set a new one. The codes we email you are stored the same way.
  • Connections: the tokens YUHA keeps to stay connected to your other services are stored encrypted (Fernet: AES encryption with an integrity check), scoped to your user. That covers the Strava OAuth tokens, the Garmin OAuth tokens, and the Google Health and Ultrahuman Ring access and refresh tokens. The tokens your phone uses to send Apple Health or Health Connect data are stored only as a one-way hash. YUHA never asks for your Garmin password. If you connected Garmin with your Garmin email and password before Garmin's own sign-in opened in YUHA, your Garmin email is stored as it is, and only your password and your Garmin session are stored encrypted, until you reconnect through Garmin's sign-in or until that connection ends (section 2.4); then all three are deleted.

8. How long we keep your data

  • While your account is active, for as long as you use YUHA.
  • Server logs, up to 30 days.
  • Strava data, right away when you remove YUHA at Strava or delete your account, and when you disconnect Strava in YUHA, right away or after 30 days, as you choose (section 5); an activity you delete or make private on Strava is removed within 48 hours.
  • Garmin data, until you delete it from YUHA (section 2.4) or delete your account; disconnecting alone keeps it. A delivery from Garmin is also kept as Garmin sent it until YUHA has processed it, and for up to 7 days after, then deleted; a delivery YUHA could not process is deleted 30 days after it failed.
  • Run club data, as section 6.8 describes.
  • After account deletion, health data is removed within 30 days; backups are purged within 90 days.

9. Sharing

We share data only with the service providers required to run YUHA:

  • MongoDB Atlas, database hosting.
  • Anthropic: Claude, the AI model that writes your coaching and reads a screenshot you attach in chat to log a workout (the AI Transparency Statement in section 2, and section 4).
  • Google: Gemini, the AI model that reads a screenshot you attach in chat when Claude does not answer, and in the same case writes your cards and push notifications, never for anyone with Garmin data in YUHA (section 4).
  • Resend: transactional email.
  • Garmin: when you connect Garmin, the planned workouts YUHA puts on your Garmin calendar (section 2.4).
  • Push services (Google's Firebase Cloud Messaging, Apple's push service, and your browser's push service on the web): deliver your notifications, whose words can include your own numbers.
  • Google Analytics: aggregate, anonymized usage analytics on the website only, never in the mobile apps (per section 2.3).
  • Open-Meteo, Google Places, Google Maps, OpenRouteService, GraphHopper, OSRM: services queried for weather, place search (a place you name in chat, your city at setup, a club's meeting point), time zones and routing. We send only the place names or coordinates needed for the request, never your account identity.
  • OpenFreeMap and OpenStreetMap: the map pictures behind a route map, a club's meeting point and the Flyover share video. Your browser or app loads them straight from these services, so they see your IP address and which part of the map is being drawn, never your account identity or the route itself.
  • Microsoft Azure, application hosting, and private storage for club photos.

In a run club, the other people in the club see what section 6 describes, and nothing more.

We do not sell your data and do not share it for advertising.

10. Connected assistants

You can connect YUHA Coach to a third-party assistant such as Claude, so it can answer with your YUHA data. Nothing reaches an assistant unless you connect it and approve what it may read. When you do:

  • Only your own data is read, only the groups you allowed (today and your coach, your plan and goals, your history, your club runs, races), and only to answer what you asked. The connection cannot change anything in YUHA, and it never includes your tracker logins. It never includes Strava data either, unless you have asked YUHA in writing to allow it for your own account.
  • You can switch a group off, or end the connection, on the Account tab under Connected apps, or by removing YUHA in the assistant. Either one stops it at once.
  • What the assistant's provider does with what it reads is governed by that provider's own policy, not this one.
  • YUHA keeps a record of each connection and of what it asked for, never the answers themselves: the record of each call for 30 days, a connection's daily counts for 400 days, a connection until you end it, then its record for 90 days, and an app that never received a connection for 30 days after it registered.

The setup steps are at yuha.app/connect-assistant.

11. Your rights and choices

  • Access & export, email hello@yuha.app and we'll send your data within 30 days.
  • Correction: edit your profile in-app, or email us.
  • Deletion: delete your account from the profile screen, or email us. Connected-service tokens and cached data are removed with the account.
  • Disconnect a source. Go to Sources in YUHA and click Disconnect. We immediately revoke the token and stop syncing. For Garmin, we also tell Garmin to end YUHA's access (if Garmin does not answer, we keep trying for up to a day), and keep the Garmin data YUHA has unless you choose to delete it (section 2.4).
  • Run clubs: show or hide your name and photo in each club at any time, leave a club at any time, mute a club, block a person, report anything, turn on "Please don't post photos of me" on your Account, and choose who can follow you and what your followers see (section 6).
  • Withdraw consent, by disconnecting or deleting your account. To withdraw your consent to the coach reading your Garmin data, disconnect Garmin and check "Also delete my Garmin data from YUHA", or tap "Delete my Garmin data from YUHA" if Garmin is no longer connected (the AI Transparency Statement in section 2).

12. Children

YUHA is not intended for children under 13 (or under 16 in regions where applicable law sets a higher age). We do not knowingly collect data from children. Run clubs are for people 18 and older.

13. International transfers

YUHA is hosted on infrastructure that may process data outside your country of residence. Where applicable, we rely on standard contractual clauses to safeguard transfers.

14. Changes to this policy

If we change this policy materially, we'll post the updated version at this URL and, where appropriate, notify you by email. The "Last updated" date above always reflects the current version.

15. Contact

YUHA HEALTH LLC
Jersey City, New Jersey, USA
Email: hello@yuha.app

Questions, requests, or complaints? Email hello@yuha.app.

YYUHA

The Readiness Coach for Runners. Built on your data, on iPhone, Android and the web.

YUHA for iPhone Download YUHA on the App Store YUHA for Android Get YUHA on Google Play

Product

Features YUHA Coach Pricing NYRR 9+1 Tracker Run Clubs Races Share your run

Company

About FAQs Contact

Legal

Privacy Policy Terms of Service
© 2026 YUHA HEALTH LLC. All rights reserved.