Training Endurance
PlatformBlog
Open app

Privacy Policy

Last updated: November 15, 2026

This Privacy Policy explains how Charges LLC ("we", "us", "our") collects, uses, shares and protects personal data when you use Training Endurance: the website trainingendurance.com, the web app at app.trainingendurance.com, our iOS and Android apps, and our server for AI assistants at mcp.trainingendurance.com (together, the "Service"). This policy is a separate document from our Terms of Service.

Training Endurance is a training platform for endurance athletes and their coaches. It imports workouts and health metrics from the devices and services you connect, builds and adapts your training plan, and shows analytics to you and to the coaches you choose.

1. Who is responsible for your data

The controller of your personal data is Charges LLC, a limited liability company registered in the State of Delaware, USA.

  • Address: 16192 Coastal Highway, Lewes, Delaware 19958, USA
  • Privacy contact: privacy@trainingendurance.com

Our representative in the European Union under Article 27 GDPR is Training Endurance OÜ, registry code 17513270, Paldiski mnt 225a-2, 13515 Tallinn, Estonia, infoeu@trainingendurance.com. You and supervisory authorities in the EU can contact it on any question about the processing of your personal data. It is a separate company: for the processing described in this policy it acts only as our representative, and Charges LLC remains the controller.

2. Data we collect

Account and profile

Your email address, name, profile photo, date of birth, sex, interface language, time zone and preferred currency. If you choose to add them: a short bio, best results, sports goals, race calendar, links to your social profiles and to your race profiles on ITRA and UTMB. If you sign in with Apple or Google, we receive your name and email address from that service.

Body and performance parameters

Height, weight, body fat percentage, heart rate, pace and power zones, thresholds, VO2max, body type and training background, together with their history.

Training data

Workouts you record, import or enter: date, duration, distance, GPS route, altitude, heart rate, power, cadence, speed, temperature and laps. Workouts and training plans that you or your coach schedule, and your training calendar. Activity files you upload.

Health and wellness data

Sleep, heart rate variability, resting heart rate, stress, blood oxygen saturation (SpO2), respiration rate, blood pressure, energy and recovery scores, skin temperature, body composition, steps and daily activity. Daily notes on how you feel and what you eat, blood test results you enter, and lactate measurements from a Bluetooth lactate meter you connect in our iOS or Android app or in a browser.

We treat everything in this group and in the two groups above — body and performance parameters and training data — as health data: most of it describes the state of your body, and it is stored together. We process health data only to provide the Service to you and to the coaches you choose, and from November 15, 2026 we ask for your explicit consent to it (section 4). We also keep a record of your decisions about health data (sections 4 and 9).

Coaching and messages

Your connections with coaches, athletes, schools and teams; notes a coach keeps about an athlete; discussions and the files attached to them; invitations you send, including the email address of the person you invite.

AI assistant

Your questions to the AI assistant in the app and its answers. Section 5 describes how they are processed. We also keep a record of your decisions about AI (sections 5 and 9).

Payments

Your orders and subscriptions, amounts and currency, wallet balance and records of payment disputes. You enter card details on the payment provider side; we do not receive or store full card numbers.

Connected services

The access tokens a connected service issues to us, the permissions you granted, and the ID of your account in that service.

Support

Messages you send to our support chat or by email, their attachments, and the contact details you give us.

Technical data

IP address, device and browser type, app version and server logs. Error reports from the app contain your user ID, IP address, device or browser, the page and the technical details of the error. They go to our own error tracker on our hosting.

We also record what you have connected in the app: the model and name of a paired lactate meter and whether automatic import of its measurements is on; whether Apple Health is connected and whether workout import is on; whether sending workouts to Apple Watch is allowed; and when the app first and last reported this.

Analytics

In the app, Google Analytics and Mixpanel (on EU servers) receive the pages you open, your actions in the app and your user ID with the type of your account (athlete or coach, PRO), but not your name or email. With a payment we keep the Google Analytics visitor ID to know where the purchase came from. On this website, Google Analytics and Microsoft Clarity, which records how you use the pages, run only if you accept analytics cookies. You can withdraw your consent at any time: .

