Send a message to contact@timelinetovideo.com. Use a subject such as “Android export,” “iPhone JSON error,” “MP4 export,” “privacy question,” or “attribution correction” so the request can be triaged without reading sensitive content.
What to include in a technical report
Include the device type, operating-system version, browser and version, whether the file came from Android, iPhone, or an older Takeout archive, an approximate file-size bucket, the exact visible error message, and the step that failed. A screenshot is useful only if it excludes the map, route, filenames, user titles, and other personal details.
Before writing, try the private Timeline JSON checklist or the complete export guide.
What not to send
Do not attach a Timeline JSON file, exported archive, photo, music file, or generated video. Do not include coordinates, place or city names, exact trip dates, route screenshots, filenames, custom titles, account details, or links containing private journey parameters.
If a minimal reproduction is necessary, use the fictional sample journey and describe which settings reproduce the failure. The sample is designed for testing without personal location history.
Privacy and independent status
Email is an external communication channel and is not part of the browser-local rendering pipeline. Read Privacy before deciding what to send.
Timeline to Video is independent and is not affiliated with, endorsed by, or sponsored by Google. Questions about a Google account, Timeline backup, or Google Maps retention must be handled through Google’s own support resources.