Cookie Policy

1. What is a cookie?

A cookie is a small text file a website places on your device when you visit it. Cookies let the website remember things about your visit (such as the fact that you are signed in) and help us understand how the Service is used. We also use similar technologies — local storage, session storage, and tracking pixels — and we refer to all of them collectively as "cookies" in this policy.

2. Cookies we use

Essential cookies

These cookies are required for the Service to function. We cannot turn them off without breaking core functionality such as signing you in or remembering an in-progress trip profile.

• Clerk session cookies — set by our authentication provider Clerk to keep you signed in across pages and to protect your session from cross-site request forgery.
• Next.js / Vercel session cookies — set by our hosting platform to route requests and balance load.
• rv_origin — remembers the starting city you chose or confirmed, and whether you located it, picked it from the list or kept the suggestion, so the first question is pre-filled with it on your next visit instead of a guess from your network location. If your network places you in another country, we suggest that city instead. Kept for 180 days.
• Local storage entries — used to remember short-lived UI state (for example, a partially filled trip profile before the next autosave), and rv_geo_asked, the time we last asked your browser for your location, so we do not ask again for 30 days.

Trip profile cookie

• rv_profile_id — a random identifier of your trip profile. We set it when you start planning a trip, whether or not you accept statistics cookies, and also when you sign in if you have accepted them. It is kept for one year and removed when you sign out. We use it to connect what you do on the site to your trip profile in our own records, for example when you share a trip invitation. If you accept statistics cookies, we also send it with your events to Google Analytics and PostHog.

Analytics cookies

These cookies help us understand which features people use, so we can prioritise improvements. We set them only after you accept statistics cookies in our cookie banner.

• Google Tag Manager — loads the analytics tags we have configured for the Service.
• Google Analytics 4 — measures page views, session length, and the custom events that show how people progress through the trip profile and recommendation flow. GA4 stores a randomly generated identifier in a cookie so repeat visits can be counted as one user.
• PostHog — product analytics: records page views, clicks, and the same custom events, and may record a replay of how you use a page (pointer movement, clicks, scrolling, and what is on screen; text you type into form fields is masked). It stores a random identifier in cookies and local storage whose names start with ph_. Once you start planning a trip or sign in, each event also carries the identifier of your trip profile from our rv_profile_id cookie, so we can connect your visits to the trips you plan, whether or not you have an account. If you are signed in, PostHog links these events to your account.

Functional / third-party cookies

• Mapbox — when your trip profile asks where you are flying from, Mapbox provides the city autocomplete. Mapbox may set its own cookies to optimise that lookup.
• Sentry — our error-monitoring partner sets a short-lived cookie to correlate a session of error reports when the Service throws an exception.

3. What we don't do

We do not use cookies for cross-site behavioural advertising and we do not sell information collected through cookies to third parties. We may add additional analytics or advertising cookies in the future; if we do, we will update this policy and, where required by law, ask for your consent before placing them.

4. Your choices

You can control cookies in a few ways:

• Cookie banner — analytics cookies (Google Analytics and PostHog) are set only if you accept statistics cookies. If you decline, they are not set.
• Browser settings — most browsers let you block or delete cookies. Blocking essential cookies will break sign-in and other core functionality.
• Do Not Track — we honour the browser-level GA4 opt-out signal where supported.
• Marketing email — unsubscribe links are at the bottom of every marketing email we send.
• Account deletion — deleting your account from Manage account inside the Service also clears the server-side records cookies refer to.

5. Changes to this policy

We may update this Cookie Policy as our Service evolves. The "Last updated" date at the top reflects the most recent change. For material changes we will notify you in the Service or by email where required by law.

6. Contact us

Questions about cookies can be sent to hello@rendezvous.global.