Cookie policy
Last updated: 31 October 2026
1. The short version
This website uses Google Analytics measurement cookies, and only if you accept them. It also shows a Google Maps map of where we are, and only if you accept that too: you answer each one separately. Until you answer the notice, we ask Google for nothing: no script, no map, no preconnection, nothing at all. If you say no, the same.
The only advertising cookies are those of the Meta Pixel and those of OpenAI's pixel , and only if you also accept advertising, apart from the rest: until then, and if you say no, we ask neither Meta nor OpenAI for anything. There is no social button and no chat. The typeface is served from this same domain, so your IP address does not reach anyone because a letter had to load.
2. The cookies that need your permission
These are Google Analytics'. They tell us how many people come in, which pages they read, how far down they go, what they press and where they arrive from. We use them to find out whether this site works, which until now we did not know.
_ga- Distinguishes one visitor from another. Expires after 2 years.
_ga_<id>- Keeps the state of the session. Expires after 2 years.
They are Google's cookies, not ours, even though they are set from this domain. Google LLC is a United States company and processes that data there. Our Analytics property sits under a Google Ads account: if we ever link the two to measure campaigns, Google will add advertising cookies, and this page will say so before that happens.
Browsers cut those lifetimes down on their own: Chrome caps them at 400 days, and Safari at 7 if you do not come back.
If you also accept advertising, the Meta Pixel's cookies join them. They tell Meta which pages you see here and whether you send the form or press the WhatsApp button, so that we know which of our Facebook and Instagram ads bring requests and so that Meta shows them to whoever is most likely to write to us.
_fbp- Identifies your browser so that Meta can provide advertising and site analytics services to the businesses that use its products. Expires after 90 days.
_fbc- The same, with the identifier Meta adds to the link when you arrive by pressing one of its ads. Expires after 90 days.
lastExternalReferrer- Left by the Meta Pixel in the browser's local storage, not in a cookie. It holds whether you arrived from Facebook, from Instagram, from another website or from none. It has no expiry date: you clear it from your browser, as explained below.
lastExternalReferrerTime- The same, with the moment it was stored.
They are Meta's cookies, not ours, even though they are set from this
domain. What they are for and their 90 days come from Meta's
cookies policy;
that _fbc holds the click's identifier comes from its
developer documentation.
Meta also uses what it receives for purposes of its own, such as personalising the ads it
shows you, and processes it partly in the United States. And it says in that policy that,
on websites that use its products, it uses cookies and receives information without any
further action from you, whether or not you have a Facebook or Instagram account. In the
pixel's documentation
it adds that the pixel relies on Facebook cookies, which let it match a website's visitors
to their Facebook accounts: those are Meta's, and the same cookies policy describes them.
Advertising also brings in those of OpenAI's pixel. They tell OpenAI which pages you open here, whether you arrived by pressing one of our ads on ChatGPT and whether you send the form, so that we know which of our ChatGPT ads bring requests.
__oppref- Holds the identifier OpenAI adds to the link when you arrive by pressing one of its ads on ChatGPT. Expires after 30 days, which start again with each click on an ad.
__obref- A randomly generated reference of your browser, for this website. Expires after 365 days.
__oaiq_consent- Holds whether the pixel may send anything, as you answered the notice. Expires after 30 days.
oaiq_consent- The same, in the browser's local storage, not in a cookie. It has no expiry date: you clear it from your browser, as explained below.
OpenAI's pixel sets them from this domain. What the first two are for and their 30 and 365
days come from OpenAI's
pixel documentation;
it does not name the other two, which we measured ourselves on 21 October 2026. When it
loads, the pixel asks bzrcdn.openai.com for its code and its settings, where
Cloudflare, which protects that address from automated traffic, sets two technical cookies
on OpenAI's domain, __cf_bm and _cfuvid. According to that
documentation, the pixel also finds details of yours on the page, such as the email or
the phone you write in the form, turns them in your browser into a code, a SHA-256 hash,
and sends that code instead of the detail, to match your request to our ad even when you
do not arrive through its link: on 21 October 2026 we saw it send the email and the phone
that way when the form was sent. OpenAI Ireland Limited receives it,
also uses it for purposes of its own and processes it partly outside the European
Economic Area, as the privacy policy explains.
Art. 22.2 of the LSSI: informed consent is required. AEPD cookie guide, May 2024, section 2.1.2 (p. 12): analytics or measurement cookies are not exempt. Section 3.1.1 (pp. 15-16): the policy must say which cookies there are, whose they are, what for, how long they last and whether there are transfers to third countries. Meta Business Tools Terms, effective 3 November 2025, section 3.d: consent, in a verifiable manner, before Meta cookies are stored on your device. OpenAI's Conversion Terms, section 2, and its Ad Tools Data Processing Addendum, section 1.3: the notices and any consent required are ours to give and obtain.
3. The Google map
In the contact section, at the end of the page, there is a Google Maps map showing where we are. Google serves it, so it loads only if you accept it, apart from analytics. Until then you see our address and a link that opens it in Google Maps, which sends nothing until you press it.
When it loads, your browser asks Google for the map, and Google receives your IP address and
the usual technical data of any web request. On 7 October 2026 we loaded it in a browser with
no previous data: it set no cookie, and it requested resources from six Google
domains: www.google.com, maps.gstatic.com,
maps.googleapis.com, places.googleapis.com,
fonts.googleapis.com and fonts.gstatic.com. If you are signed in to
Google, your browser may send it the Google cookies you already have; those are Google's, and
its own privacy policy governs them.
Google processes that data under its own privacy policy, and part of it in the United States.
AEPD cookie guide, May 2024, section 3.1.2.2 (pp. 20-22): a panel to accept or refuse by purpose, where no option comes ticked in advance and saving with none ticked is a refusal.
4. What is stored anyway, without asking you
Two things, and neither of them is a cookie. They live in the browser's local storage:
-
demarchy_consent— holds your answer to the cookie notice, one for analytics, one for the map and one for advertising, and its date. It is what stops us asking you on every page. Without it the notice would be impossible to honour. - A demo key — the pages under
/demos/are password-protected. If you enter one, a technical value is stored so you are not asked again.
Neither of them leaves your browser or reaches our servers. They are exempt because they are strictly necessary to give you a service you asked for: remembering your own decision and your access.
Art. 22.2, third paragraph, of the LSSI. AEPD cookie guide, May 2024, section 1 (p. 10): authentication or user identification cookies.
5. Your answer, and how to change it
You have not answered yet, so nothing is loaded.
You can change it whenever you like, and it costs what giving it cost: one button. If you accepted and now refuse, we stop loading Google at once, the map leaves the page, the Meta and OpenAI pixels stop sending them anything and OpenAI's deletes its cookies __oppref and __obref; you can clear the cookies Google or Meta already set from your browser, as explained below.
Your answer stands for 24 months. After that we ask again. A "no" is honoured exactly as long as a "yes": we do not come back sooner because you refused.
AEPD cookie guide, May 2024, section 3.2.8 (p. 29): good practice that consent should not last more than 24 months. Section 3.2.9 (p. 29): withdrawing consent must be as easy as giving it.
6. How to delete whatever is there
From your own browser, by clearing this site's data. In Chrome and Edge it is under Settings → Privacy and security → Browsing data; in Firefox, Settings → Privacy & Security → Cookies and Site Data; in Safari, Preferences → Privacy → Manage Website Data. You can also browse in a private window and nothing will be left when you close it.
You lose nothing by deleting it: the site will ask you about cookies again and the demo will ask for its password again.
7. The hosting
This website is served by Cloudflare. On 19 September 2026 we measured the responses from demarchy.ai and none of them carried a cookie of the server's own. Cloudflare may use a technical cookie to protect a site from automated attacks; were that to happen on a standing basis, we would say so here.
8. Where to find the rest
Who is behind this website, in the legal notice. What we do with what you write to us and what rights you have, in the privacy policy.