Cookie policy
Which ones there are, what they are for, and how to say no.
Last updated: 9 September 2026
One advertising cookie, if you accept it
We advertise Buildyo on Google. This cookie is what tells us whether the person who ends up writing to us through the form arrived from one of those ads, and that is the only thing it measures.
Google sets it, and it is not loaded until you accept: while you have not chosen — and also if you choose not to — this page asks Google for nothing and sends it nothing. The lawful basis is your consent, because an advertising cookie is not among those exempted by Article 22.2 of the Spanish LSSI, which is why you are asked instead of it being taken for granted.
| Cookie | What for | How long |
|---|---|---|
| _gcl_au | Telling whether the form you send arrived from a Google ad | 90 days |
If you accept it, Google knows you have seen this page: that is what lets it connect the ad with the form you send afterwards. Sending the form also passes an internal row identifier, which only serves to avoid counting the same thing twice and says nothing about you. What you write in the form does not leave here.
You can change your mind whenever you like, with the button at the foot of this page.
Behind “Sign in” there is no advertising cookie and there will not be: that promise is written into the contract signed with every developer.
The ones needed for this to work
There are two, and both are exempt from consent under Article 22.2 of the Spanish LSSI, which exempts cookies strictly necessary to provide a service the user asked for.
| Cookie | What for | How long |
|---|---|---|
| Authentication session | Keeping you signed in as you move between pages, behind “Sign in” | Until you sign out or it expires |
| Cookie choice | Remembering whether you accepted or rejected the advertising one, so you are not asked again | 12 months |
If you block the session one, you will not be able to sign in. Neither is used for anything else.
What there still is not
There is no audience analytics, ours or anyone else’s: we use neither Google Analytics nor any similar tool to measure how many people come in, where they go or how long they stay.
No equivalent technique is used either: no browser fingerprinting, and no local storage for measurement.
The technical fingerprint mentioned in the privacy policy is none of these: it is computed on our server to stop automated form submissions, it measures nothing, it never reaches your browser, and it is deleted after 24 hours.
How to control them anyway
Every browser lets you view, block and delete a site’s cookies from its privacy settings. For the advertising one you also have the button at the foot of this page, which is more direct.