Timeline JSON files are read in your browser. The website does not upload the source file, coordinates, selected dates, custom title, preview frames, or finished MP4 to a Timeline Visualizer account or storage service. There is no user account feature.
The map renderer uses tiles supplied by CARTO and OpenStreetMap data. The tool asks for consent before requesting tiles for a selected journey. CARTO can receive normal request information such as IP address, browser headers, and the tile coordinates needed for the route. Those coordinates may reveal the geographic areas shown in the journey.
The site uses Google Analytics 4 through Google Tag Manager for limited page and tool-interaction measurement. For visitors in the European Economic Area, the United Kingdom, and Switzerland, analytics and advertising storage default to denied until the published Google-certified consent message communicates the visitor’s choice. Outside those regions, Google tags may use analytics and advertising storage by default where applicable. A Plausible-compatible service at pageview.app provides cookie-free pageview and referrer reporting. Events are limited to low-cardinality actions such as loading a sample or Timeline file, completing a preview, exporting a video, downloading, or sharing. They do not include file names, route coordinates, selected dates, custom titles, point counts, distances, or generated media.
The site includes Google AdSense code for site verification and advertising services. When the code loads or ads are served, Google and third-party advertising technology providers may collect or process normal request information such as IP address, browser or device information, and other identifiers. They may place or read cookies, or use web beacons and similar technologies, for ad delivery, frequency control, measurement, security, fraud prevention, and personalization where consent and applicable law allow it. Third-party vendors, including Google, may use advertising cookies to serve ads based on a visitor’s prior visits to this website or other websites. Timeline file names, route coordinates, selected dates, custom titles, point counts, distances, preview frames, and generated videos are not added to ad requests.
Google’s advertising cookies allow Google and its partners to serve ads based on visits to this site and other sites on the Internet. You can opt out of personalized advertising in Google Ads Settings.
For visitors in the European Economic Area, the United Kingdom, and Switzerland, a Google-certified consent message is published to provide consent choices and a manage-options path before relevant advertising storage or personalization is used. You can learn how Google uses information from sites and apps that use its services at Google’s partner sites policy.
No manual ad unit is intentionally placed inside the Timeline upload controls, settings, preview, result actions, error states, or legal pages. Advertising settings will continue to be reviewed so ads do not obstruct the first-screen tool or the private local-processing workflow.
Do not send a Timeline JSON file through the contact channel. To reduce sharing risk, use a narrow date range, inspect the preview for private stops, and share the rendered video instead of the source data. You can stop processing by closing the tab; locally selected files are not retained by the site after the page session ends.
This policy may be updated when the site adds or removes third-party services. Material changes will be reflected on this page. Contact [email protected] with privacy questions.