Information stored on your device
The planner uses browser storage for recent and saved trip choices, manual itinerary edits, traveler checklist progress, display preferences, cached live responses and beta problem reports. This information normally stays in that browser unless you choose a cloud-save feature, submit a report, copy a link or export a file.
Shared trip links can contain the visible planning choices in the URL, including origin, destination, date, duration, group size, interests, travel mode, pace and budget band. Anyone receiving such a link may see those choices.
Ask Triply processes chatbot questions inside the current browser tab using the published destination catalogue. The current rule-based beta does not send questions to an AI provider, save them to browser storage or add them to the Triply database.
Information handled by the service
Requests necessarily include ordinary connection data used to deliver the site. The service creates random request IDs and records privacy-limited server failures with the route, status code, response time and time of failure. Raw IP addresses are not placed in the incident log.
Submitted beta reports may include the selected category, description, release number and a limited trip context. Exact station or address fields, saved-trip IDs, edited-stop IDs, names, email addresses, precise device locations and browser fingerprints are excluded by the report tool.
If account-based trip saving is enabled, the service uses the signed-in account identifier to separate saved trips. The owner workspace is restricted to the configured owner account.
Live information providers
Weather and road-route requests send destination or route coordinates to the configured weather and routing providers. Map tiles may be requested from OpenStreetMap infrastructure. Verified tourist-place images load from Wikimedia Commons in the browser, which sends ordinary connection data to Wikimedia; the displayed credit links to the image source and licence. When no curated image exists, the service searches Commons only after a conservative place-and-district match. Following an official source, Google Maps, booking or other external link takes you to that provider, whose own privacy terms apply.
The beta does not request browser geolocation, camera or microphone access.
Your choices
- Remove saved trips and reset checklist confirmations inside the planner.
- Clear downloaded or device-saved problem reports from the report window.
- Clear this site’s browser data to remove its local storage and cache.
- Avoid sharing a trip link when its visible choices are sensitive.
- Use the Help & contact page to request assistance with server-held beta information.
Retention and changes
Operational failure records are designed for 30-day retention. The device report queue is limited to 25 reports. Provider cache entries expire according to the service’s freshness windows. Other server records, including submitted reports and account-saved trips, are retained for operating the beta until removed through the available controls or an owner action.
This notice may change when accounts, providers, analytics or nationwide coverage are introduced. The date at the top will be updated when the notice changes.