vorka.run
Privacy policy
Last updated: 5 September 2026
This policy explains how vorka.run (“vorka.run”, “we”, “us”) processes personal data when you use the vorka.run website and training application. vorka.run is the controller of the data described here. Contact us at info@vorka.run.
Information we collect
- Account and access-interest data: name and email address submitted to request access; plus password hash when used, Google or Apple account identifier when selected, account dates, beta invitation redemption, and authentication records if you create an account.
- Training profile: goal race, race date, target time, experience level, current weekly distance, preferred training days, coaching preferences, and constraints you provide.
- Workout and activity data: planned and completed workouts, distance, duration, pace, heart rate, elevation, activity date, sport type, notes, and connected-device or service identifiers. We receive this only when you connect a supported service or add it yourself.
- Coaching data: messages you send to the coach, its responses, recommendations, plan changes, derived training insights, and detailed AI token and cost records. If you separately opt in to diagnostic trace retention, this also includes the complete AI request context, tool results, and response.
- Billing data: Stripe customer and subscription identifiers or Apple App Store transaction identifiers, plus subscription status, product or price identifier, renewal date, environment, and scheduled-cancellation status where available if you subscribe to Pro. Payment details are collected by Stripe or Apple and are not stored by vorka.run.
- Technical and usage data: IP address, device and browser information, pages viewed, app events, crash details, and diagnostic logs.
Why we use it
We process data to respond to access-interest registrations, create and maintain your account, generate and adapt training plans, import completed activities, deliver workouts to services you choose, provide coaching, administer paid subscriptions, secure and troubleshoot the service, respond to support requests, and understand how the product is used.
Our legal bases, where the GDPR or similar law applies, are performance of our contract with you, your consent where we ask for it, compliance with legal obligations, and our legitimate interests in operating, securing, and improving vorka.run. You may withdraw consent at any time without affecting earlier processing.
AI transparency
vorka.run uses an artificial intelligence service provided by Anthropic to generate plans, coaching responses, and proposed plan changes. The information sent may include your training profile, relevant workouts and activities, coaching preferences, and the messages you submit. Activities imported through Strava are excluded from AI processing. AI output can be incomplete or wrong; it is a coaching aid, not medical advice or an autonomous decision with legal or similarly significant effects.
Garmin-sourced data is not sent to an AI system until you give separate, explicit consent. You can give or withdraw that consent in Settings. After withdrawal, Garmin-sourced activities are excluded from new AI requests. Raw activity streams, location coordinates, and original activity files are never sent to the AI service. We do not use connected-service data to train our own general-purpose AI models.
Detailed token counts, model identifiers, request status, and estimated cost are retained with your account for service security, allowance administration, and cost auditing. Complete AI request and response traces are off by default. If you opt in, a trace may contain your messages, training context, preferences, and tool results; it is encrypted with a separate application key, retained for no more than 30 days, excluded from analytics and error monitoring, and deleted when you withdraw trace consent. Strava-sourced data is never included in an AI request or trace.
Connected services
When you connect Intervals.icu, vorka.run requests read access to completed activities and write access to your training calendar using OAuth. Calendar write access is used only when you explicitly push your active plan, publish, update, or remove a supported workout, or send the next seven days; ordinary workout edits do not write externally. Repeated actions create, update, or remove only calendar workouts created by vorka.run. Intervals can then forward those planned workouts through Garmin Connect according to your Intervals connection settings. The access token is encrypted and is removed when you disconnect. Intervals.icu is the ingestion provider; Garmin remains the recorded source for Garmin-origin records. vorka.run stores the activity summary and calculated kilometre splits needed by the product, not the original file, route coordinates, or complete sample streams. Disconnecting stops new imports while preserving already-imported history until you delete it or your account.
Historical Strava records may remain visible, but new Strava connection paths are not active. Strava-derived records remain excluded from AI processing. Garmin-origin information is displayed with Garmin attribution and is also handled under the Garmin Connect privacy policy. Intervals.icu data is subject to its own terms and privacy practices.
Who receives data
We use service providers only as needed to operate vorka.run, including hosting and database infrastructure, Google or Apple when you choose that sign-in method, Anthropic for AI features, Stripe or Apple for subscription billing, Sentry for error monitoring, PostHog for product analytics when configured, and Intervals.icu for user-authorized activity import and plan export. We may disclose information if required by law, to protect users or the service, or as part of a business transaction with appropriate safeguards.
We do not sell personal data. We do not use health or activity data for targeted advertising.
Retention and security
We keep access-interest details while we are inviting prospective users, and account, training, coaching, billing-entitlement, and AI usage-accounting data while your account is active. If you subscribe to Pro, Stripe or Apple processes your payment details and provides us with subscription and billing-status identifiers; vorka.run does not store full card details. Opt-in complete AI traces expire automatically after 30 days and are deleted immediately when trace consent is withdrawn. You can ask us to remove access-interest details, and account data is deleted when you delete your account, subject to limited retention in backups, payment records, security records, or where law requires. Connection tokens are kept only while the service remains connected. We apply access controls, encryption in transit, managed infrastructure, secret separation, monitoring, and data-minimisation practices appropriate to the nature of training and health-related data.
No system is completely secure. If an incident affects your rights, we will notify you and relevant authorities as required by law.
International transfers
Our providers may process data outside your country. Where required, we use recognized safeguards for international transfers, such as adequacy decisions or contractual protections.
Your choices and rights
You can update training preferences, disconnect services, and download a copy of your vorka.run data or delete your account in Settings. Depending on where you live, you may also have rights to access, correct, erase, restrict, object to processing, receive portable data, withdraw consent, and complain to a data-protection authority.
For a request or question, visit Support or email info@vorka.run. We may need to verify that you control the account.
Children
vorka.run is not directed to children under 18, and we do not knowingly collect their personal data.
Changes
We may update this policy as the product or law changes. We will change the date above and provide additional notice when a change materially affects how we use personal data.