Cookie notice
Last updated: 29 September 2026
The Betrayal stores a few small things it needs to work. The law doesn’t require us to ask your consent for these, but we want you to know what they are. We also ask whether we may use Google’s advertising cookies, which tell us which of our adverts bring people here. They stay off unless you say yes, and the game itself (your Table and every player’s phone) never uses them.
Google Tag Manager is on the site’s pages either way, in Google’s Consent Mode. Until you say yes it sets and reads no cookies and sends Google only a basic signal that a page was viewed or a Table booked, with no identifier for you (your browser’s request carries its IP address, as any request does). If you arrived from one of our adverts, the advert’s reference stays in the page address as you move around the site, so it can be saved if you then say yes. Google uses those signals to estimate how many bookings its adverts led to.
What we store on your device
| Name | Type | What it does | How long |
|---|---|---|---|
cc_gate | Cookie | Remembers that you entered the preview password while the site is not yet public. It will be removed when we launch. | 30 days |
bt-pin | Browser storage | Keeps the Keeper PIN on the Keeper’s phone, so the Keeper doesn’t have to type it for every tap. | Until the Keeper wipes the game or clears the browser |
bt-draft | Browser storage (this tab only) | Keeps the host’s game plan while it is being set up, so a reload doesn’t lose it. | Until the tab is closed or the game starts |
bt-played | Browser storage | Remembers that a Classic game has been played on this phone, so the next setup can suggest the twists. | Until cleared |
bt-device | Browser storage | A random identifier for this device, sent with problem reports and the game’s error log so we can tell which screen had the trouble. It contains nothing about you. | Until cleared |
bt-m-code, bt-mreq-code | Browser storage | Modern: keeps your place in a Table (a random token), so a reload doesn’t lose it, or a request to be let back in. | Until cleared |
bt-name, bt-pass-code, bt-test-code | Browser storage (this tab only) | Modern: carries your name, the booking code or a test-game choice from one page to the next while you join or set up. | Until the tab is closed |
bt-egg | Browser storage | Remembers that you found the broken seal, so the Book a Table page can apply its 10% off one party. Cleared once you’ve used it. | Until used or cleared |
bt-src | Browser storage (this tab only) | Notes how this visit reached us: the link’s campaign tags (such as utm_source), an advert’s click, or the site you came from. If you buy, it goes with your booking so we can see which links and adverts lead to sales. It holds nothing about you and nothing about other sites you’ve visited. | Until the tab is closed |
bt-v1, bt-settings | Browser storage | Only when the game is played offline without a Table: keep the game and the question-bank switches on that device. | Until cleared |
Advertising cookies (only if you say yes)
| Name | Type | What it does | How long |
|---|---|---|---|
bt-consent | Browser storage | Remembers whether you said yes or no to advertising cookies, so we don’t ask again. | Until cleared |
bt_click | Cookie (ours) | Set only after you say yes, and only if you came from one of our adverts: the advert click’s reference, kept by our own server so that if you book later, even days later, we can tell Google Ads that advert led to a booking. Saying no deletes it. | 90 days |
_gcl_au and Google’s own advertising cookies | Cookies (Google Ads) | Set by Google’s tag, only after you say yes. They let Google Ads tell us when someone who clicked one of our adverts books a Table, so we know which adverts work. After a yes, a booking also sends Google a hashed form of the email address given at checkout, so it can match the booking to the advert; Google can’t read the address from it. Google’s use of them is covered by Google’s advertising policy. | Up to 90 days (_gcl_au); Google sets its own |
Payments
When you pay, you’re taken to Stripe’s secure checkout page. Stripe sets its own cookies there, which it needs to take the payment and prevent fraud. See Stripe’s cookie policy.
Controlling them
You can change your advertising choice at any time with the button above. You can also clear or block cookies and browser storage in your browser’s settings. If you do, the Keeper will have to re-enter the PIN, and the preview password will be asked for again.
Questions? See our privacy notice or contact us.