TrackItMX privacy, in plain language.

Built to make ride features work.

TrackItMX is built to help riders get to the trail, record rides, review sessions, keep setup context, and use online features like Group Ride rooms, spectator links, unlisted shared ride links, backup, and restore when those features are turned on.

Location powers navigation, recording, and live rider visibility.

TrackItMX may use location data for trail lookup, route guidance, ride recording, map behavior, Group Ride visibility, spectator links, and other location-aware ride features when you grant the needed permissions.

You can explore another area without sharing your current location. Searching for a town or address uses Apple's map search service and sends that search request to Apple. Included trail geometry is stored on your device; map imagery and online place search may still require a connection.

Saved rides can include more than a line on a map.

Depending on the feature and permissions you use, TrackItMX may handle timestamps, distance, speed, route traces, device motion signals, ride events, setup context, and other saved ride details needed to reopen, review, compare, share, or restore a session.

Live rooms depend on shared room data and rider locations.

When you use Group Ride, TrackItMX may handle room identifiers, rider aliases, room membership, shared locations, shared room codes, browser spectator visibility, connection recovery details, and related room data needed to keep the crew connected.

Optional, permission-based, and not required for the core app.

If you enable supported Apple Watch or HealthKit features, TrackItMX may read limited health-related signals like heart rate, activity context, or active energy. If you do not grant those permissions, the app should not have that access.

Some data helps reliability and support.

TrackItMX may collect app reliability data tied to crashes, performance, and feature behavior. Support emails or messages you send are used to answer you and follow up on your request.

Apple, Firebase, and OpenAI support specific features.

Firebase services may be used where applicable for authentication, online ride features, live room data, sharing, backup, restore, or analytics. Apple platform services may be used where applicable for maps, routing, system integrations, and device-level permissions. HealthKit applies where riders choose to connect it. Optional online Coach and Mechanic requests use OpenAI, as described below.

Shared ride features are visible in the context you choose.

If you use public sharing, spectator links, live room features, or public trail-sharing surfaces, selected ride details, aliases, route previews, messages, selected metrics, or live locations may be visible to other riders or spectators in that feature context.

You choose whether Coach and Mechanic use online AI.

When online AI is available, you can enable it in Settings → AI Privacy and Access. With your consent, TrackItMX sends your question, recent conversation, and relevant rider, garage, and ride context to OpenAI through TrackItMX's service. Ride context can include GPS locations and heart-rate data when available. Web searches may use details needed to answer your question.

TrackItMX does not keep a separate chat log on its AI gateway. OpenAI states that API content is not used for model training by default. OpenAI may retain content for abuse monitoring, generally for up to 30 days, with exceptions for legal or safety needs; other temporary processing and caching may apply. See OpenAI's data controls for details.

You can turn online AI off in AI Privacy and Access to stop future requests. Turning it off does not erase requests already processed or remove local conversation history or account backups.

Account backups can include your full riding library.

If you use account backup, data sent to Firebase can include recorded rides and GPS samples, saved tracks and trails, garage and rider setup, app settings, Group Ride history, and assistant memory. Ride data can include optional health signals recorded with your permission. Backups are associated with your account so you can restore them after signing in.

Local storage and account backups are separate. Removing the app or a local copy does not by itself prove that a cloud copy has been removed. Contact us if you need help accessing or deleting account data.

Anyone with the link can view and replay the shared ride.

Creating an unlisted ride link uploads the selected route, recorded timing when available, lap intervals, selected metrics, and highlights to TrackItMX's sharing service. The link is not posted to a public board, but anyone who receives it can open it and forward it to someone else until it expires or is revoked.

Shared rides are snapshots. Later edits to the ride on your device do not automatically change an existing link. Revoking a link stops future access through the service; it cannot recall screenshots or copies someone already saved.

Retention depends on the feature you used.

Some ride or setup data may remain on-device until you remove it or delete the app. Online data may remain long enough to support the feature, restore behavior, abuse prevention, account protection, or fixing product problems.