Legal

Cookies and tracking

This site sets no cookies of its own — no analytics, no session, no preference store. Two advertising scripts do, and this page is about those two.

Last updated 7 September 2026

01

What this site sets

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.

02

The first: the Meta Pixel

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.

03

The second: the Google tag

The Google tag, from Google Ireland Ltd, so we can tell which of our adverts on Google Search lead to an enquiry rather than merely to a visit. It works differently from the pixel above, and the difference is worth stating rather than hiding: this script is loaded for everyone, but it is instructed to deny every kind of storage before it starts. Google calls this Consent Mode. Until you accept, it writes nothing to your device, reads nothing from it, and what it sends carries no identifier of you. If you accept, it stores:

_gcl_au
Set on this domain by the Google tag. A randomly generated identifier that lets Google connect a click on one of our adverts to what happened afterwards on this site. Expires after about 90 days.
gclid, from an advert link
If you arrive from a Google advert, the click identifier in the URL is kept the same way, so an enquiry that follows can be attributed to the advert that paid for the visit.
Cookies on google.com
Set on Google's own domains rather than here, when you are signed in to a Google account. They are governed by Google's cookie policy, not by ours.

What is sent to Google is the fact of a page view, the page address, the identifiers above, and — if you send the contact form — the fact that a briefing was submitted. Your name, your company, your email address and the contents of your message are never passed to it.

04

How to refuse 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.
  • Turn off ad personalisation in your Google account settings, which stops Google 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.

05

Changes

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.

Company details

Registered name
TWENTYONE WEST COAST TRVL STORIES ΜΟΝΟΠΡΟΣΩΠΗ Ι.Κ.Ε.
In Latin characters
TWENTYONE WEST COAST TRVL STORIES SINGLE MEMBER P.C.
Legal form
Single-member private company (Ι.Κ.Ε.) incorporated in Greece
Registered office
Plataion 55, 104 35 Athens, Greece
Γ.Ε.ΜΗ. number
191601903000 — General Commercial Registry (Γ.Ε.ΜΗ.), Athens Professional Chamber
VAT number
EL803186370 (ΚΕΦΟΔΕ Αττικής)
Manager
Panagiotis Athanasakopoulos
Contact
hello@twenty-one.co · 210 3000 463

Honestly? You’re going to regret switching tabs.

Finding top-tier custom developers who actually care about your business scale is nearly impossible.

We are the best at what we do, and we’ve got the track record to prove it. Don’t waste time and money with second-best options.

You convinced me.
Let’s talk!