TriPlan Privacy Policy
How Alexandr Korsak (Bitscorp) collects, uses, and stores data in the TriPlan mobile app (co.bitscorp.triplan).
Privacy Policy
Effective date: 14 November 2026. I take your privacy seriously. This notice explains what TriPlan stores on your device, what (if anything) leaves the device, and how to contact me.
Alexandr Korsak (Bitscorp), a self-employed professional (autónomo) in Spain, operates the mobile application TriPlan (co.bitscorp.triplan). Bitscorp is a trading name, not a registered company. This page applies to TriPlan on iOS and Android. The website https://bitscorp.co has a separate Privacy Policy and Terms and Conditions.
The app
TriPlan is an on-device triathlon training planner. You enter a race distance and date, recent fitness, weekly hours, and rest days. The app builds a periodized swim, bike, and run plan. Logs and readiness check-ins stay on the phone. Strava and calendar export are optional.
Data stored on your device
- Your plan, training logs, readiness check-ins, and settings in local storage on this device.
- If you connect Strava, tokens needed to talk to Strava are stored on the device after the exchange described below.
Data that leaves your device
- Plans and logs are not uploaded to Bitscorp for training analysis. Core planning works fully on the device.
- If you connect Strava, the app sends an authorization code or refresh token to the TriPlan API (a small Python service we operate, when it is deployed) so the Strava client secret does not ship inside the app. The API exchanges or revokes tokens with Strava and returns tokens to the app. Activity writes then go from your phone to Strava with your bearer token. Planned sessions are not posted as completed work you have not done.
- Until that API is configured, Strava connect shows a configuration error and is not used.
- If you export sessions to Calendar, events are written on this device. They are not sent to a Bitscorp server.
- If you send feedback, your email app may include basic device and app version details in a message to alex@bitscorp.co.
- Purchase and subscription status are handled by Apple or Google and RevenueCat, as described below.
Permissions
- Calendar (optional): to export training sessions to the calendar on this device.
You can change or withdraw permissions in the operating system settings.
Sensitive information
Training logs, readiness notes, heart-rate or pace zones, and race dates can be health-related. They stay on your device unless you export them to Calendar or post a session to Strava.
Analytics and crash reporting
TriPlan does not include a third-party analytics or crash-reporting SDK. I do not run Mixpanel, Google Analytics, Firebase, Sentry, or a similar product inside this app. The stores and RevenueCat may keep their own purchase or install records under their policies.
Third parties
I only involve the parties below for the purposes stated. Each has its own privacy policy.
- RevenueCat: To check and restore your Pro entitlement. RevenueCat receives purchase tokens, subscription status, and an anonymous app user identifier. It does not receive the journal, photos, files, or other content you keep in the app.
- Apple: If you buy or manage a subscription or a lifetime purchase on the App Store, Apple processes the payment. We do not receive your full payment card number.
- Google: If you buy or manage a subscription or a lifetime purchase on Google Play, Google processes the payment. We do not receive your full payment number.
- Strava: Optional. If you connect your Strava account, Strava receives the token exchange and any activities you choose to post from TriPlan.
Accounts, servers, and retention
An optional TriPlan API exists only to exchange and revoke Strava tokens (so the client secret is not shipped in the app). Plans, logs, and purchases do not use this server. The API may be undeployed; in that case Strava connect is unavailable and the rest of the app still works.
TriPlan does not require a Bitscorp account. Information stored only on your device remains there until you delete it in the app or uninstall the app. Purchase records are kept by Apple or Google and by RevenueCat for as long as they need them to provide the subscription. If you email me, I keep the message long enough to respond and then delete it when it is no longer needed.
Your rights
Because most TriPlan content never leaves your device, the practical way to access or delete it is in the app, or by uninstalling the app (which removes local data). For any personal data I hold in email, or questions about purchase records, write to alex@bitscorp.co. If you live in the European Economic Area, the United Kingdom, or another region with similar rights, you may also request access, correction, deletion, or a restriction of processing of personal data I hold, and you may lodge a complaint with your local supervisory authority. In Spain that authority is the Agencia Española de Protección de Datos (AEPD).
International processing
I am based in Spain. Apple, Google, and RevenueCat may process purchase data in other countries. Their policies describe those transfers.
Changes to this policy
This Privacy Policy is effective as of 14 November 2026. I may update it from time to time. The current version will always be at https://bitscorp.co/triplan/privacy. Material changes will be reflected on this page, and I may also note them in the app.
Contact
Questions about this policy or about TriPlan: alex@bitscorp.co. There is no telephone contact number. Related pages: TriPlan Terms and Conditions, and the list of Bitscorp app policies.