support@trackitmx.com
Use this for beta help, bug reports, ride review questions, and follow-up after a real ride.
TrackItMX
Support
Email support
Support
Use this page for beta install help, bug reports, spectator link issues, troubleshooting, privacy request paths, and feedback from real rides.
Use this inbox for support, beta feedback, privacy questions, and ride issue follow-up.
Install the current iPhone beta directly through Apple TestFlight.
Shared room links can open on the web so friends, family, or the crew can follow without the app.
Contact
The fastest way to get useful help is to send the right context the first time. Start with support for install help, ride recording issues, navigation questions, or bug follow-up. Use the privacy page when the question is specifically about data use, access, correction, or deletion.
Use this for beta help, bug reports, ride review questions, and follow-up after a real ride.
Install the latest iPhone beta through TestFlight before sending ride feedback or reproduction steps.
For access, correction, or deletion questions, use the privacy page or email support with that request clearly labeled.
Bug report checklist
Real feedback helps
The best reports come from real conditions: low service, a watch connection that felt weird, a save that did not look right, a room that stopped feeling live, or a navigation handoff that made no sense in the truck.
Email supportSupport FAQ
TrackItMX is centered on iPhone today, with Apple Watch companion behavior and CarPlay navigation in active beta work. Android is planned after the iPhone beta foundation is stable enough to expand well.
Core navigation and ride recording flows are being built with low-service riding in mind. Cloud-backed features like live group rooms, sharing, backup, restore, and some syncing still need network access.
Yes. Shared spectator links can open on the web, so a non-iPhone user can still watch the live map and room presence from the browser when the room is active and connected.
Include the room code if you have it, the device and browser you were using, whether the issue was a blank map, stale riders, or a bad link handoff, and a screenshot if it helps.
Tell us whether the ride was phone-only or watch-linked, whether the app went to the background, what trail or route context mattered, and what you expected to happen instead of what actually did.
Use the privacy page or email support@trackitmx.com and clearly label the request as privacy, access, correction, or deletion.
Troubleshooting
Confirm that iPhone location permissions are enabled, let the first fix settle before starting a route, and retry after the device has a better location lock if the first read looked weak.
Note whether the session was phone-only or watch-linked, whether the app went to the background, and whether the session was paused, interrupted, or restored.
Check that the watch is paired, the watch app is installed, and the phone stays nearby long enough for the bridge to settle if you are testing watch-linked ride or live behavior.
Group Ride depends on permissions and connectivity. If the live source was watch-led, temporarily keeping the phone nearby may help while the bridge refreshes and the room catches up.
Reload the page once, confirm the room code is correct, and note the browser and device you were using if riders or the map still do not look right.
Re-enter the recovery details carefully, make sure the device has network access, and mention the restore flow explicitly when you email support if it still fails.
Start on the privacy page or email support@trackitmx.com and include enough device or ride context for us to identify the request safely.
TrackItMX support is for product help, not emergency response. If you have a real-world emergency, use local emergency services.
Support contact
Email support@trackitmx.com with the device, OS version, feature area, and what happened.
Email supportPrivacy and data
Use the privacy page for location data, ride telemetry, group ride presence, optional health signals, analytics context, and request guidance.
Open privacy policy