← Back to TriBuild
Privacy and data handling

Privacy Policy.

Last updated: July 2026

TriBuild is an endurance training app currently in development for triathletes and runners. This Privacy Policy explains how TriBuild intends to handle personal, workout, health-related, and future integration data.

Development status: TriBuild is currently in private development. Some features described here, including Garmin and Apple integrations, are planned or under evaluation and may not be available yet.

1. Who we are

TriBuild is operated by the TriBuild project team. For privacy-related questions, contact: hello@tribuild.app.

Legal or business operator information will be updated before broader public release and before external platform access requests where required.

2. Data we may collect

TriBuild may collect or process the following categories of data:

  • account information, such as email address and user profile data;
  • training plans and scheduled workouts;
  • structured workout data, such as workout blocks, steps, targets, and notes;
  • manual completion data, such as completed, partial, or skipped status;
  • completed workout data, such as sport type, date, duration, distance, pace, power, heart rate, RPE, feeling, and notes;
  • technical data needed to operate, secure, debug, and improve the service;
  • integration data from third-party platforms, only after explicit user authorization.

3. Health and workout data

Workout and health-related data is used to provide training planning, tracking, analysis, and future training recommendation features.

TriBuild does not sell health or workout data. TriBuild does not use health or workout data for advertising.

Planned workout data

Planned sessions, structured workout blocks, templates, calendar dates, and notes.

Completed workout data

Actual duration, distance, heart rate, power, pace, RPE, notes, and completion status.

4. Apple Health and Apple Watch integrations

TriBuild may support Apple Health and Apple Watch integrations in the future. Such integrations will only be used after explicit user authorization and subject to technical feasibility, operating system support, API availability, and App Store requirements.

If Apple Health integration is enabled, TriBuild may request permission to read completed workout data such as workout type, start date, duration, distance, energy, heart rate, or other workout-related samples where available and permitted by the user.

TriBuild may also evaluate Apple Watch workout scheduling or structured workout support where technically available.

5. Garmin integration

TriBuild is preparing Garmin integration for endurance athletes who train with Garmin watches and cycling computers. Garmin integration is subject to Garmin approval, API availability, technical validation, and explicit user consent.

Garmin data TriBuild may process

If a user connects Garmin in the future, TriBuild may process Garmin activity or workout data such as:

  • Garmin activity ID or workout identifier;
  • sport or activity type;
  • start date and time;
  • duration and moving time;
  • distance;
  • pace or speed;
  • heart rate;
  • power;
  • cadence;
  • elevation;
  • calories;
  • lap or split summaries where available;
  • sync or import timestamps.

How TriBuild intends to use Garmin data

TriBuild intends to use Garmin data only to provide user-facing training functionality.

  • send structured planned workouts to Garmin Connect where supported;
  • allow users to sync planned workouts to compatible Garmin devices where supported;
  • import completed Garmin activities after user authorization;
  • match completed activities to planned TriBuild workouts;
  • show training history;
  • support planned-vs-completed training review;
  • support future analysis and training adjustment features.

Garmin data restrictions

  • TriBuild does not sell Garmin data.
  • TriBuild does not use Garmin data for advertising.
  • TriBuild does not request Garmin data unless the user explicitly authorizes the integration.
  • TriBuild will not store Garmin client secrets directly inside the iOS app.
  • Users should be able to disconnect Garmin integration where supported.

6. Purpose of processing

Data may be processed to:

  • provide core app functionality;
  • create, store, and display training plans and workouts;
  • store and display manually entered completed workout data;
  • support future platform integrations after user authorization;
  • match completed activities to planned workouts;
  • analyze training history and progress;
  • support beta testing and product improvement;
  • maintain service security and reliability;
  • respond to user requests and support inquiries.

7. Data storage and service providers

TriBuild may use third-party infrastructure providers to store and process app data. Data storage and processing will be configured with appropriate technical and organizational safeguards.

Third-party infrastructure providers are used only as necessary to operate the app and related services. TriBuild does not sell user data to advertisers.

8. User consent and permissions

Integrations with Apple Health, Garmin, or similar platforms will require explicit user authorization. Users can choose whether to grant or deny such permissions.

If a user denies access to an integration, TriBuild may still provide manual planning and manual completion features.

9. User rights

Depending on applicable law, users may have the right to request access, correction, deletion, restriction of processing, data portability, or withdrawal of consent.

Requests can be sent to: hello@tribuild.app.

10. Data deletion

Users may request deletion of their account and related data by contacting hello@tribuild.app.

If third-party integrations are supported in the future, users should also be able to disconnect those integrations. Additional platform-specific deletion or disconnect steps may apply.

11. Security

TriBuild aims to protect user data through appropriate technical and organizational measures. Access to user data should be scoped to the authenticated user.

Integration credentials and tokens should be handled securely by backend services where required, and should not be embedded directly in the iOS application.

12. Children

TriBuild is not intended for children. If future availability or App Store settings require more specific age restrictions, this policy will be updated accordingly.

13. Medical and coaching disclaimer

TriBuild is a training planning and tracking product. It does not provide medical advice. Users should consult qualified professionals before making health, medical, or training decisions where appropriate.

14. Changes to this policy

This Privacy Policy may be updated as TriBuild develops and new features or integrations are added. The “Last updated” date will be changed when material updates are made.

15. Contact

For questions about this Privacy Policy or data handling, contact:

hello@tribuild.app