Privacy policy
Last updated: 21 October 2026
This page is the second layer of the data protection information: the summary sits next to the form's button, and the detail is here. Six things happen here and nothing else: the contact form, the conversation on WhatsApp if you write to us there and, only if you accept each of them, the measurement of visits with Google Analytics, the Google map of where we are, the Meta Pixel, which measures our ads, and OpenAI's pixel, which measures those on ChatGPT. Two more do not happen on this website but are explained here: the forms of our ads on Facebook and Instagram, if you fill one in, and, if you are a client, when a project closes we invite you to review us on Trustpilot.
Art. 11.1 of the LOPDGDD, which allows the basic information to be given when the data is collected, pointing to an electronic address that gives simple and immediate access to the rest. Art. 12.1 GDPR: concise, transparent, intelligible and easily accessible.
1. Who is responsible for your data
- info@demarchy.ai
For the Meta Pixel, if you accept it, we answer together with Meta Platforms Ireland Limited, as section 6 explains. For OpenAI's pixel, if you accept it, OpenAI Ireland Limited answers for what it does with what it receives, as a controller in its own right, and we for what we do, as section 6 also explains. For the forms of our ads on Facebook and Instagram, Meta answers for what it does with them and we for what we do. Who Meta is and how to contact it, in its privacy policy.
No data protection officer has been appointed.
Art. 13.1 a) and b) GDPR. Art. 11.2 a) of the LOPDGDD. Art. 26 GDPR: joint controllers.
2. What data we process
From the form, what you type:
- a name, whichever you care to give us;
- the name of your company;
- an email address and a WhatsApp number, so we can reply;
- if you like, the text in which you tell us about your process.
If you are about to type someone else's data into that text, please don't: a first conversation does not need it.
And, if you came from one of our ads, the campaign written into the ad's link: its name, the particular ad, the keyword of ours that matched your search, where it ran and what kind of ad it is, for example "google" and "cpc", pay per click. It travels with the form if you send it from the page the ad brought you to. Its keyword alone goes at the end of the message the WhatsApp button types for you, where you see it before sending and may delete it. And Cloudflare, which hosts this website, notes your arrival, whether you accept analytics in the cookie notice, whether you press the WhatsApp button and whether you send the form or its mail fails to go out, with the campaign, the ad, the keyword, the page, the country, whether it is a phone and whether a robot asked for the page, without your IP address or anything you write. Presses of the WhatsApp button and forms, sent or failed, are noted so even when you did not come from an ad, without a campaign. Nothing is stored on your device for it. It names the campaign, not you.
From WhatsApp, if you write to us from the button on this website: your number, your profile name and the messages you send us. The button goes through our website, which notes the press as said above, and opens WhatsApp with a message already typed; nothing you write reaches us until you send it. The press also reaches our commercial records, with the page, that message and the ad's campaign, and nothing of yours: to know which ad the conversation that follows it comes from.
From analytics, and only if you have accepted the cookies: which pages you see, for how long, how far down you go, which links you press, whether you start filling in the form, from what kind of device, in which language, from which country and which site you arrived from, and whether you send the form or press the WhatsApp button, without anything you write. Google also collects your IP address to work out that approximate location, and does not show it to us. We see aggregate numbers, not people.
If you do not accept, none of that is collected, because Google's code is never even loaded.
From the map, and only if you have accepted it: when your browser loads it, Google receives your IP address and the technical data of the request. That reaches Google, not us: we receive nothing from the map.
From the Meta Pixel, and only if you have accepted advertising: which pages you see and whether you send the form or press the WhatsApp button, without anything you write. The pixel itself also sends Meta, according to Meta, what any web request carries, such as your IP address, your browser, the page and the one before it; its own id and the Meta cookie; the buttons you press, with their labels; and the names of the form's fields, not what you type into them. Meta says its cookies let it match a website's visitors to their Facebook accounts. If you do not accept, the pixel is never even loaded.
From OpenAI's pixel, and only if you have accepted advertising: on every page you open, its address without what follows the "?", a randomly generated reference of your browser and, if you arrived by pressing one of our ads on ChatGPT, that click's identifier; and, if you send the form, that you sent it, with your email and your phone turned in your browser into a code, a SHA-256 hash, instead of written out. As with any web request, it also receives your IP address and your browser's details. If you do not accept, the pixel is never even loaded.
From Meta's forms, if you fill in one of our ads' forms inside Facebook or Instagram: what that form asks you for and you choose to send us, such as your name, company and email address. Meta collects it on its platform and passes it to us.
If you are a client, when a project closes: your name and email address, and the email itself with which we close the work, which copies Trustpilot in blind copy so that it invites you to review us.
Art. 13 GDPR, which governs data obtained from the data subject. The individual cookies and their lifetimes are in the cookie policy.
3. What we use it for
The form: to read your request, answer you through whichever means you gave us and, if it makes sense, arrange a call. You are not added to any mailing list, and we send no commercial messages you did not ask for. WhatsApp, for the same.
Analytics: to find out whether this website is any use. How many people come in, which pages they read, which nobody reads, and how many visits end in a form sent or a WhatsApp. We did not know that until now, and a page cannot be improved without knowing it.
The campaign: to know which ads bring us requests and which do not.
The map: to show you where we are.
The internal notice: so that whoever answers you knows the moment you have written to us, through the form, on WhatsApp or through a Meta form, and answers you as soon as possible.
The Meta Pixel: to 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.
OpenAI's pixel: to know which of our ChatGPT ads bring requests.
Meta's forms: for the same as this website's form, to read your request, answer you and, if it makes sense, arrange a call.
Trustpilot: to ask for your opinion of the work, with the same invitation every client of ours gets. Whether you write it is up to you.
Art. 13.1 c) GDPR. Art. 11.2 b) of the LOPDGDD.
4. On what legal basis
The form: steps taken at your request before entering into a contract. You write to find out whether we can help and what it would cost, and that is what precedes a possible contract. This is article 6.1 b) GDPR, which makes processing lawful where it is "necessary for the performance of a contract to which the data subject is party or in order to take steps at the request of the data subject prior to entering into a contract". WhatsApp, the same.
Analytics: your consent, article 6.1 a) GDPR, the one you give or refuse in the cookie notice. You may withdraw it whenever you like, and withdrawing it does not affect what was processed while it stood.
The map: your consent too, given or refused in the same notice apart from analytics, and withdrawn the same way.
The Meta Pixel: your consent too, article 6.1 a) GDPR, given or refused in the same notice apart from the rest, as article 22.2 of the LSSI asks for its cookies, and withdrawn the same way.
OpenAI's pixel: the same consent, the one you give or refuse for advertising, and withdrawn the same way.
Meta's forms: the same as this website's form, steps taken at your request before entering into a contract, article 6.1 b) GDPR.
Trustpilot: our legitimate interest in knowing what our clients think of the work we did for them, article 6.1 f) GDPR. You may object: just tell us and the invitation is not sent.
The campaign: our legitimate interest in knowing which ads bring us requests, article 6.1 f) GDPR. You may object: just tell us and we do not use it.
The internal notice through Telegram: our legitimate interest in answering you as soon as possible, article 6.1 f) GDPR. You may object: just tell us and we no longer tell ourselves of you that way.
Your name, company, email address and WhatsApp number are needed in order to answer you: without them we cannot. The text is optional. Analytics is needed for nothing of yours: if you refuse it, the site works exactly the same and you lose no feature. Nor is the map: our address is written next to it, with a link to Google Maps. Nor are the Meta and OpenAI pixels: refuse them and you lose nothing.
Art. 6.1 a), b) and f) GDPR. Art. 13.1 c) and d) GDPR: the legal basis and, where it is a legitimate interest, which one. Art. 13.2 b), c) and e) GDPR: the right to object and to withdraw consent, and whether you are obliged to provide the data. Art. 21 GDPR.
5. How long we keep it
Your message lives in our mailbox and in our commercial records, where we copy it from that mailbox: this website stores nothing you send. We keep it for one year from the last message between us, and then delete it. If a client relationship comes out of it, it is kept while that lasts and afterwards for the periods tax and commercial law require.
The WhatsApp conversation lives on the phone of whoever answers you and on the server of ours that reads it, and we copy it into our commercial records when it is with a law firm or company we are already in touch with, or when your first message names Demarchy, as the message the button on this website types for you does. We keep it on the same terms as a message from the form.
The Telegram notice stays in the internal group of ours where it reaches us, and we delete it on the same terms as a message from the form.
The Trustpilot invitation: Trustpilot deletes the blind-copy email after 30 days, and the rest of the invitation data after two years at most. If you write the review, you publish it from your own Trustpilot account and it is governed by Trustpilot's privacy policy.
The analytics data is kept by Google, not by us. The period set on our property is 14 months from the last visit. The cookies behind it expire after two years, and your browser cuts that down further: Chrome to 400 days, Safari to 7 if you do not come back.
From the map we keep nothing. What Google keeps is governed by its own privacy policy.
The pixel's data is kept by Meta, not by us: its terms let it retain it for a maximum of two years. The cookies behind it expire after 90 days.
The data of OpenAI's pixel is kept by OpenAI, not by us, for as long as it needs for its services and its legitimate purposes, under its privacy policy, which sets no period for it. The cookies behind it expire after 30 and 365 days.
What you send in one of Meta's forms we download from Meta, which makes it available for 90 days from when you send it, and we keep it on the same terms as a message from this website's form. What Meta keeps is governed by its own privacy policy.
Art. 13.2 a) GDPR: the storage period, or the criteria used to determine it.
6. Who else sees it
We sell your data to no one. Only if you accept advertising do the pixels pass what they collect to Meta and to OpenAI, which then both also use it in their own right, as explained below. These suppliers of ours handle it:
- Google, by three separate routes: the form becomes an email that arrives in our Google Workspace mailbox and stays there; if you accepted analytics, Google Analytics collects and processes the visits; and, if you accepted the map, Google Maps receives your IP address when it loads.
- Cloudflare, because it serves this website and the form submission passes through its servers.
- WhatsApp Ireland Limited, if you write to us on WhatsApp or we write to the number you give us in the form: it provides the WhatsApp Business service we answer you with. As a WhatsApp user, what you do there is also governed by its own privacy policy.
- Telegram, through which we tell ourselves of every request that comes in, in an internal group of ours: it receives your name, your company, your phone and your email.
- Trustpilot A/S, of Copenhagen, only if you are a client: it receives the blind-copy email and sends you the invitation.
- Meta Platforms Ireland Limited, by two routes: if you accepted advertising, it receives what the pixel sends; and, if you fill in a form of our ads on Facebook or Instagram, it collects it and passes it to us. As a Facebook or Instagram user, what you do there is also governed by its own privacy policy.
- OpenAI Ireland Limited, only if you accepted advertising: it receives what OpenAI's pixel sends.
All of them act as processors: they process the data on our behalf and on our instructions, under the written contract the GDPR requires. The map is the exception: Google serves it as a service of its own, under its own privacy policy, and not on our behalf. Meta is the other: for the forms it is a controller as we are, each for its own part. And Telegram, the third: it offers no processor contract and processes the notices as a controller, under its own privacy policy. For the pixel, it acts as our processor to measure the results of our ads; for collecting the data on this website and transmitting it to Meta, Meta Ireland and we are joint controllers; and what it does with the data afterwards it does as a controller in its own right. And OpenAI, the fourth: for what it receives from its pixel it is a controller in its own right, neither our processor nor a joint controller.
That joint controllership is governed by the Controller Addendum to the Meta Business Tools Terms, which we have accepted to share out what the GDPR requires of the joint processing. In essence: it falls to us to give you this information, and Meta Ireland is the one responsible for your rights of access, rectification, erasure, restriction and portability over the data it stores afterwards. You can exercise them against Meta directly, or with us, and we pass your request on. Meta receives that data, under its terms, to target and deliver ads, ours included, to people who may be interested, to reach people with commercial messages on Messenger and other Meta products, and to personalise what it shows on and off its products. How it processes it, on what legal basis and how to exercise your rights against Meta, in its privacy policy.
So says OpenAI's Ad Tools Data Processing Addendum, which is accepted by using its pixel. Under its Conversion Terms, OpenAI uses what it receives to give us reports, to create audiences for us, to improve, optimise, measure and deliver its services, and to develop and improve its products; we may not use those reports in a way that allows anyone to be identified. Its privacy policy says that what it receives from advertisers also helps it show more relevant ads to people who use ChatGPT for free or on the Go plan; and the pixel's documentation, that it does not currently use the pixel's data to personalise what it shows each person. How it processes your data and how to exercise your rights against OpenAI, in its privacy policy.
Google LLC and Cloudflare, Inc. are United States companies and part of the processing happens there. WhatsApp Ireland transfers the data to WhatsApp LLC and Meta Platforms, Inc., in the United States, under the EU-U.S. Data Privacy Framework. Meta Ireland transfers what it processes from the pixel as our processor to Meta Platforms, Inc., in the United States, under the same Framework; what it processes in its own right, the forms included, it stores in data centres in several countries under its own privacy policy. OpenAI Ireland processes what it receives on servers outside the European Economic Area, the United States included, and, for countries without an adequacy decision of the European Commission, relies on the standard contractual clauses it approved, under its privacy policy. Telegram stores the data of accounts from the European Economic Area in data centres in the Netherlands, and transfers it to its companies in the British Virgin Islands and Dubai under standard contractual clauses approved by the European Commission. Trustpilot does not take it outside the European Economic Area or the United Kingdom without the safeguards the GDPR requires.
Art. 13.1 e) GDPR (recipients) and 13.1 f) (transfer to a third country and safeguards). Art. 28.3 and 28.9 GDPR: the processor is bound by a contract, which shall be in writing. Art. 26.2 GDPR: the essence of the arrangement between joint controllers, made available to the data subject. OpenAI's Conversion Terms, sections 2, 3 and 5; its Ad Tools Data Processing Addendum, sections 1.1, 1.3 and 3.2.
7. What you can require of us
You may ask us for access to your data, its rectification or erasure, the restriction of processing, the portability of the data, and you may object to the processing. And you may withdraw your consent to analytics, the map or advertising whenever you like, from the cookie policy.
Your rights over what Meta processes in its own right, such as the forms on Facebook and Instagram or what it keeps from the pixel, you can also exercise against Meta directly, as its privacy policy explains. And those over what OpenAI keeps from its pixel, against OpenAI, at privacy.openai.com or at dsar@openai.com, as its privacy policy explains.
Write to info@demarchy.ai. It costs nothing and we answer within one month of receiving it. If we do not attend to you, or you dislike how we do it, you can complain to the Spanish Data Protection Agency: www.aepd.es.
Art. 13.2 b) GDPR (the rights), 13.2 c) (withdrawing consent) and 13.2 d) (complaint to a supervisory authority). Art. 12.3 GDPR (one month) and 12.5 (free of charge). Art. 11.2 c) of the LOPDGDD.
8. Automated decisions
There are none. A person reads your message and a person answers it. Nothing you tell us is used to score you, and of the analytics we see only totals: we build no profile of you and do not recognise you from one visit to the next. For the Meta Pixel: on our behalf, Meta links your visit or your request to the ad of ours you were shown before, to tell us which ads bring requests; we may use those reports only on an anonymous, aggregated basis. What Meta does in its own right with what it receives, such as deciding whom it shows ads to, its privacy policy explains. For OpenAI's pixel: OpenAI links your request to the click on our ChatGPT ad you came from, to tell us which ads bring requests; we may not use those reports in a way that allows anyone to be identified. What OpenAI does in its own right with what it receives, its privacy policy explains.
Art. 13.2 f) GDPR.
9. Cookies
Which cookies there are, which need your permission, how long they last and how to change your answer, in the cookie policy.
Art. 22.2 of the LSSI.