Cookie Policy

1. What cookies are

A cookie is a small file a website asks your browser to keep and send back on your next visit. Websites also use related technologies — local storage and session storage — which hold data in your browser but are never sent to a server automatically.

This policy covers all three, because what matters is what is stored on your device, not the mechanism.

2. How Tripsy uses cookies

Only to make the product work:

• to keep you signed in as you move between screens;
• to remember settings like your preferred currency;
• to make screens load instantly instead of refetching what you just looked at.

And one thing beyond that: an affiliate cookie that lets a travel partner credit Tripsy for a booking you make after following a link from us. It is described in its own section below.

We do not use cookies to profile you, build an advertising audience, or measure your behaviour for analytics.

3. Strictly necessary cookies — the only ones we set

• Supabase session cookies (names beginning sb-): your sign-in session, set by our authentication provider. Without them you would be signed out on every page. They last for your session and are refreshed while you stay signed in.
• tripsy_beta: set only if you reach Tripsy through a pre-launch access link, so you are not asked again. It is httpOnly, so JavaScript cannot read it, and it lasts 30 days.

These are essential to deliver a service you asked for, so under UK and EU rules they do not require consent. You can block them in your browser, but you will not be able to sign in.

4. Functional, analytics, performance and advertising cookies

Functional

We use no functional cookies. The equivalent preferences are kept in local storage — see below.

Analytics

None. Tripsy has no analytics package installed. We do not use Google Analytics, PostHog, Mixpanel, Amplitude, Hotjar, Plausible, or any equivalent.

Performance

None. No performance-monitoring or error-tracking SDK — no Sentry, no Vercel Analytics or Speed Insights.

Marketing and advertising

No advertising cookies, no Meta Pixel, no TikTok Pixel, no Google Ads tags, and no remarketing. We do not build audiences and we do not sell or share what we store.

Affiliate attribution — the one non-essential cookie we set

We use Travelpayouts, an affiliate network. Its script marks your visit so that if you follow one of our links to a travel partner and book, that partner can credit Tripsy with a commission. You pay the same price either way.

• am_user_session: set on getripsy.com by the Travelpayouts script, identifying the visit for attribution.
• A local storage entry used by the same script.
• Travelpayouts and the travel partner also set cookies on their own domains once you follow a link and leave Tripsy. Those are outside our control — use your browser controls for those.

This is the only category you can reject, and rejecting it does not change what Tripsy recommends to you — see our Affiliate Disclosure.

5. Third-party services

Stripe: when you buy something, we send you to Stripe's own checkout page. Stripe sets its own cookies there, on its own domain, for payment processing and fraud prevention, under Stripe's privacy policy. We do not embed Stripe's JavaScript in Tripsy, so Stripe sets nothing while you are on getripsy.com.

Our identity verification provider: if you verify your identity for Tripsy Circle, that check happens on the provider's own platform under its own policies. See the Privacy Policy.

Vercel, our hosting provider, processes requests to serve the site and keeps standard server logs. It does not set tracking cookies for us.

Links in Tripsy may take you to third-party sites — an airline, a hotel, a booking site — which set their own cookies once you arrive. We have no control over those. See our Affiliate Disclosure.

6. Local storage and similar technologies

These stay in your browser and are not transmitted to us automatically:

• tripsy_profile — a legacy copy of your travel profile, kept only so older browsers can migrate from it. Local storage.
• tripsy_gen_count — a local count of trips generated, for in-app display. Local storage.
• tripsy_trip_capture_dismissed — that you dismissed an email prompt, so we do not ask again. Local storage.
• tripsy_pack_essentials_<trip> — which packing-list items you have ticked. Local storage.
• tripsy_itinerary_<trip> — a short-lived copy of the itinerary you are viewing, so it reappears instantly. Session storage, cleared when you close the tab.

Clearing your browser data removes all of these. Your Account, trips and profile live on our servers and are unaffected.

7. Managing your preferences

On your first visit you will see a banner with two equally weighted choices, Accept and Reject, covering the affiliate cookie described above.

Being straight with you about the default: the affiliate script loads unless and until you reject it, so on a first visit it may set its cookie before you have chosen. Choosing Reject stops the script loading on this and every later visit, and clears the affiliate cookie and local storage it left on getripsy.com. Cookies already placed on Travelpayouts' or a travel partner's own domain are outside our reach and can only be removed through your browser.

Your choice is stored in a cookie called tripsy_cookie_consent for one year. To change it, clear that cookie in your browser and the banner will appear again.

Strictly necessary cookies are not covered by the banner, because the service does not work without them.

8. Browser controls

Every major browser lets you view, block, and delete cookies and clear local storage:

• Chrome — Settings, then Privacy and security, then Third-party cookies.
• Safari — Settings, then Privacy.
• Firefox — Settings, then Privacy & Security.
• Edge — Settings, then Cookies and site permissions.

Blocking cookies for getripsy.com will sign you out and prevent you signing back in, because the sign-in cookie is one of them.

9. Changes to this policy

We will update this page when what we store changes, with a new effective date. This page was revised on 9 August 2026 when we added affiliate attribution, which was the first non-essential cookie Tripsy had ever set.

10. Contact

Questions about anything here: hello@getripsy.com.