Privacy, in plain English.

Your location

TrafficCue asks for your device location only when you choose to use your current location, or when permission was already granted. Your coordinates are sent to our same-origin service only to search places and calculate the route you requested.

Traffic and place data

Search text and selected-place details are sent from our Cloudflare service to TomTom for place search and geocoding. Route coordinates are sent from our Cloudflare service to Google Maps Platform Routes API to obtain current and predicted driving-time estimates. TrafficCue does not send your name, email address, or a TrafficCue account identifier because the app has no account system.

Caching and rechecks

TomTom place-search and geocoding results may be cached temporarily at the network edge to reduce repeated requests. Google Maps route results are not stored in TrafficCue's Cloudflare cache. If TrafficCue recommends waiting, the current trip coordinates, destination label, departure window and recheck time may be saved only in your browser so you can recheck that cue later. This local recheck is not synced to an account or stored in a TrafficCue trip-history database.

Sharing

Share cards deliberately omit your exact origin and destination. The image is created in your browser and can show the city and time-saving insight. You decide whether to share or save it.

Important journeys

Traffic predictions can change. TrafficCue is a decision aid, not a guarantee of arrival time. Always keep a safety buffer for flights, medical appointments, exams, and other time-critical trips.

Traffic and route estimates are provided using Google Maps Platform. Place search and geocoding use TomTom and OpenStreetMap data. Use of Google Maps Platform is subject to the Google Maps/Google Earth Additional Terms of Service and Google Privacy Policy.

Google Maps · Places © TomTom, © OpenStreetMap.