§Cookie policy
analytics only, only if you acceptCourtesy translation. The Spanish version is the only legally binding one; if the two differ, the Spanish version prevails. Read the binding Spanish version.
By default, no tracking cookies
When you arrive no tracking cookie is loaded. We use Google Analytics to measure visits in aggregate and Microsoft Clarity to see heatmaps and recordings of browsing, and both only if you accept in the notice that appears the first time. If you reject it — or simply ignore it — neither of the two is loaded and no analytics cookie is stored. Accepting and rejecting cost the same: one click.
Which cookies Google Analytics sets (only after accepting)
-
_gaand_ga_<id>: distinguish visitors anonymously to count visits and page views. They expire after 2 years. They are managed by Google as data processor; in Google Analytics 4 the IP address is not stored (it is used to infer the country and then discarded).
Changed your mind? Delete this site’s cookies in your browser and the notice will appear again so you can choose anew.
Which cookies Microsoft Clarity sets (only after accepting)
Clarity is used to see where people click and how far they get on a page, and to replay a visit when something is not understood. It is what tells us whether a button cannot be seen or whether a store page is abandoned halfway.
-
_clckand_clsk: anonymously identify the browser and the session in order to group the movements of a single visit. They expire after 1 year and 1 day respectively. They are managed by Microsoft as data processor.
What Clarity does NOT take from here: we have strict masking enabled, so all the text of the page is replaced by blocks before leaving your browser. In the recordings not a single code, email or anything you type in the search box can be read: only the shape of the page and where you move. And it is not loaded at all if you have rejected the notice.
Local storage (this is not tracking)
We keep a few things in your own browser that do not leave your device and do not
identify you: your favourites, whether you have already reported an offer that does not work, your
choice about cookies, which of the two versions of the notice you were shown and, if you have ever
entered with ?interno=1, the mark that makes your visits not be counted. They are not sent to
any server.
A visit counter, without cookies
Apart from Google Analytics, we count visits on our own and without any cookie. Each time a page is opened we add one to three counters: the day’s, the page type’s (front page, store page, category…) — and on merchant pages, that merchant’s — and whether cookies have been accepted or not. And when someone copies a code, reveals a referral, shares or clicks an offer link, we add one more to the counter of that action and to that of that offer — that is how we know which coupon is of any use. That is all that is stored: numbers. There is no identifier, no IP address, no session, no way of knowing that two visits are from the same person. It does not read or write anything on your device and stores nothing that identifies you: that is why we do not include it in the cookie notice. The counters live on our own infrastructure (Cloudflare), without any third-party analytics tool, and delete themselves after 400 days.
It exists for statistical honesty: since Google Analytics is only loaded if you accept, its numbers are those of part of the people. This counter tells us how many people we are talking about, without following anyone.
When leaving for a store
When you click an offer link you leave for the store’s website, which will have its own cookies and policies, already outside our control. More detail in privacy.