Cookie Policy

1. What cookies are

Cookies are small files a site asks your browser to store and send back on your next visit. They are how a website recognises that two visits came from the same browser.

2. The two cookies we set

Both are strictly necessary, both hold no personal detail, and neither can be switched off without breaking something you asked for.

• →rt_uid — a long random token and nothing else: no name, no email, no trip content. It is how we recognise your planning session, so the trips you created are still yours when you come back and a paid subscription stays attached to you. It lasts up to one year. It is httpOnly, so scripts in the page cannot read it; it is sent only over HTTPS in production; and it is scoped to Runtrip with SameSite=Lax, so it is not sent to other sites.
• →rt_consent — the choice you make in the banner, stored as two on/off values and a version number. It lasts twelve months, after which we ask again. Scripts can read this one, because the page has to know whether it is allowed to load anything optional before it loads it. It carries no identifier and grants no access.
• →Why neither needs your consent — under the ePrivacy rules a cookie that is strictly necessary to deliver the service you asked for is exempt, and so is one that records a privacy preference. Everything that is not exempt is in §3, off until you say otherwise.

3. Optional cookies, and what we never use

There are two optional categories. Both are off until you turn them on in §4, and nothing in either one loads before that — the analytics code is not downloaded, let alone run.

• →Analytics — product analytics and session replay, provided by PostHog on its European servers. With this on, PostHog stores its own identifier and a few related values in this browser (a cookie and some local storage) so it can tell one visit from the next, and it records which pages you opened, which features you used, and a replay of your interaction with the page. Replays deliberately mask what you type and the plans we generate for you, so your trip brief and itinerary are not legible in a recording. Its identifiers last up to a year unless you clear them or switch this off.
• →Marketing — email marketing and matching a subscription back to the ad or link that brought you here. Nothing on Runtrip uses this category yet, so turning it on changes nothing today. It exists as a separate switch because consenting to analytics is not consent to marketing, and we would rather ask you once than re-prompt everyone later.

What we do not use, whatever you choose: no advertising cookies, no cross-site trackers, no social pixels, and no sale of your data to anyone who runs them. We also measure aggregate traffic and page performance with Vercel Analytics and Speed Insights, which are deliberately cookieless — they store nothing on your device and build no cross-site profile — so they are not part of the choice below.

4. Your cookie settings

The choice is stored per browser, so it applies here and not on your other devices. Switching analytics off stops the collection at once and clears what the analytics SDK is holding in this browser; switching it back on starts a fresh collection and does not recover anything from before. Withdrawing has no effect on your trips, your account, or your subscription.

5. Third-party storage

Signing in, subscribing, and paying are handled for us by monetize.software, which serves those screens from its own domain. That provider may set its own cookies or storage on that domain to keep you signed in through checkout, governed by its own cookie and privacy policies rather than this one.

Booking links in a plan take you to partner sites such as airlines, hotels, and booking platforms. Once you follow a link, that site's own cookie policy applies. We do not embed partner tracking on Runtrip itself.

6. Managing cookies

For the optional categories, use the switches in §4 — that is the fastest route, it takes effect immediately, and it is reachable from the “Cookie settings” link in the footer of every page. Switching analytics off also stops the collection and clears what the analytics SDK is holding in this browser.

You can also clear or block cookies entirely in your browser settings. Because rt_uid is what links you to your saved trips, clearing it will sign you out and start a fresh anonymous session — trips created under the old session will no longer appear, so export anything you want to keep first. If you have signed in, signing back in restores access to your account. Clearing rt_consent means we ask about the optional categories again on your next visit.