Cookie Policy - TimeTuna

The short version

Booking pages set no tracking cookies. Not on timetuna.com, not on a host’s custom domain, not in an embed.
On our own website we use analytics and marketing cookies. Where the law requires consent, nothing loads until you agree.
You can change your answer at any time from “Cookie settings” in the footer.

If someone sent you a TimeTuna link to book a meeting, this page is mostly not about you. Booking pages store nothing on your device beyond what is needed to complete a payment, so you are never shown a cookie banner and never asked to agree to anything.

1. Booking pages are cookieless

A booking page is the page a host shares with their guests. We deliberately run no analytics identity, no session recording, no advertising tags and no support chat there. Nothing is written to cookies, local storage or session storage, with one exception:

booking_<booking page id> in session storage, written only if you start a paid booking, so your answers survive the redirect to Stripe and back. It is cleared when you close the tab.

We do count anonymous page views on booking pages, using a privacy-preserving identifier that our analytics provider derives on its own servers and rotates daily. It stores nothing in your browser and cannot be used to recognise you tomorrow.

2. What timetuna.com sets

Name	Set by	Where	Purpose	Expiry	Category
`tt_consent`	TimeTuna	Cookie	Remembers your cookie choice	6 months	Strictly necessary
`sb-<project>-auth-token`	Supabase	Cookie	Keeps you signed in	Session to 1 year	Strictly necessary
`tt_calendar_oauth_<provider>`	TimeTuna	Cookie	Security check while connecting a calendar	10 minutes	Strictly necessary
`appsumo_activation`	TimeTuna	Cookie	Links an AppSumo purchase to your sign-in	24 hours	Strictly necessary
`tt-stale-deployment-reload-at`	TimeTuna	Session storage	Prevents a reload loop after we deploy an update	Tab session	Strictly necessary
`ph_<token>_posthog`	PostHog	Cookie and local storage	Product analytics, including session recording on our own pages	1 year	Analytics. Never set on a booking page
`_ga`, `_ga_<id>`	Google Analytics	Cookie	Website analytics	2 years	Analytics
`_gcl_au`	Google Ads	Cookie	Measures which ads lead to signups	90 days	Marketing
`crisp-client/*`	Crisp	Cookie and local storage	Keeps your support chat history	6 months	Functional
`timetuna_utm_data`	TimeTuna	Local storage	Remembers which campaign brought you, for signup attribution	30 days	Marketing

3. When we ask, and when we do not

We work out roughly where you are from your connection, and ask for consent where the law requires it: the EU and the wider EEA, the United Kingdom, and Switzerland. If you are there, nothing in the analytics, marketing or functional categories loads until you answer, and declining is one tap, exactly like accepting. If we cannot tell where you are, we treat you as if you were in the EU.

Elsewhere, those categories are on by default and you can turn them off at any time from “Cookie settings” in the footer. Strictly necessary items are always on: without them you cannot sign in, connect a calendar, or complete a payment.

4. Global Privacy Control

If your browser sends a Global Privacy Control signal, we treat it as a refusal everywhere in the world, and we do not show you a banner. You can still opt in deliberately from “Cookie settings” if you want to.

5. Changing your mind

Anyone can use “Cookie settings” in the footer. If you have a TimeTuna account, the same choice also lives under Profile, Privacy, where it follows your account across every device you sign in on. Withdrawing consent stops what we can stop immediately and reloads the page to unload the rest.

6. Contact

Questions about this policy, or about the data behind it, are covered by the contact section of our Privacy Policy.