TrainerPower for Windows and Android

Privacy policy

Last updated 6 November 2026

Who this covers

This policy covers the TrainerPower apps for Windows and Android, published by Tedi, including the version distributed through the Microsoft Store and the Android app downloaded from this website.

What stays on your computer

On Windows, TrainerPower keeps its data on your PC, in two folders:

• C:\Users\<you>\TrainerPower: rider profiles and settings (name, FTP, weight, maximum heart rate), ride history, paired Bluetooth devices, trainer calibration, sign-ins for services you connect, and a log file.
• Documents\TrainerPower: your rides as FIT files, and any problem report you create.

None of it is sent to the developer. Uninstalling the app leaves both folders in place, so a reinstall keeps your history. Delete them to remove everything.

What stays on your phone

On Android, the same data lives in the app's private storage, which other apps can't read, and it is left out of Android's cloud backup. None of it is sent to the developer. Uninstalling the app deletes all of it.

The share card goes into your gallery when you save it, or when you turn on Open Strava to add the card.

Bluetooth devices

The app connects to your smart trainer, power meter and heart-rate strap over Bluetooth to read power, cadence, speed and heart rate, and to set the trainer's resistance. It remembers each device's name and address so it can reconnect next time.

On Android, the app asks for nearby devices and location, because Android requires the location permission to scan for Bluetooth devices. TrainerPower never reads or records where you are.

Services you choose to connect

Each is off until you connect it in Settings, and you can disconnect it there at any time. Once a ride or other data reaches one of these services, that service's own privacy policy applies.

• Garmin ConnectYou sign in with your Garmin email and password. The password goes to Garmin once, to start a session, and is never stored. The session is kept on your device, encrypted by Windows or by Android's keystore. A ride is uploaded when you press Send, or as it finishes if you turn that on. To work out a ride's calories, the app reads your resting-calorie figure from Garmin.
• StravaYou sign in on Strava's own website; TrainerPower never sees your Strava password. The access Strava grants is stored on your device. Finished rides are uploaded if you turn Strava uploads on.
• intervals.icuYou paste an API key, which is stored on your device. The app reads your planned workouts, FTP and power zones, power curve, and profile details (age, height and sex, used only to estimate calories). Finished rides are uploaded if you turn uploads on.

Problem reports

If you create a problem report in Settings, the app saves a zip file with the log, your settings and a list of recent rides. Passwords, tokens and API keys are left out. It goes nowhere unless you send it to someone yourself.

The app's own screens

TrainerPower draws its screens through a small web server that listens only on your own PC (127.0.0.1), so nothing outside your computer can reach it, unless you deliberately start the app with the option that opens it to your home network.

Where the app comes from

If you installed TrainerPower from the Microsoft Store, Microsoft handles the download, installation and updates under the Microsoft Privacy Statement. Microsoft may show the developer aggregated figures, such as install counts and crash reports, through its developer dashboard.

The Android app is a file you download from this website, which is hosted by Cloudflare. Google Play Protect on your phone may check the app when you install it, under Google's own privacy policy.

Changes

If this policy changes, the new version will be posted on this page with a new date.

Contact

Questions about this policy: [email protected].