3. Where the data comes from

  • You: when you register, fill in your profile, plan and log workouts, write messages or talk to the AI assistant.
  • Devices and services you connect. We receive data from a service only after you connect it and grant permission, and only the data types you allow:
    • Garmin Connect — we receive activities and daily health data: sleep, heart rate variability, stress, daily summaries, respiration, SpO2, blood pressure, skin temperature and body composition. We send planned workouts to Garmin Connect.
    • Strava — we receive activities.
    • Polar — we receive training sessions, sleep, Nightly Recharge, daily activity and SpO2.
    • Suunto — we receive workouts, sleep, heart rate variability, stress, daily activity and SpO2. We send planned workouts to Suunto as guides.
    • Wahoo — we receive workouts and your Wahoo profile details. We send planned workouts and plans to Wahoo.
    • COROS — we receive activities, sleep, heart rate variability and daily data. We send planned workouts to COROS.
    • Intervals.icu — we receive activities. We send planned workouts as calendar events.
    • Huawei Health — we receive workout records with route, altitude and heart rate; sleep; heart rate variability; daily steps and resting heart rate, including up to 30 days of history before you connect. We send planned workouts to your Huawei watch.
    • Apple Health, through our iOS app — we receive the data types you allow in Apple Health, such as workouts, heart rate, routes and steps. With your permission, our app writes workouts to Apple Health and sends your planned workouts to Apple Watch.
    • Google Calendar — we add your planned workouts to the calendar you choose.
  • A Bluetooth lactate meter you connect in our iOS or Android app or in a browser: lactate measurements.
  • Activity files you upload.
  • Public race results from ITRA and UTMB, if you add a link to your profile there.
  • Your coach: plans, workouts, notes and messages a coach adds for you.

4. How we use data and on what legal basis

Where the EU or UK General Data Protection Regulation (GDPR) applies, we rely on these legal bases:

  • Providing the Service — your account, importing and analyzing workouts and health metrics, building and adapting your plan, sending planned workouts to your devices, and showing your data to the coaches you choose: performance of our contract with you. For health data — also your explicit consent, with the transitional period described under "Health data and your consent" below.
  • Showing the coaches you are connected with that your diary is closed and why ("Health data and your consent" below): our and their legitimate interest in managing their connection with you.
  • AI features — your explicit consent, with the exceptions described in section 5.
  • Payments, invoices and accounting: performance of the contract and our legal obligations.
  • Preventing fraud and abuse: our legitimate interest in protecting the Service and its users. For example, when a payment is disputed, we record the dispute, cancel the related subscription and may flag the account for manual review.
  • Support: performance of the contract and our legitimate interest in answering your requests.
  • Service emails about your account, security and payments: performance of the contract.
  • Marketing emails: only with your consent; every email has an unsubscribe link.
  • Analytics: in the app, our legitimate interest in understanding how the Service is used; on this website, your consent.
  • Security, error monitoring and reliability: our legitimate interest in keeping the Service secure.
  • Complying with the law and defending legal claims: legal obligation and legitimate interest.

We do not sell your personal data. We do not use workout or health data for advertising or marketing, and we do not share it with data brokers.

Health data and your consent

The Service is a training diary, and almost everything in it is health data (section 2). From November 15, 2026 we ask for your explicit consent to it (Article 9(2)(a) GDPR) on a screen that opens after you sign in, before anything else in the app and separately from AI. Nothing is selected in advance, and "Allow" and "Don't allow" are equal choices. We record each decision with its date, the version and language of the text you saw, and the place in the app where you answered.

If you refuse — and, after the transitional period below, if you have not answered — the diary does not work: the app does not open, we do not accept data from your devices or send workouts to them, and your coach, your coach's school and the apps you connected cannot see your diary. Your account stays: you can give consent later, sign out or delete your account.

