Cookies and tracking

One thing, and only after you have been asked. When you answer the banner, your answer is written to your browser's local storage under the key t21.consent, so we do not ask again on every page. It never leaves your device, it is not a cookie, it is not sent to us or to anyone else, and it holds nothing but yes or no and the date. That record is what Article 5(3) of the ePrivacy Directive calls strictly necessary: without it there is no way to honour the answer you gave.

No cookies at all. There is no login, no basket and no on-site analytics, so there is nothing to keep. Anything the site needs to remember within a page it remembers in memory, and forgets when you close the tab.

The Meta Pixel, from Meta Platforms Ireland Ltd, so we can tell whether our advertising on Facebook and Instagram is reaching the people it is meant to reach. It stores:

_fbp

Set on this domain by the pixel script. A randomly generated browser identifier that lets Meta recognise the same browser across visits. Expires after about 90 days.

fbc, from an fbclid link

If you arrive from a Meta advert, the click identifier in the URL is stored the same way, so the visit can be attributed to that advert. Expires after about 90 days.

fr and other Meta cookies

Set on facebook.com rather than here, when you are signed in to Meta's own services. They are governed by Meta's cookie policy, not by ours.

What is sent to Meta is the fact of a page view, the page address, and the identifiers above. We do not pass your name, email address or the contents of an enquiry to it.

The pixel does not load at all unless you have agreed. Decline on the banner and nothing is written; there is no second layer, no legitimate-interest tab, and declining takes exactly one click, the same as accepting.

You can change your mind in either direction at any time: Cookie settings, at the foot of every page, reopens the banner. Withdrawing also deletes the identifiers already stored and reloads the page, because a script that has already run cannot be unloaded — stopping the next one would not be an honest answer.

Beyond that, the usual controls all work:

• Block third-party scripts in your browser, or use a content blocker — the pixel is one of the scripts every major blocker already recognises.
• Refuse or delete cookies for this site in your browser's site-settings panel. Chrome, Safari, Firefox and Edge all offer this per-site.
• Turn off off-Facebook activity and ad personalisation in the settings of your Meta account, which stops Meta linking what it receives to your profile.
• Browse in a private window, which discards everything set during the session when you close it.

Refusing changes nothing about how this site works for you: no page, form or feature depends on the pixel.

If we ever add a script that stores something on your device, it is listed here before it ships, and the date at the top moves. The privacy policy explains the legal basis for each one and the rights you have over what it collects.

Questions about any of this go to hello@twenty-one.co, or 210 3000 463, or Plataion 55, 104 35 Athens, Greece. A named person reads that inbox — it is not a ticket queue.