Cookies

Last Updated: 24 September 2026

This page explains the cookies and similar technologies used by Deuce Creative Limited (trading as Grofomo) across grofomo.com, our ticket pages on grfm.to, and the Grofomo app. It sits alongside our Privacy Policy.

The short version: almost everything we set is needed to make the site work, and we do not use cookies to build a profile of you or to advertise to you. The few that measure which links and adverts sell tickets are only set if you agree, and you are asked before they are.

Essential cookies

These are needed to provide a service you asked for, so they do not require your consent. Blocking them will break sign-in, checkout, or both.

NameSet byWhat it doesLasts
sb-*-auth-tokenGrofomo (via Supabase)Keeps you signed in and carries your session between grofomo.com subdomains. Without it you would be signed out on every page.Until you sign out, refreshed as you browse
active_orgGrofomoRemembers which organisation console you were last working in, so we can take you back there.30 days
last_login_methodGrofomoRemembers how you signed in last time, so the login page can show a "last used" hint. It holds the method only, never your identity.1 year
cf_* (Turnstile)CloudflareConfirms that a form submission comes from a person rather than an automated script. Protects sign-up, pre-sale registration, and ticket lookup from abuse.Session
gfm_consentGrofomoRecords the choice you made in the cookie banner, so we do not ask again and so we honour it. Ironically the one cookie we cannot ask permission for.6 months

Measurement cookies, which we ask about first

These help an event organiser see what led to their ticket sales. Ours remembers which link, post or advert brought you to an event, for up to 30 days, in case you come back later to buy. Where an organiser has also connected their own Meta advertising account to their ticket page, the Meta Pixel loads and sets its own cookies too. Each is set only where you agree.

NameSet byWhat it doesLasts
gfm_attrGrofomoRemembers which link, post or advert brought you to an event on grfm.to, so that if you buy a ticket on a later visit the organiser can see what led to the sale and an ambassador who referred you is credited. It holds the campaign tags and any referral code, not who you are. If you buy, the tags are saved with your order.30 days
gfm_funnel_<event> (session storage)GrofomoA random number that lets the organiser count how many visitors to a ticket page chose tickets and went on to pay, without counting you twice when you reload. It is not a cookie and is never sent anywhere on its own.Until you close the tab
_fbp, _fbcMetaSet by the Meta Pixel where the event organiser has added one, so that organiser can measure which of their adverts led to ticket sales, and reach similar audiences. Meta receives your IP address and the pages you viewed on the event site and ticket page. If you buy, we also report the purchase to that organiser’s pixel from our server, with your IP address, the advert click id and a hashed (scrambled) copy of your email address, so Meta can match the sale to the advert. That report is only made where you accepted these cookies.Up to 90 days

These do not run unless you accept them, and you are asked before they load. A banner appears on the ticket page itself, with Accept and Decline. Nothing is set until you choose, and if you decline, nothing is set at all. Declining does not limit anything you can do on the site, and you can still buy a ticket exactly as normal. If you arrive through a tagged link and buy in the same visit, the link is still credited from the page itself, without anything being stored on your device. Where the Meta Pixel runs, the organiser whose event you are looking at is the controller for that measurement and Meta is their provider, not ours. We list this on our subprocessors page under services a customer switches on.

Changing your mind

The choice is made and changed on the ticket pages themselves, because that is the only place these cookies are ever set. Use the “Cookie settings” link in the footer of any ticket page, or open grfm.to/cookies to change it there.

You can also clear cookies in your browser, or block them entirely through your browser settings, though blocking essential cookies will stop sign-in and checkout working.

Other technologies

Local storage. Ticket pages store a small marker in your browser after a purchase, so that refreshing the confirmation page does not report the same purchase twice. It contains an order reference and nothing else, and is cleared when you close the tab.

The Grofomo app. The mobile app does not use cookies. It stores a randomly generated device identifier and your preferences on the device itself, as described in the Privacy Policy. It contains no advertising identifier and no cross-app tracking.

Content loaded from other companies. Some pages load fonts from Google, and the site-map editor loads Google Maps. These do not set cookies for us, but the company hosting them receives your IP address and browser details as part of serving the request, which is unavoidable for any content loaded from another domain.

Questions

Email privacy@grofomo.com. You can also complain to the Information Commissioner’s Office at ico.org.uk.