Your coach sees your decision, but not your diary. While you are connected, your coach's list of athletes shows your name and that you have refused to share your data — or, after the transitional period, that you have not answered yet. We show this so that your coach knows why your diary is closed and can end the connection. Nothing else about you is shown with it, and your coach's school, AI assistants and the apps you connected do not see your decision.

You can withdraw your consent at any time in the settings: turn the switch off and confirm in the window that opens. From then on, we stop accepting and showing your health data and others lose access to it, as if you had refused. Data already stored is not erased by itself: to erase it, delete your account and write to privacy@trainingendurance.com (section 9). Withdrawal does not affect processing that took place before it.

The transitional period: until November 22, 2026, the Service keeps working as before for people who have not answered yet, including those who do not open the app; a refusal applies immediately. From November 22, 2026, no answer counts as a refusal. If we move this date, we will update this section before it.

AI is decided separately. Section 5 says when AI features work with your data; refusing this consent stops them too, with the exceptions described there.

5. AI and your data

Some features of the Service use artificial intelligence (AI) models run by other companies. This section explains when AI works with your data, what it is used for, what data it receives, who processes the data, and how to change your decision.

When AI works with your data

The rule: AI features work with your data only if you have allowed it and have not refused the processing of your health data (section 4). The rest of this section relies on this rule without repeating its exceptions. They are:

  • during the transitional period described under "How we ask", the features, except support and troubleshooting, also work for people who have not answered the question about AI yet, unless they have refused the processing of their health data;
  • a request already running when you withdraw is completed;
  • texts other than calendar entries are translated for a viewer who has allowed AI, whatever their author decided about AI;
  • technical records can reach the AI tools our team uses for troubleshooting.

The last three are described under "Limits you should know about".

What AI is used for

  • the AI assistant in the app: it answers your questions and, to do so, reads the data it needs from your account;
  • translations and parsing: automatic translation of texts such as workout names and descriptions, notes and diary entries; translation on request of a coach's comment or a message in a discussion; and turning a text description of a workout into a structured workout;
  • your coach's work with AI: the coach's assistant in the app and AI assistants the coach connects through our MCP server can read your data that the coach has access to; if your coach works at a school, so can AI assistants that the school's management connects through our MCP server;
  • AI assistants that you connect to your own account through our MCP server;
  • support and troubleshooting, when our team uses AI tools to investigate a problem with your account.

Two more uses are named in the consent text and are not launched yet: an AI analysis of each new workout, and reading each message you send your coach to tell whether it needs an answer. The same consent covers them. We will update this section when they launch.

What data AI can receive

Almost everything you have in the Service: workouts and data from your devices, health and wellness metrics (section 2), your calendar and plans, notes, your profile, and your conversations with the assistant and with your coach. A translation request contains the text being translated. An assistant request contains your question, the earlier conversation and the data the assistant looks up in your account to answer. In support and troubleshooting, the AI tools our team uses can also receive technical records, your payment records and the messages you send to our support (section 2); "Troubleshooting" under "Limits you should know about" says when.

Legal basis

Your explicit consent (Article 6(1)(a) and Article 9(2)(a) GDPR) — one consent for all the uses above. Giving it is optional: everything in the Service that does not use AI works the same without it. For the translation of texts other than calendar entries and for technical records in troubleshooting we rely on the legal bases in section 4, as "Limits you should know about" describes.

How we ask

We ask in a window when you open the app after signing in, after the question about health data (section 4). The same choice appears if you open the assistant without having allowed AI, and when you connect to a coach. Nothing is selected in advance, and "Allow" and "Don't allow" are equal choices. We record each decision with its date, the version and language of the text you saw, and the place in the app where you answered.

The transitional period: we ask for this consent from November 15, 2026. Until November 22, 2026, the uses listed above, except support and troubleshooting, keep working as before for people who have not answered yet; a refusal applies immediately. From November 22, 2026, no answer counts as a refusal. If we move these dates, we will update this section before they come.

