Skip to content

ATV Companion Privacy Policy

Last updated: September 29, 2026

This Privacy Policy explains what information ATV Companion (the "App" or "Service") — provided by Lumagate Inc. ("Lumagate", "we", "us") — collects, how we use it, and which third parties we rely on. It applies to the App as a native iOS and Android application and to the ATV Companion web companion.

ATV Companion records off-road rides and shows trail maps. Recording a ride means recording precise location, so this policy describes location data in detail, including the few places where information you create is deliberately visible to others. If you have questions about this policy or your data, contact us at support@lumagate.us.

1. You Can Use the App Without an Account

Ride recording, offline maps, trail browsing, and navigation all work while signed out. Used that way, your rides and waypoints stay on your device and are never sent to us. Signing in is optional and exists so your data can follow you to another device.

2. Identity and Authentication

If you choose to sign in, you do so through Firebase Authentication using Apple, Google, or Microsoft. We never see or store your password. From your chosen sign-in provider we receive your email address, display name, profile photo URL, and a stable user identifier that we use to recognize your account. If you sign in with Apple and choose to hide your email, we receive Apple's private relay address instead of your real address. Firebase Authentication handles those sign-in details. Your email and provider photo URL are not part of the synced rider profile; if you use the provider photo as your avatar, a copy may be stored with that profile.

3. Location Data

The App collects precise location. This is the core function of a ride recorder, and it is used for the following purposes only:

  • Recording the GPS track, distance, speed, and elevation of a ride you have started
  • Saving the GPS route of a past workout that you explicitly choose to import from Apple Health or Health Connect
  • Showing your position on the map and navigating a route you have chosen
  • Sharing your live position with a group ride you have joined, for the duration of that ride
  • Attaching a location to a waypoint, photo, or trail condition report that you create

Location is collected from the device in the background only while a ride or navigation session you started is active, and the App shows an ongoing notification while it is doing so. Past workout routes are read only when you open the import picker and choose a workout. We do not track your location when you are not recording or navigating, and we do not use location for advertising or profiling.

Privacy zones. You can define areas — typically around your home or trailer — whose start and end points are hidden from rides you share with others.

4. What We Store When You Are Signed In

When you are signed in, your app data is synced through a Cloudflare Worker to Cloudflare's database and object storage (D1 and R2). Cloudflare Durable Objects support live group and trip-sharing features. Firebase Authentication handles sign-in. The synced data includes:

  • Your rider profile (display name, bio, and avatar if one is set) and app preferences
  • Your rides, including the recorded or imported GPS track, heart-rate samples and active-energy total when available, and other ride samples, plus routes and waypoints you create or import
  • Photos you attach to waypoints, activities, or trail condition reports
  • Social content you create if you use those features: your public profile, activities (each with a visibility setting you choose), crews, follows, kudos, and comments

5. Information That Is Visible to Others

Your rides, routes, and waypoints are private to your account. Several other things are deliberately not, and it is important that you understand each before you use them:

  • Trail condition reports are public. A report you submit — its kind, note, location, and any photo — can be read by anyone using the App, including people who are not signed in. Do not include anything in a report that you would not post publicly.
  • Emergency beacons are public by design. If you trigger an emergency beacon, it is readable without sign-in so that nearby riders and responders can see it and help. This is a deliberate safety choice.
  • Trip share links grant access to anyone holding them. When you share a trip, possession of the link is the permission. Anyone you send it to — or anyone they forward it to — can view that trip.
  • Group rides share your live position with the group. While you are in a group ride, members of that group can see where you are. Nearby group rides additionally broadcast your presence directly between devices on the same platform, over Bluetooth and Wi-Fi, without going through our servers.
  • Your rider profile is public. If you sign in, your profile — display name, bio, and any avatar — can be read by anyone who has your profile link. It is your public identity in crews, activities, and shared rides. The list of riders is never browsable, so you are not enumerable.
  • Activities you post carry a visibility you choose. An activity set to public or unlisted can be read by others, and so can the kudos and comments on it. An activity you keep private is not. Kudos and comments you leave on another rider's activity are visible to whoever can see that activity.

Crews are visible to signed-in riders, and who you follow is visible to signed-in riders. Everything else you create — your rides, routes, waypoints, and offline maps — stays private to your account unless you choose to share it.

6. Health and Fitness Integrations

These integrations are optional. Updated versions of ATV Companion ask you to expressly consent to each use before reading workout history, collecting ride heart-rate or active-energy data, or exporting finished rides. Apple Health or Health Connect asks for device permission separately. An earlier device permission does not carry forward as an in-app consent choice when you update. Earlier app versions may have asked only for device permission. You can decline the new choices and still record rides, use maps, and navigate. For health-data processing enabled by these express choices, our legal basis is your consent under GDPR Article 6(1)(a) and your explicit consent under Article 9(2)(a).

With your permission, the App writes rides you finish to Apple Health on iOS or Health Connect on Android as workouts with distance and route. During a ride you start, the iOS App can also read Apple Watch heart rate and active energy if you grant access. Heart-rate samples and the active-energy total are saved with the ride on your device and, if you sign in, synced to your private account with that ride.

