Skip to content

Cookies and browser storage

Last updated 26 September 2026.

This page lists what this site keeps in your browser, the one cookie our API can set, and the outside services a page loads.

Contents
  1. In short
  2. Session storage
  3. Local storage
  4. Cookies
  5. What pages send to us
  6. Other services a page loads
  7. Your choices
  8. What this notice covers
  9. Changes and contact

In short

The site itself writes no cookies. It keeps a few small values in your browser’s session storage, which the browser clears when you close the tab. One cookie can come from our API, which runs on Google Cloud. The site uses no advertising cookies and loads no advertising or social media trackers.

Session storage

Session storage belongs to this site and this tab. None of these values holds your name, your email or anything else you typed.

Attribution IDtc_attribution_token
A random ID for your visit, or one carried in from a Tripcreator AI link that includes the atk parameter. It is added to the Partner Hub sign-in link, so a sign-up can be traced to the visit that led to it.
Visit IDtc_analytics_session_id
A random ID for your visit, so the visit is counted once in our visit statistics.
Visit countedtc_analytics_session_started
Marks the visit as counted, so reloading a page does not count it again. Its name ends with the visit ID.
Reload guardtcLandingChunkHealerLastReloadAt
The time the page last reloaded itself after part of the site failed to load, for example shortly after we release an update. It stops the page reloading more than once a minute.
Investor sign-ininvestor_token
Only for invited investors who sign in to the investor data room. It keeps you signed in for the session and is removed when you sign out.

Local storage

The site keeps nothing in local storage. Earlier versions saved your colour theme there under tc-theme. The current site neither reads nor writes it, and you can clear it in your browser settings.

Cookies

The site writes no cookies of its own. One can arrive from our API:

Server routingGAESA, on api.tripcreator.ai
Our API receives the page reports described below and the forms you send. It runs on Google Cloud, which may set this cookie so that your requests reach the same server. It is used only for that routing and expires after 30 days.

What pages send to us

Each page sends short reports to our API at api.tripcreator.ai: page speed measurements and any errors, with the page address and a random ID for that page view. When you send a form, such as a demo request or a contact message, it goes to the same API. Our privacy policy covers what we do with it.

Other services a page loads

Cloudflare
Delivers the site and adds its Web Analytics script, from static.cloudflareinsights.com, to each page. It measures page views and load times and sets no cookies.
Unsplash
The photographs on our pages load from images.unsplash.com.
Mapbox
When the map in Ask MarcoPolo zooms in to a day, the street map loads from api.mapbox.com.
TidyCal
If you book a call in the demo request form, its scheduling step shows a TidyCal calendar in a frame. TidyCal’s own terms and cookies apply inside that frame.

Each of these services receives your IP address and basic browser details when your browser contacts it. The site’s fonts are served from our own domain.

Your choices

You can clear or block cookies and site storage in your browser settings. The site still works without them, but the investor data room cannot keep you signed in.

What this notice covers

This notice covers www.tripcreator.ai. The Partner Hub, MarcoPolo Chat, Triage and the planners on our customers’ websites are separate apps. Our privacy policy covers the personal data they handle.

Changes and contact

We update this page when what the site stores changes. Questions: privacy@tripcreator.ai.