Cookie Policy
Last updated: 2026-10-28
Functional cookies (required)
sb-* cookies from Supabase Auth keep you signed in. Without them the service can't function.
Other cookies on our own site
We also set a few small first-party cookies of our own. None of them is shared with an advertising network, and each one only carries what is listed here.
gz_ref(30 days): the referral code from a shared link, so the person who referred you is credited when you sign up, even if you confirm your email in another tab.gz_src(30 days): which of our pages sent you to sign up (for example the free ATS checker or a sponsor page), and the company, scheme or city on it, so your account opens on the right starting point.gz_plan_pref(7 days): the plan you picked on the pricing page, and whether you chose monthly or annual billing, so it is still selected after you confirm your email.gz_signup_intent(1 hour): the plan and the button that brought you to sign up, and the page it was on, so it is still known if you sign up with Google, LinkedIn or Apple. It holds no identifier.gz_paywall_seen(1 day): remembers that we have already shown you the plans page today, so we do not show it again until tomorrow.gz_dev(1 year): a random device marker that limits the free lookups available without an account. It holds no personal details.rizzume_locale(1 year): the language you chose.cv_share_*(24 hours): set only when you unlock a password-protected shared CV, so you do not have to enter the password again on that link.
Cookieless analytics (always on, no cookies)
Before you choose anything, we measure the site with privacy-first, cookieless analytics (PostHog EU, Frankfurt). It sets no cookies, stores nothing on your device, and creates no persistent identifier, so it cannot recognise you across sessions or sites. We use it only in aggregate, to see which pages are visited and where visitors get stuck, and the client IP is discarded. Because it stores nothing on your device, it needs no consent under PECR, and session replay is never part of it.
Account events (no cookies)
Separately, when you create an account or pay, we record a few events tied to your account ID: the sign-up itself, a one-off link between the visit in which you signed up and your new account, payment confirmations, and failed AI requests sent by our server. They set no cookies and are recorded whatever you choose here, under legitimate interests rather than consent. The privacy policy lists exactly what they contain and how to object (email support@gorizzume.co.uk).
Enhanced analytics (opt-in)
When you opt in, we switch analytics to a persistent mode that recognises returning visitors and turns on session replay, using three processors. None of them sets an advertising ID, tracks you across other sites for advertising, or resells any data. (Marketing cookies, below, are a separate opt-in and do involve advertising networks. They are off unless you turn them on.)
- PostHog EU (Frankfurt): persistent product events, funnels, retention and sampled session replay. Cookies set on the PostHog EU domain.
- Microsoft Clarity: anonymised heatmaps and session replays so we can fix usability issues. Form inputs, CV body and interview transcripts are masked client-side before they ever leave your browser. Cookies set on
clarity.ms. - Google Analytics 4 (Google, United States): page views and sign-up and checkout steps across the whole site, so we can see which channels bring people who go on to sign up. It is not loaded at all until you opt in. It runs with Google signals and ad personalisation off and advertising storage denied, and it is not given your name, email or account ID. Cookies set on our own domain (
_gaand_ga_*). If you withdraw consent, it stops collecting and stops reading or setting its cookies straight away, without a page reload. Our lawful basis is your consent; detail in the privacy policy.
Marketing cookies (opt-in)
Only set if you explicitly opt in via the cookie banner. These measure whether an advertising campaign actually brought someone to us. Unlike everything above, this involves advertising networks, and it is the one tier that is off by default and stays off unless you choose it.
- TikTok Pixel: tells us that a visitor arrived from a TikTok ad and later signed up, so we can tell which campaigns are worth running. Cookies set on
tiktok.com. TikTok uses this data for its own purposes as well as ours, which makes us joint controllers rather than TikTok being our processor. See the privacy policy for what that means for your rights. - Meta Pixel (Facebook and Instagram ads): the same thing for Meta campaigns. Cookies set on
facebook.com. Meta likewise uses what it receives for its own purposes as well as ours, so we are joint controllers there too.
Where they run. Both pixels load on our advertising entry pages only: the home page, campaign landing pages, pricing, the free ATS checker, and the blog. They are deliberately absent from three places:
- Anywhere you are signed in. Your CV, your applications, your job searches and your profile are never in scope.
- Our visa and sponsorship pages. A page address alone can reveal that someone is researching immigration sponsorship, and that is not something we will hand to an ad network.
- Shared scan results, shared CVs, and your own scan result page. These carry a private link, and a pixel would send that link onward.
Changing your mind. Turning marketing cookies off in Settings Data & privacy stops collection immediately, without needing a page reload.
Managing your preferences
You can change or withdraw your cookie preferences at any time, signed in or not, with the link, which is also at the bottom of every page. If you have an account, the same choices are in Settings Data & privacy.