If you open the import picker, the App reads workout sessions and available GPS routes from Apple Health or Health Connect so you can choose individual activities to save as private rides, routes, or both. It reads the workout type or title and time; a selected workout's GPS route supplies its track and route-derived distance. On Android, access to older Health Connect sessions needs the separate history permission, and another app's route may require consent for that specific activity. The App does not bulk-import workouts or read unrelated Health Connect data such as steps or medical records.

Imported rides and routes stay on your device while signed out. If you sign in, they sync to your private account as described in Section 4, including any imported GPS track. They are not posted publicly unless you separately choose to share them. Sharing an activity or a live trip does not expose heart-rate samples or active-energy totals; those remain in your private ride record. You can revoke health permissions in your device settings. In updated app versions, you can also withdraw each health-data choice in the App: withdrawing workout browsing stops future reads, withdrawing ride metrics stops new heart-rate and energy reads and removes those metrics from saved rides, and withdrawing workout export stops future writes. An activity you deliberately imported remains in your saved rides or routes until you delete that item in the App; deleting it withdraws your choice to retain it. Revoking device permission alone does not erase items already saved.

7. What We Do Not Do

ATV Companion contains no advertising, no analytics SDK, and no third-party crash or behaviour tracking. We do not sell or rent your personal information, we do not share it with data brokers, and we do not build advertising profiles from your rides or location.

8. Third Parties

We rely on a small number of processors and data sources:

  • Google Firebase — authentication for signed-in accounts
  • Cloudflare — the App's API, database, object storage, and live group and trip-sharing services
  • Apple MapKit and Google Maps — base map rendering on their respective platforms
  • OpenStreetMap (Overpass API) — public trail geometry, queried for the area you are viewing
  • Open-Meteo — weather for the area you are viewing
  • Public government open-data trail sources, each credited in the App with its own attribution

Map, trail, and weather requests necessarily reveal the approximate area you are looking at to the provider serving it. We do not send your account identity with those requests.

9. Where Your Data Is Stored

Our production Cloudflare database and object-storage bucket are currently placed in eastern North America; this does not guarantee storage or processing within a particular country. Live group and trip-sharing positions are handled by Cloudflare Durable Objects, whose locations are not restricted to that region. Firebase Authentication separately handles sign-in data. If you would prefer your ride data not to leave your device, use the App signed out — recording, offline maps, trail browsing, and navigation all work without an account, though sync, group rides, and social features necessarily do not.

10. How We Protect Your Data

Data is transmitted over encrypted connections, and Cloudflare encrypts D1, R2, and Durable Object data at rest. The App's API verifies your Firebase sign-in token and enforces account-scoped access to private rides, routes, waypoints, and preferences. Your rider profile and the other shared surfaces described in Section 5 are readable by design; the API enforces their visibility separately.

11. Data Retention

We keep your synced data for as long as your account exists. When you delete a ride, route, or waypoint, it is removed from your other devices and the record of that deletion is cleared after 30 days. Content you deleted while signed out never reaches us at all.

Publicly visible content you create — trail condition reports and emergency beacons — is retained until you delete it or delete your account. We do not expire it on a timer, because a trail hazard stays useful to other riders until someone reports it cleared. You can delete a report you submitted at any time, and deleting your account removes them as described below.

12. Deleting Your Account

You can delete your account from within the App. Deletion is thorough, and it explicitly includes the public content described in Section 5. It removes:

  • Your private data — rides, routes, waypoints, and preferences
  • Your public profile and your follow relationships
  • The trail condition reports and emergency beacons you submitted
  • Activities and crews you own, and any ride groups you hosted
  • Kudos, comments, and flags you left on other riders' content
  • Your stored files — ride tracks, profile media, activity media, and condition photos

The authentication account itself is deleted last. Deletion is permanent and cannot be undone. Note that a trip you shared by link, or a position another rider saw during a group ride, cannot be recalled from anyone who already had it. You may also request deletion by contacting support@lumagate.us.

13. Your Privacy Rights

Depending on where you live, you may have the right to access, correct, export, or delete the personal information we hold about you, and to withdraw consent. To exercise any of these rights, contact support@lumagate.us. Canadian residents may also contact us regarding rights under PIPEDA and, in Quebec, Law 25; see the storage locations described in Section 9. If you are in the European Economic Area, the United Kingdom, or Switzerland, a detailed explanation of our processing and how to submit a request is on Your GDPR Rights.

14. Trail Data Is Not Legal Advice

The App colours trails by access type using public government and OpenStreetMap data, and its routing avoids trails marked closed, impassable, or non-motorized. This information can be incomplete, out of date, or wrong. It is not a determination of what is legal. Always follow current local rules, posted signage, and closures. You are responsible for where you ride.

15. Children's Privacy

The Service is intended for off-road riders and is not directed to children under the age of 13. We do not knowingly collect personal information from children under 13. If you believe a child has provided us with personal information, please contact us at support@lumagate.us and we will take prompt steps to delete it.

16. International Users

Our service providers may process your information in the United States or other countries. Where required, cross-border transfers are covered by the EU-US Data Privacy Framework where applicable, Standard Contractual Clauses, or equivalent safeguards provided by the processor.

17. Changes to This Privacy Policy

We may update this Privacy Policy from time to time. Any changes will be posted on this page with a revised "Last updated" date, and material changes will be communicated through the Service where appropriate.

18. Contact Us

If you have any questions or concerns about this Privacy Policy or how Lumagate handles your information, please contact us at support@lumagate.us.