How to change your decision

At any time in the settings, under "AI and your data". Withdrawing is as easy as giving consent: turn the switch off and choose "Don't allow" in the window that opens. It applies from the next AI request: under the rule above, your data stops going to the uses listed in this section, and the assistant stops using the earlier conversation, although you still see it on screen. Withdrawal does not affect processing that took place before it.

Without your consent

If you refuse — and, after the transitional period, if you have not answered:

  • the assistant does not work;
  • translations are not shown, and translating on request and parsing a workout description do not work;
  • your coach's assistant and MCP do not see you, and the names of your workouts are not translated for your coach automatically;
  • your own access through MCP does not work;
  • support looks into your Garmin data without AI.

For support the limit is wider than Garmin and has no transitional period: see "Troubleshooting" under "Limits you should know about". You can connect to a coach whatever you answer about AI.

Who processes the data

  • Anthropic — the assistant, translations and parsing of workout descriptions;
  • OpenAI — search in our training methodology for the assistant, and a backup for the assistant, translations and parsing;
  • Google (Gemini API) — a backup for parsing workout descriptions.

A backup is used when the providers before it are unavailable or return no answer. The order for the assistant and translations is Anthropic, then OpenAI; for parsing — Anthropic, then Google, then OpenAI.

These providers act as our processors under data processing agreements: they process the data to provide the service and to detect abuse. None of them uses it to train its models: the terms of Anthropic and of Google's paid Gemini API rule this out, and OpenAI trains on API data only if the customer opts in, and that option is off. How long they keep requests and responses:

  • Anthropic deletes them within 30 days. It can keep a request flagged as violating its policies for up to 2 years and the safety scores of such a request for up to 7 years, and keep data longer to comply with the law;
  • OpenAI keeps its abuse-monitoring logs for up to 30 days, unless the law requires longer or keeping them is reasonably necessary to protect its services or others from harm. When the backup assistant is used, OpenAI also stores its conversation for at least 30 days, and its terms name no upper limit;
  • Google keeps them for 55 days to detect abuse.

These companies are based in the USA and may process data there and in other countries where they or their subprocessors operate; section 8 describes the safeguards for such transfers.

For support and troubleshooting our team uses AI tools from Anthropic on its plan for organizations. The same commercial terms and data processing agreement apply: here too Anthropic acts as our processor and does not train its models on the data. It keeps session data for 30 days; a session we keep in its product stays there until we delete it and is removed within 30 days after that. The exceptions for flagged content and for the law are the same as for Anthropic above.

AI assistants that you, your coach or your school's management connect through our MCP server are not our processors. They receive the data that the person who connected them is allowed to read and handle it under their own terms. The rule above decides whether your data can reach an assistant connected by your coach or your school.

Limits you should know about

  • A request already running when you withdraw is completed; an assistant reply takes no more than 10 minutes.
  • Data already sent to an AI provider or to an AI assistant connected through MCP cannot be recalled: the provider keeps it as described above, and the history of an MCP assistant stays with the person who connected it.
  • Translation for other people. Entries in your calendar, including workouts from your devices, follow the rule above. Other texts — notes, diary, nutrition, goals and tags, messages in discussions, a coach's comments, and templates, library items and plans that are not part of a calendar entry — are translated for a viewer who has allowed AI, whatever their author decided about AI: for example, your coach can see a translation of your note even if you have not allowed AI. We treat this as part of showing your data to the people you chose (section 4).
  • Translations made earlier stay in our cache (section 9) and can be shown again to people who have allowed AI, also after you withdraw your consent to AI; this involves no new AI processing.
  • Troubleshooting. The AI tools our team uses can come across technical records that relate to you — server logs, error reports, account identifiers and settings — whatever you decided about AI. We do this on the legal bases for support and reliability in section 4. Everything else in your account — your workouts, device data and health metrics, whatever service they came from, your profile, notes and diary, plans, payment records, and your messages, including those you send to our support — goes to these tools only under the rule above and without its transitional period: here no answer about AI counts as a refusal from the first day.

