Cookie policy
What gets stored in your browser when you visit this site, who puts it there and how to remove it.
Draft of 29 July 2026. Effective date: <pedir al cliente>.
Draft document. The cookie list must be checked against the real configuration of the payment account before the site goes live.
1. What a cookie is
A cookie is a small file a website stores in your browser to remember something between one page and the next: a preference, an open session or, during a payment, a fraud check. Alongside cookies there are other storage techniques with the same effect, such as the browser’s local storage, and this policy applies to them too.
2. First-party cookies
This site is served as static pages and needs no cookies to work: there is no user session, no cart and no analytics of our own. There are no advertising cookies either, because the site shows no advertising. If a technical cookie were ever added — for example to remember your chosen language — it would be detailed in this table before being activated. First-party cookies installed as of this document: <pedir al cliente>.
The redirect behind dynamic codes installs no cookies or identifiers on the scanner’s phone either: what does get recorded is explained in what gets recorded when a dynamic QR code is scanned and detailed in the dynamic codes section of the privacy policy.
3. Payment provider cookies
The one-time payment is processed by Stripe. During checkout, Stripe may set cookies from its own domains that are strictly necessary to process the payment and prevent fraud. These are the ones it usually declares for that purpose:
| Cookie | Domain | Purpose | Declared duration |
|---|---|---|---|
| __stripe_mid | stripe.com | Fraud prevention and detection during payment | 1 year |
| __stripe_sid | stripe.com | Fraud prevention: identifies the checkout session | 30 minutes |
Names and durations are those published by Stripe and can change without notice: the current list is in Stripe’s cookie documentation. Before taking this table as final, it must be checked against what the site’s payment account actually installs.
4. Consent
Article 22.2 of the Spanish Law 34/2002 requires prior, informed consent to install any cookie that is not strictly necessary to provide the service. The payment cookies above are strictly necessary to process the payment you request, so they are exempt from consent and appear only during checkout. Since the site sets no advertising or analytics cookies, there is no cookie banner to click through: there is nothing to consent to.
5. From the browser
Every browser lets you view, delete and block cookies from its settings, usually under privacy and security. You can also use private browsing, which discards them when the window closes. Blocking all cookies affects many sites, not just this one.
6. What happens if you block them
Browsing works exactly the same: neither the QR code editor nor any of the QR code types depends on a cookie to be generated or previewed. What can fail is the payment: if the payment provider’s cookies are blocked, Stripe may reject the transaction as a fraud prevention measure.
7. Changes to this policy
If the providers, the purposes or the installed cookies change, this page is updated with a new date. The related processing of personal data is described in the privacy policy.