GPX Bridge ("the app", "we") converts shared Google Maps directions into GPX files for use on Garmin cycling computers. We designed the app to do its job without collecting personal information about you. This policy explains exactly what data is involved when you use it.
1. Who we are
GPX Bridge is published by an independent developer based in Canada. For privacy questions, contact [email protected].
2. Data we do not collect
- We do not require an account, sign-in, or profile.
- We do not require your name, email, phone number, or address to use the app. (If you choose to give us your email — including via the optional field in the in-app “Report a failed link” feature in Section 3c — we receive that email so we can reply.)
- We do not track your location.
- We do not sell personal information.
3. Data the app handles
3a. Map links you share into the app
When you share a Google Maps or Ride with GPS link into GPX Bridge, the app fetches that URL so it can extract the route and convert it into a GPX file. Requests go to:
maps.google.com/maps.app.goo.gl— to resolve the shared route.ridewithgps.com— to fetch route data when you share a Ride with GPS link.api.gpxbridge.com— our backend service that performs the conversion. The shared URL and resulting route geometry are processed in memory to generate your GPX file and are not associated with you or stored in a user-identifiable database. The backend runs on Google Cloud, which automatically captures request logs (including client IP and the requested URL) for operational and abuse-prevention purposes; these logs are retained for up to 30 days and then automatically deleted.
The resulting GPX file is saved on your device and shared only via the iOS share sheet at your direction.
3b. Settings stored on your device
The app stores a few small preferences locally using the operating system's standard preferences storage — for example your light/dark theme choice and a timestamp used to space out ads. This data never leaves your device.
3c. Reporting a failed link
If a Google Maps or Ride with GPS link fails to convert, the app offers to send the link to our support team. Tapping “Send to support” emails us the link you were trying to convert (which may include the start point, destination, and waypoints of your route), the error type, and your platform and app version. The email is delivered through Web3Forms, a form-to-email service (see Section 4). You may optionally add your email address so we can reply; it is used solely as the reply-to for your report and is never used to track or identify you. Nothing is sent unless you tap “Send to support”, and none of this is sent to Analytics. We use these reports only to diagnose and fix link-conversion problems.
4. Third-party services
GPX Bridge uses the following third-party SDKs. Each of these has its own privacy policy that governs the data they collect.
Google AdMob (advertising)
We show ads in the app via Google AdMob. AdMob may collect information such as your device's advertising identifier (only if you grant tracking permission — see Section 5), IP address, coarse location derived from IP, device type, and basic usage signals needed to deliver and measure ads. We do not share any personal information with AdMob ourselves.
Google's policy: policies.google.com/privacy.
Firebase App Check (abuse prevention)
We use Firebase App Check with Apple's App Attest to verify that requests to our backend come from a genuine, untampered copy of the app. App Check uses a device-level attestation token; it does not identify you and does not access your contacts, photos, location, or other personal data.
Google's policy: firebase.google.com/support/privacy.
Firebase Analytics (usage measurement)
We use Firebase Analytics to understand how the app is used in aggregate — for example how often a conversion is started, succeeds, or fails, and which share options are used. We log event names and coarse parameters (such as an error type); we never send the contents of your links or routes to Analytics. Firebase Analytics may process device and app information and an app-instance identifier as described in Google's policy.
Google's policy: firebase.google.com/support/privacy.
Firebase Crashlytics (crash reporting)
We use Firebase Crashlytics to receive automatic reports when the app crashes, so we can fix stability problems. A crash report includes diagnostic information such as the device model, operating-system version, app version, and a stack trace. We do not attach your links, routes, or other personal content to crash reports.
Google's policy: firebase.google.com/support/privacy.
Web3Forms (support email delivery)
When you tap “Send to support” to report a failed link (Section 3c), or use the contact form on our support page, your message is delivered to our support inbox through Web3Forms, a form-to-email service. The information you submit — such as the failed link, error type, app version, and any email address you choose to include — passes through Web3Forms only to deliver that email.
Web3Forms's policy: web3forms.com/privacy-policy.
5. App Tracking Transparency (iOS)
On first launch, iOS will ask whether you allow GPX Bridge to track your activity across apps and websites. Your choice only affects ad personalisation:
- Allow: ads may be personalised using your device's advertising identifier.
- Ask App Not to Track: ads are still shown but are not personalised, and your advertising identifier is not used.
The app works the same either way. You can change this choice anytime in Settings → Privacy & Security → Tracking.
6. Children's privacy
GPX Bridge is not directed to children under 13. We do not knowingly collect personal information from children. If you believe a child has provided personal information through one of the third-party services listed above, please contact us and we will work with the relevant provider to address it.
7. Security
All network requests from the app use HTTPS. Our backend is hosted on Google Cloud and is protected by App Check to reject requests from unverified clients.
8. Your rights
Because the app does not maintain accounts or store personal information about you on our servers, there is generally no personal data for us to access, correct, or delete on request. For data held by the third parties listed in Section 4, please use their respective controls (for example, your device's advertising-identifier reset and tracking settings).
9. Changes to this policy
If we make material changes to this policy we will update the "Last updated" date above and, where appropriate, surface a notice in the app. Continued use of the app after an update constitutes acceptance of the revised policy.
10. Contact
Questions or concerns? Email [email protected].