Cookie Policy — TicketConnect

1. What we store ourselves

Session / sign-inSet when you sign in, so you stay signed in. Strictly necessary — without it there is no account.

Cart contentsYour basket is kept in your browser’s local storage so it survives a page reload. It stays on your device and is not a tracking identifier.

Theme preferenceRemembers light or dark mode on the documentation pages. Purely a display setting.

None of these require consent: they are what makes the site function, and they do not follow you anywhere else.

2. What embedded providers store

Some parts of the site are provided by third parties. When one of them loads, it can set its own storage and will see your IP address. Each has its own policy, which governs what it does with that.

PrivyAuthentication and wallet session state. Loads on any page where you can sign in.

StripePayment processing and fraud prevention. Loads at checkout. Stripe’s fraud checks are a legal requirement for taking card payments.

CARTOMap tiles. Loading a map discloses your IP address to them. No tracking storage is set by us on their behalf.

ChatwootSupport chat, when you open it.

CloudinaryImage delivery. Serves files; sees the request, sets nothing.

SpotifyOnly if you start an import, and only for the duration of that flow.

3. Analytics and marketing — only with your consent

Analytics and marketing storage is off by default. On your first visit we ask; we store your choice in tc_consent_v1 — a strictly-necessary cookie that only remembers the decision itself, not anything about you. You can change your choice at any time via Cookie settings in the footer, or right here:

Necessarytc_consent_v1 — localStorage, ~12 months. Your cookie choice. Always set, never asks.

Analytics (only after consent)tc_attribution — localStorage, 30 days. Which campaign link brought you here (UTM parameters). _ga / _ga_* — cookies, up to 24 months, Google Analytics via Google Tag Manager.

Marketing (only after consent)_fbp — cookie, 3 months, Meta Pixel browser id. _fbc — cookie, 3 months, Meta ad-click id.

With consent, usage and purchase events go to Google (GTM/GA4) and Meta (Pixel and, server-side, the Conversions API). Purchases also carry the campaign parameters (UTM) that brought you here — that first-party attribution stays in our own database and is attached to your order regardless of consent; it is not shared with Google or Meta without your consent.

4. How to control it

Every browser lets you view, block and delete cookies and local storage, per site. Look for “Cookies and site data” under privacy settings.

Blocking storage for this site will sign you out, empty your cart and forget your cookie choice — those are the three things the necessary storage covers. The site keeps working without them; you will just be asked about cookies again.

Analytics and marketing storage (section 3) exists only if you opted in. To revoke it, use — also always available in the footer — and save a choice without analytics or marketing: we stop sending events immediately and set nothing new. Anything Google or Meta already set is removed when you clear this site’s data in your browser.

5. Questions

Write to [TO FILL IN: privacy contact email]. The Privacy Policy covers what happens to personal data more broadly.