Trip-ey.com
Cookie Policy
Effective date: September 12, 2026
This page lists every cookie and browser storage entry Trip-ey uses on the website and in the Chrome extension, what each is for, and how long it lasts. Sections 1–6 cover the website; section 7 covers extension storage.
Trip-ey runs no analytics, no advertising, no social media pixels and no third-party trackers. Nothing on this site profiles you or follows you to other websites. That is why you are not being interrupted by a cookie consent banner — see section 4.
Cookies
Cookies are small files a site stores in your browser. Trip-ey sets only first-party, strictly necessary cookies, and only once you take an action that requires them. Browsing Trip-ey without signing in sets no cookies at all.
| Cookie | Purpose | Set when | Lifetime |
|---|---|---|---|
sb-<project>-auth-token | Keeps you signed in to your account. Set and read by our authentication provider, Supabase. | You sign in | Until you sign out, or the session expires |
sb-<project>-auth-token-code-verifier | Short-lived security value that completes the sign-in exchange and prevents interception of the sign-in code (PKCE). | A sign-in begins | Minutes; deleted when sign-in completes |
trip-ey:oauth-consent:v1 | Records that you ticked the privacy acknowledgement immediately before being sent to Google, so we can verify it when you come back. Sign-in is refused without it. | You choose Sign in with Google | 10 minutes, then deleted |
Browser storage on your device
Most of what Trip-ey remembers is kept in your browser’s own storage rather than in cookies. It stays on your device, is not transmitted automatically with each request, and is not readable by other websites.
| Entry | Purpose | Created when | Lifetime |
|---|---|---|---|
trip-ey:preference-draft:v3 | Your in-progress answers, so you can close the tab and come back to the same travel brief. | You answer the first question | Until you clear it or choose Start over |
trip-ey:wizard-progress:v1 | Which step of the planner you had reached. | You answer the first question | Until you clear it or choose Start over |
trip-ey:preference-consent:v1 | Your acknowledgement of storing your profile, with the policy version it applied to. | You make a choice on the summary step | Until you change it or clear it |
trip-ey:insights-consent:v1 | Your separate, optional permission for aggregated insights and its policy version. Refusing does not restrict the planner. | You opt in on the summary step | Until withdrawn or cleared; a policy version change requires a new choice |
trip-ey:guest-session:v1 | A random identifier with no name or email attached, so a guest submission can be found again and deleted on request. It is created only at the moment you submit a search, never on page load. | You submit a search as a guest | Until you choose Start over or clear it |
trip-ey:accommodation-favorites:v1 | Rooms you saved in the accommodation demonstration. | You save a demo room | Until you remove them or clear it |
trip-ey:recommendations:v3 | Carries your results from the planner to the results page. Session storage only. | A search completes | Until you close the browser tab |
What we do not use
We want this to be unambiguous. Trip-ey contains no Google Analytics, no Google Tag Manager, no Meta or TikTok pixel, no Hotjar, Clarity, Segment, Mixpanel, PostHog or Plausible, no advertising or retargeting tags, no A/B testing tools, no social media share widgets, no embedded maps or videos, and no third-party iframes of any kind. Fonts are served from our own domain rather than from Google Fonts, so loading a page does not disclose your IP address to a font provider.
Some pages link out to airlines, booking sites, government advisories and research publishers. Following such a link takes you to a site with its own cookies and its own policy, which we do not control.
Choosing Sign in with Google sends you to Google, which sets its own cookies on its own domain as part of signing you in. That is Google acting as your identity provider, governed by Google’s policies, not ours. If you sign in with an email address and password instead, Google is not involved at all.
Why there is no cookie consent banner
Under Article 5(3) of the EU ePrivacy Directive — and the equivalent UK rule in PECR — consent is required before storing information on a user’s device, except where the storage is strictly necessary to provide a service the user has explicitly requested, or is used purely to carry a communication.
Every entry in sections 1 and 2 falls inside that exemption. Each one is created only in response to something you deliberately did — signing in, answering a planner question, saving a demo room, running a search — and each is needed to deliver exactly what you asked for. None of them measures your behaviour, builds a profile, or is shared with anyone.
Because there is nothing here that requires consent, a banner would ask you a question with no real choice attached, which regulators discourage. This page is our disclosure instead.
This will change if Trip-ey ever adds analytics or advertising. If we introduce any measurement or marketing technology, we will publish it in the table above and put a genuine consent banner in front of it — one that loads nothing until you agree, with refusing as easy as accepting.
How to control or delete this data
To reset the website planner’s draft, progress, results and consent choices, use the Start over control, which also asks us to delete the matching saved submissions from our database.
You can also clear cookies and site data for Trip-ey.com in your browser settings, or block cookies entirely. If you block them, the public planner still works, but you will not be able to stay signed in and your draft will not survive a page reload.
Signed-in users can delete their account and associated data from the account page. For anything else, write to support@trip-ey.com.
Related policies
This policy sits alongside the Privacy Policy, which explains what we do with personal data on our servers and locally in the extension, and the Terms of Use.
Chrome extension storage and controls
The extension sets no cookies and uses no analytics or advertising storage. Temporary storage supports the chooser you request. It does not use Chrome Sync or copy room selections into the website planner’s storage or database.
| Entry | Purpose | Created when | Lifetime |
|---|---|---|---|
| Saved places and rooms (page memory) | Remembers selections on the same page. | You save a place or room | Until removed, page reload, navigation away or tab closure. Toggling the chooser off does not clear selections. |
rooms:<tabId> | Chrome session storage marker and expiry time to open rooms in the requested tab. No property URL is stored in this marker. | You choose Rooms & photos | Valid for two minutes; removed when consumed or navigation fails. Expired, unconsumed entries can remain until Chrome clears the session on extension disable, reload, update or browser restart. |
Reload or close a Booking.com tab to clear its saved selections. To clear pending handoffs, disable the extension or restart Chrome. To stop using it, disable or uninstall it and reload affected tabs. The website’s Start over control does not clear extension state.
Booking.com and its content providers may set their own cookies or use storage while pages and photos load. Trip-ey does not control those practices. Manage Booking.com’s consent settings and browser site data separately; clearing Trip-ey data does not delete Booking.com cookies.