6. Who we share data with

  • Coaches and teams you connect with see the data the Service shows to coaches, wherever they are.
  • Connected services. When you send workouts to a connected service, it receives them under its own privacy policy (section 7).
  • AI assistants connected through our MCP server — by you, by your coach or by the management of your coach's school — receive the data that person is allowed to read, under their own privacy policies. Section 5 describes when your data can reach them.
  • Service providers that process data on our behalf under contracts with us:
    • hosting and storage — Google Cloud (Belgium and Germany) and Hetzner (Finland);
    • email delivery — Brevo;
    • internal error alerts — Telegram;
    • maps — CARTO: map tiles load from CARTO directly in your browser, so CARTO sees your IP address and the map area you view;
    • weather — Apple WeatherKit and OpenWeatherMap receive the start location and time of a workout;
    • sign-in — Apple and Google, if you choose to sign in with them;
    • email — Google Workspace;
    • AI processing — Anthropic, OpenAI and Google, as described in section 5;
    • analytics — Google Analytics and Mixpanel.
  • Payment providers. When you pay through Paddle, Paddle sells the subscription to you as merchant of record and processes your payment data as an independent controller under its own privacy policy.
  • Microsoft Clarity. If you accept analytics cookies on this website, Microsoft receives through Clarity how you use the website. Microsoft is not our processor here: it handles this data under its own terms and privacy statement.
  • Our relay in Russia. The relay described in section 8 runs on servers of CLO, a hosting provider in Moscow.
  • The Russian version of the Service. If you choose Russia as the country of payment, you continue in the Russian version of the Service. There, a separate company in Russia holds your account and profile and accepts your payments under its own terms and privacy policy, so we transfer your account and profile data to that company. Your training data and connected services remain with us.
  • Authorities and others, when the law requires it, or to protect the rights, property or safety of our users, the public or us.
  • A successor, if Charges LLC is involved in a merger, acquisition or sale of assets. The successor remains bound by this policy.

7. Connected services

Disconnecting a service

You can disconnect a service at any time in the Training Endurance settings, on the page with your connected services. We then stop importing data from it and stop sending workouts to it. For Garmin, Polar, Strava, Suunto, Wahoo and COROS we also revoke our access on the service side. For Huawei Health, Intervals.icu and Google Calendar, remove our access in that service as well (see below). Data imported before you disconnect stays in your account until you delete it or your account (section 9).

Huawei Health

For data we receive through HUAWEI Health Kit, we are the controller and Huawei acts as a processor. We request only the permissions needed for the features in section 3, and you can grant or withdraw each of them. To withdraw access on the Huawei side: on your phone, Settings > HUAWEI ID > Privacy center > Control account access; or in the Huawei Health app, Me > Privacy management > Data sharing and authorization.

Garmin

Garmin is an independent controller of the data in your Garmin Connect account. When you send planned workouts to Garmin Connect, we transfer to Garmin the workout details — name, date, steps and targets — so that Garmin can deliver them to your device. Garmin processes this data under the Privacy Policy for Garmin Connect and Compatible Garmin Devices. Do not send data to your Garmin Connect account if you are restricted from doing so. You can also remove Training Endurance from the apps connected to your Garmin Connect account in its settings.

Apple Health

We use data from Apple Health only to provide the Service to you and to the coaches you choose. We do not use it for advertising or marketing and do not sell it. AI features process data from Apple Health stored in your account only under the conditions in section 5. You can change what our app reads and writes on your iPhone: Settings > Privacy & Security > Health > Training Endurance.

Google Calendar

Google asks you to grant access to your calendars. We use it only to create, update and delete the workout events we add; we do not read your other events. Our use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. To remove our access, open the third-party connections in your Google Account.

Intervals.icu

To remove our access, use the settings of your Intervals.icu account.

8. International transfers

