RoutePathIQ · Privacy · Terms · Support
What RoutePathIQ collects, why, and who it's shared with — in plain terms first, then in full.
At a glance
RoutePathIQ is made by Snare Intelligence Labs, LLC. This policy covers the RoutePathIQ app on iOS and Android — what it collects, how it's used, and your choices.
RoutePathIQ requests your device location to center the map on where you are, use it as a starting point for route searches, and sort suggested roads by distance. Location is used in two ways. It is sent to our routing provider, HERE Technologies, as part of each route, traffic, and weather request — that's how those results get computed — and those requests pass through RoutePathIQ's own server, which adds our access key and forwards them. It is also sent to RoutePathIQ's server (rounded to a few decimal places) when you open Cruise Mode, so the server can pick the scenic drives near you. Cruise Mode also plans drives that start and end where you are: to do that, the app sends points around your starting location to HERE to find towns along the way (a place search) and to route the drives. Our server does not store these locations or the provider's answers: it forwards each request to the provider and returns the answer to the app that asked. Your most recent location fix is also cached locally on your device (see 2.4) so the app starts up faster. While the map screens are open, the app also reads your phone's speed from its GPS to tell whether you are moving; if you are, it asks you to pull over or confirm you are a passenger before you report or update a road hazard. That speed is used on your device only and is not stored or sent anywhere.
When you report a road hazard, you can optionally attach a photo from your photo library. That photo is uploaded and stored so other drivers can see it alongside the report. If you don't attach one, no photo data is collected.
The hazard type, any note you write, the coordinates, and a timestamp are stored so the report can be shown to other drivers on the map, and so other drivers can confirm ("still there") or dismiss ("gone") it. This content is not tied to a personal identity — RoutePathIQ doesn't have user accounts, so there's no name, email, or login associated with a report. Other drivers can report a hazard report to us, or block the anonymous device that sent it; reported content is reviewed and removed if it breaks our Terms of Use. If you report a hazard when your phone has no signal, the report (and its photo, if any) is kept on your phone and sent automatically when you're back online; a report that can't be sent within 6 hours is discarded from your phone, because it would no longer be current.
Your last known location (for a faster app start), your recent destination searches, your Cruise Mode curviness setting, the roads you've rated, your usage-sharing choice, and a random anonymous ID (see 2.5) are saved locally on your device using standard app storage. So are the things that make the app work with no signal: drives you save (the road, its map line, the score it had when you saved it, and the hazard reports along it at the time), the last list of drives Cruise Mode showed you, and any hazard reports waiting for a signal (2.3). A planned drive that starts where you are includes that starting point. None of these is transmitted to us or to anyone else, except the anonymous ID, which is sent with usage sharing (2.5) if you opt in and with safety confirmations (2.6), and waiting hazard reports, which are sent as described in 2.3.
The first time you open the app we ask whether you'd like to share anonymous usage to help tune route scoring for your part of the country. If you say no, nothing in this section is collected and nothing is queued. If you say yes, the app sends only the following:
Each event carries the app version, your device's platform (iOS or Android), a random anonymous ID generated on your device (it is not your advertising ID, is not linked to your name, email or phone, and changes if you reinstall the app), and your approximate area — your location rounded to a grid roughly 17 × 21 miles wide, never a coordinate or address. We do not collect your name, email, destination searches, addresses, exact location, or where you actually drive, and we do not store IP addresses with these events. Our server accepts only this fixed set of fields and discards anything else.
We use these events to see how roads are chosen and rated in different regions and to improve the scoring. We do not use them for advertising and do not share them with anyone.
Reporting or updating a road hazard is meant for when you're stopped, or when a passenger is using the phone. While a map screen is open, the app reads your phone's speed from its GPS, on the device. If you're moving — or the app can't tell — it stops you before you report or update a hazard and asks you to pull over or confirm you're a passenger. If you confirm, the app sends us a short record of that answer: the time, whether the phone was moving or its speed couldn't be read, your answer, your speed in whole miles per hour, the version of the Terms you accepted, the app version and platform, and your random anonymous ID. It contains no name, email, location, address or free text, and we do not store your IP address with it.
This record is kept whether or not you opt in to anonymous usage sharing. It is kept for safety and legal purposes — to show that drivers were warned and responded — and not for advertising or analytics. We don't share it with anyone, except where the law requires it or to establish or defend a legal claim. Because it must remain a reliable record, deleting the app or its data from your phone does not remove it from our server.
Like any app that makes network requests, connecting to our service providers below exposes ordinary technical data (such as IP address) to them as an unavoidable part of how the internet works. We don't separately collect or log this ourselves.
You can export a drive as a GPX or JSON file. The file is created on your phone and contains the drive's name, description, length and its start, via and end points (for a drive planned from where you are, that includes your starting point). It goes only where you send it, using your phone's share sheet; we don't receive a copy.
We share information only with the service providers that make the app's features work — never for advertising, and never sold to data brokers.
| Provider | What they receive | Why |
|---|---|---|
| HERE Technologies | Location / search coordinates, including points around your starting location when Cruise Mode plans drives from where you are | Routing, live traffic, weather, geocoding, search. The HERE privacy policy and HERE end user terms apply to what HERE receives |
| Supabase | Hazard reports (type, note, photo, coordinates, timestamp) | Storing and serving crowdsourced hazard data to other drivers |
| Hetzner (our server host) | Requests the app makes to RoutePathIQ's own server: nearby-road lookups, forwarded provider requests, and — only if you opt in — anonymous usage events | Running RoutePathIQ's server; we operate it, and Hetzner provides the hardware |
| Colorado DOT (CDOT) | Nothing — we only read their public construction-zone feed | Showing official road-work data on the map |
Hazard reports remain visible while the community treats them as current — confirmed by other drivers marking them "still there," and removed when marked "gone" or once they age past the point of being useful. Anonymous usage events (2.5) are kept for up to 24 months and are then deleted or reduced to totals that can't be traced to an install. Safety confirmations (2.6) are kept for up to three years from the date of the answer and are then deleted. Locally-stored data (2.4) stays on your device until you remove it (for example, removing a saved drive), clear the app's storage or uninstall it, except that route lines and times from HERE in saved drives and in the offline list are deleted from your phone after 30 days unless refreshed, and waiting hazard reports are discarded after 6 hours.
RoutePathIQ is not directed at children under 13, and we don't knowingly collect information from them. If you believe a child has used the app and shared data with us, contact us (below) and we will delete it.
Data in transit to our service providers is encrypted (HTTPS/TLS). No method of transmission or storage is 100% secure, but we don't take that as license to be careless with it.
If this policy changes, we'll update the effective date at the top of this page. Continuing to use RoutePathIQ after a change means you accept the updated policy.
Questions, or a data request under section 6: privacy@routepathiq.com