ATV Companion Privacy Policy
Last updated: September 10, 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.
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
- 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 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. 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 data is synced to Google Firebase (Cloud Firestore and Cloud Storage). This includes:
- Your profile (the display name, email, and photo URL provided by your sign-in provider) and your app preferences
- Your rides, including the recorded GPS track and per-point samples, plus routes and waypoints you create
- 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 and photo — 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
If you grant permission, the App writes finished rides to Apple Health on iOS or Health Connect on Android as a workout, with distance and route. This is a one-way write: the App does not read your health data, and these integrations are optional.
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, database, file storage, and server functions for signed-in accounts
- 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
Signed-in data is stored in Google Cloud's United States multi-region. This applies to all riders, including riders in Canada: if you sign in, your rides and location history are processed and stored in the United States. 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 stored by Google Firebase with encryption at rest. Access to your private data — your rides, routes, waypoints, and preferences — is enforced by server-side security rules tied to your account, so another rider cannot read it. Your rider profile and the other shared surfaces described in Section 5 are readable by design, and those rules enforce that visibility too rather than hiding it.
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; note the United States storage location 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 are located primarily in the United States, and your information may be processed there. Where required, these transfers are covered by the EU-US Data Privacy Framework, Standard Contractual Clauses, or equivalent safeguards provided by each 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.