Our main database and file storage are in the EU (Belgium), logs are stored in Germany, and our servers for background processing are in Finland. Charges LLC is a company in the USA, and some of our service providers process data in the USA and other countries.

If you use the Service from Russia, or if our main address cannot be reached, your connection may go through our relay server in Russia. The connection stays encrypted between your device and our servers in the EU, so the relay cannot read what you send; it sees your IP address, which of our addresses you connect to and how much data passes.

Where GDPR applies, we transfer personal data outside the European Economic Area only on the basis of an adequacy decision of the European Commission (including the EU–US Data Privacy Framework for certified recipients) or the Standard Contractual Clauses, or because it is necessary to perform our contract with you: for a transfer you ask for — such as showing your data to a coach in another country or continuing in the Russian version of the Service — and when your connection goes through our relay in Russia.

9. How long we keep data

We keep your data while your account exists; what stays after you delete your account is described below. Some data has shorter periods:

  • original activity files — 7 days after processing;
  • incoming notifications from connected services — 7 days;
  • server logs — 30 days;
  • AI assistant usage records — 13 months; translation cache — 12 months;
  • a copy of a text waiting for translation — up to 7 days;
  • error tracker backups — 30 days.

We keep the records of your decisions about AI and about health data while your account exists and for 3 years after you delete it.

We keep payment records, including records of payment disputes, for 7 years after the end of the year of the payment: tax and accounting laws require this, and we may need them to defend legal claims. Then we delete them.

When you delete your account, we delete at once your login (your email and password, or sign-in with Apple or Google) and the photos and pictures you uploaded, and we stop all imports from connected services. Your profile, workouts, health data, notes, plans, messages and conversations with the AI assistant are marked deleted and your account disappears from your coaches' lists, but this data stays in our database. We are building its automatic deletion. Until then, write to privacy@trainingendurance.com and we will erase it within one month.

Backups of our databases are kept for up to 30 days, so deleted data disappears from them within that time.

10. Your rights

Depending on where you live, you have the right to:

  • access your data and receive a copy;
  • correct inaccurate data;
  • delete your data;
  • restrict or object to processing, including processing based on our legitimate interests;
  • receive the data you provided in a structured, machine-readable format and transfer it to another service;
  • withdraw your consent at any time; this does not affect processing before the withdrawal;
  • lodge a complaint with a data protection authority: in the EU, in the country where you live or work or where the infringement took place; in the UK, with the Information Commissioner's Office.

Some of this you can do yourself in the app: edit your profile, delete workouts, disconnect services and delete your account. For anything else, write to privacy@trainingendurance.com. We answer within one month; for complex requests we may extend this by two more months and will tell you why. We may ask you to confirm your identity. Exercising your rights will not affect how we treat you.

If you live in a US state with a consumer privacy law, you can exercise the rights that law gives you in the same way.

11. Children

The Service is intended for people aged 16 and over. Some coaches and schools use it with younger athletes. If you are a parent or guardian and want your child's data deleted, write to privacy@trainingendurance.com and we will delete it.

12. Security

We protect your data with technical and organizational measures: encrypted connections (HTTPS), encryption at rest for our main database and file storage, and access to production systems only for the people who need it for their work. We request from connected services only the access the Service needs. No system is completely secure: if a personal data breach puts your rights at risk, we will inform you and the authorities as the law requires.

13. Changes to this policy

We may update this policy. We will post the new version on this page with a new date and, if the changes are significant, notify you by email or in the app before they take effect.

14. Contact us

Questions and requests about your data: privacy@trainingendurance.com. Charges LLC, 16192 Coastal Highway, Lewes, Delaware 19958, USA.

  1. Privacy Policy

Products

  • Platform
  • Calculators

Resources

  • Blog
  • Help

App

  • App Store
  • Google Play
  • Support

Copyright © 2025–2026 Training Endurance. All rights reserved.

  • Privacy Policy
  • Terms of Service
  • Offer Agreement
  • Refund Policy