Cookie policy

1. Cookies and local storage are not the same thing

A cookie is a small file a site leaves in your browser and that is sent back to the server on every visit. It is the mechanism used to follow people across sites.

Local storage is different: the browser keeps a value and sends it nowhere. It stays on your device until you or the browser delete it.

This site uses both, and article 22.2 of the Spanish LSSI covers them equally, so we declare them together in the table below.

2. What exactly is stored

It depends on what you decided. The first two rows are always stored; the rest only if you accepted them.

3. How we ask for your consent

The first time you arrive, a notice appears at the bottom. Until you answer, none of the cookies that depend on your consent is installed: the factory setting is that they are all denied, not the other way round.

The notice offers three ways out: accept all, reject all, or open the panel and decide category by category. Accept and reject sit in the same place, at the same size, one click away each, because recital 42 of the GDPR requires refusing to be as easy as accepting.

The notice does not block the site. You can read every page without answering anything, and nothing is installed meanwhile. We do not use cookie walls.

Your decision is stored in your browser with its date. If we ever widen the scope of what is being consented to, that decision stops counting and you are asked again, because a yes given to a different question is not a yes to the new one.

4. What happens exactly if you reject

The Google script still loads, and we would rather say so than have you find out by reading the source. This is what Google calls advanced consent mode.

What your rejection changes is that the script is forbidden from writing anything on your device: no "_ga", no "_gcl_au", no identifier of any kind that would let it recognise you between one visit and the next. Without that identifier there is no profile, no remarketing and no cross-site tracking.

What Google does receive is a signal with no identifiers: that a visit happened, to which page, and from roughly which country. That lets it estimate how many people came through, but not reconstruct your path or add it to any profile.

If you would rather your browser did not load that script at all, any content blocker will stop it and the site works just as well. We neither detect nor penalise anyone who does.

5. Third parties

Two measure visits, and neither can identify you unless you let it. The Telegram visit notice is separate and explained at the end. The first is Google, which the cookies in the table above belong to.

That data may be processed in the United States. Google relies on the EU-US Data Privacy Framework and, failing that, on the standard contractual clauses approved by the European Commission.

Beyond Google, the site loads nothing from third parties: no external web fonts, no embedded maps, no video players from other platforms, no social buttons that track the visit. The background video and the images are served from our own domain.

The hosting provider records accesses in its technical logs, as any web server does. That is not a cookie and it is explained in the privacy policy.

The second is Vercel Inc., which hosts the site and also measures visits in aggregate. IT USES NO COOKIES AND STORES NOTHING ON YOUR DEVICE, which is why it is absent from the table and why we do not ask for your consent: it identifies a visit with a code computed on its server from technical data, and that code changes every day, so by the next day you are no longer recognisable. It tells us how many people come and to which pages, and nothing more. Since it neither stores nor reads anything on your device, it falls outside article 22.2 of the Spanish LSSI.

Separately, our server notifies us via Telegram when someone arrives at the site, which pages they open and whether they send the contact form, with the approximate country and city, the type of device, the language and the referring site. THIS IS NOT A COOKIE EITHER: it stores and reads nothing on your device, which is why it is absent from the table and does not depend on your consent. We check the IP address at that moment only to tell people apart from bots, but it is not in the notice and is not kept (our server remembers a fingerprint of the visit for 30 minutes so it isn't reported more than once), and the notices are deleted after 24 hours. The details are in the privacy policy.

6. How to change your decision or delete what is stored

In the footer of every page there is a link that says "Cookies" and reopens the panel. You can change your mind as many times as you like, and withdrawing consent is as easy as giving it, which is what article 7.3 of the GDPR requires.

Withdrawing it has no retroactive effect on what was already collected, but it stops the collection from that moment and the cookies stop being renewed.

You can also delete everything from your browser settings, under website data or privacy, or browse in a private window: what is stored is discarded when you close it. If you delete the record of your decision, the notice reappears on your next visit.

Deleting the language preference breaks nothing: the site goes back to whatever language your browser asks for, and you can pick it again from the footer.

7. Changes to this policy

If the site starts using cookies other than those declared here, or loading services from other third parties, this page is updated before that happens, the date in the header changes, and your consent is requested again.