Your privacy choices

What we measure

Events, not people: a page was viewed, a date was checked, a quiz was finished, a booking reached step three, an arcade was opened. Each one carries a few fixed fields — which package, how many days before the party, what kind of device, whether the answer was yes or no — and nothing else. Anything not on that list is dropped before it is stored, by design, because a list of allowed fields fails safe and a list of banned ones does not.

bc_aid13 months

A random number that means “this browser”. It is not derived from anything about you — not your email, not your IP, not a fingerprint — and on its own it identifies nobody.

bc_sid30 idle minutes

Groups one visit together, so five pages read in one sitting are not counted as five visits. It is cleared when you close the tab.

bc_attr90 days

Where you first arrived from: the campaign tag on the link, the site that linked to us (the host name only, never the full address), and the first page you landed on.

bc_ref90 days

If you came from someone's invitation, an opaque code for that invitation — never the web address, which contains a child's name. It is how we know that parties bring people to us rather than adverts.

What we deliberately do not

• No third-party trackers on the invitation pages — no Meta pixel, no Google Analytics, no TikTok tag, no session recorder, no heatmap, no ad network. An invitation's web address contains a child's first name, so nothing on those pages loads from anyone but us. That is a rule (§18), not a phase.
• On our own marketing pages — the ones with prices on them — we do run a Meta pixel, so we can tell which advert brought someone here. It is switched off entirely by the toggle above and by Do-Not-Track, and it never sees a name, an email or an invitation address.
• No children's data in analytics, ever. Not a name, not a nickname, not a player name typed on the TV, not an age, not a birthday.
• No names, emails, phone numbers or addresses in an analytics event — the collector refuses them at both ends, in your browser and again at our server.
• No web address of an invitation. The address contains a child's first name, so it is replaced before anything is sent.
• No RSVP answers reported from the page you typed them on.
• No cross-site tracking, no advertising profiles, no data brokers, no sale or sharing of any of this. Nothing here leaves our own servers.

If your child was invited to a party

The invitation page carries no advertising and no third-party code at all. What you type into an RSVP goes to the host of that party, and to us only so we can show it to them: first names, a head count, and anything you chose to add. Your reply is recorded by our server when you send it — it is never packaged up as an analytics event in your browser, so there is nothing about it to leak from one. The optional “when is your child's birthday?” question is exactly that: optional, asked of you and never of your child, and used for one email about a month before. The phone number is optional too, and the box beside it — “text me about the party” — is the only thing that lets us send anything to it: unticked when you arrive, never needed to reply, good for that one party, and STOP ends it. Leave it alone and the number is simply the host's, the way it always was.

Children’s privacy notice · Privacy policy

Other ways to stop us

• Turn on Do Not Track or Global Privacy Control in your browser. We honour both: with either one set we send nothing at all, and we do not even set the identifier cookie.
• Block cookies for this site. Everything on it still works; the measurement simply stops.
• Have an account with us? Ask us to delete it and everything attached to it goes with it, within thirty days.