How Yigri handles athlete data.

When you sign in to Yigri, we collect basic account information such as your email address.

If you connect Strava, Yigri receives the Strava data you authorize us to access, which may include activity summaries, detailed activity fields, gear information, and related metadata needed to generate athlete-facing insights.

If you connect Apple Health, Yigri receives the workout, health, and fitness data you authorize the app to read so it can import your runs and generate athlete-facing insights.

If you connect Garmin or COROS through Stridee, Yigri receives authorized running activity files and related device metadata. These files can include timestamped route coordinates.

Yigri collects product interaction and usage data through PostHog. PostHog receives your internet protocol (IP) address and derives approximate, city-level location information such as country, city, and coarse latitude and longitude for product analytics. Yigri does not use this information for advertising or cross-app tracking.

If you submit a support request, we collect the information you include in that request.

Yigri uses your data to authenticate your account, connect to your chosen activity source, import your authorized activity history, and generate personalized running insights for you.

For Garmin and COROS imports, Yigri discards route timelines during parsing and retains only the first valid outdoor coordinate needed for weather enrichment, plus location-free running metrics and streams.

Yigri displays Strava-derived data only to the athlete who authorized it. Strava records and analysis that depends on them are excluded from AI connections, including after Strava is disconnected. Apple Health information supports the athlete's running and fitness insights. Sharing through an AI connection requires separate authorization and must be permitted for the source, recipient and location. Your approval cannot override provider restrictions or applicable law.

Yigri uses product interaction, usage, and IP-derived approximate location information to understand product adoption, diagnose broad usage patterns, and improve the service.

Yigri may also use your information to troubleshoot product issues, respond to support requests, and keep the service secure.

You can authorize an AI app, such as ChatGPT or Codex, to read existing Yigri information for your running and fitness questions. Each connection has its own approval. It stays active until you revoke it or access otherwise ends. Any additional prompts before individual reads depend on the AI app's settings.

Depending on the tools you use and the eligible records available, Yigri can share your account ID, training summaries, recent runs, dates, distance, duration, pace, heart rate, recorded weather, stored run analysis, fitness trends, key findings, weekly execution and stored Weekly Readouts. Yigri processes tool arguments, such as a date range or run ID, to return the requested information.

The integration reads existing information. It cannot sync your watch, generate new Yigri analysis, save a training plan or change your account or training data. Garmin and COROS through Stridee, and Apple Health, are technically supported. Sharing is subject to source restrictions and recipient eligibility. Accounts with a current Strava connection cannot use the integration. Previously imported Strava data and analysis based on it stay excluded. Information with unverified origins may be withheld, so results can be incomplete or unavailable.

The selected AI service receives the returned information under its own terms, privacy policy and your settings. It may retain information for responses, personalization, memory or model improvement, depending on your account and settings. Yigri's own AI processing inside the product is separate from that service's handling of information received through your connection.

You can revoke an individual connection in Yigri's AI connections screen. Revocation stops future reads through that connection. It does not delete answers or other copies already received by the AI service. Use that service's controls for those copies.

Yigri uses Supabase for accounts and training records, Ory for AI authorization and restricted credentials, and Vercel for hosting. The AI service does not receive your Yigri password, first-party session or activity-provider credentials.

MCP operational analytics capture is currently disabled in production. Other Yigri product analytics follow the disclosures applicable to those features. There is no separate analytics selection on the AI approval screen. Connection approval and revocation control access to your training information. Contact Yigri support about access, correction or deletion of information held by Yigri.

Application diagnostics use bounded tool names, response states, timing and fixed failure categories. They exclude request bodies and raw exception messages. Hosting and authorization providers may separately process network and security metadata.

Yigri uses third-party infrastructure and service providers to operate the product. These may include hosting, database, authentication, analytics, and AI service providers.

Today, Yigri uses Strava for athlete authorization and activity data, Apple Health for user-authorized workout and fitness data, Supabase for data storage and authentication, PostHog for product analytics including IP-derived approximate location, and OpenAI-backed API processing for certain classification or copy-generation features inside the product.

Yigri uses Stridee to connect Garmin and COROS accounts and deliver the original activity files authorized by the athlete.

You should also review Strava's own privacy documentation because Strava independently governs the data it provides through its platform.

Yigri retains account data, authorized activity data, and analytics data, including IP-derived approximate location, for so long as needed to operate and improve the service, respond to support issues, and satisfy legal or security obligations.

You can permanently delete your account inside the Yigri app at Settings → Delete account. Access stops as soon as the request is accepted, and Yigri-controlled account and training data normally finishes deleting within 24 hours.

External processors, including analytics and connected activity providers, may take longer to verify their cleanup. The app stores a secure deletion receipt in your device Keychain so you can check Yigri deletion and external-cleanup status after sign-out.

Account deletion revokes connected-provider access, cancels pending Yigri messages, removes uploaded files, and requests deletion of associated PostHog analytics events and recordings. Support records associated with the authenticated account or its exact email address are deleted.

Raw Garmin and COROS activity files are stored privately while retryable, for about 24 to 48 hours after successful parsing, or for up to about eight days after a terminal parser or validation failure. The extra time reflects daily cleanup lag. Account deletion removes remaining raw files immediately.

Yigri uses commercially reasonable administrative, technical, and organizational safeguards intended to protect the data under our control.

No service can guarantee absolute security, and you use Yigri at your own risk.

You can choose whether to connect Strava to Yigri.

You can choose whether to grant Apple Health access and can change that access in the Health app.

You can connect or disconnect Garmin or COROS through Yigri. Only one activity source can be primary at a time.

You can request access or correction through the support page and delete your account inside the app at Settings → Delete account.

If you no longer want Yigri to access your Strava account, you can disconnect it from Yigri and revoke the application in your Strava settings.

Yigri may update this policy from time to time. If we make material changes, we may update the effective date and publish the revised policy here.