This is a translation. In case of discrepancy, the Spanish version prevails.
We do not add analytics or advertising tools to this website. We use the technical cookies and storage explained here, all our own; Stripe also takes part in the payment, with its own (third-party) cookies, even though it sets some of them under this website’s domain.
The ones we use
"__Host-sesion" or "sesion": let staff sign in to management and the access app. They expire on sign-out or after 14 hours; while in use, they can be renewed for up to 7 days after sign-in.
"__Host-reto" or "reto": bind the staff email sign-in code to the browser. The cookie lasts one day, but the code is valid for only 10 minutes.
"retencion_mesa": recognises this browser so your table or place can be held temporarily while you complete your booking. The cookie lasts one day; the table is held only for the time shown on the form.
"pendiente_pedido_…" and "pendiente_reserva_…": remember a pending purchase or booking when you return from payment and help prevent duplicates. They expire within 62 minutes at most.
On the protected preview website, "cocoa_pase" lets you reach the username and password prompt. It lasts 30 days and does not replace those credentials.
"cocoa-sugerencia-idioma": is kept in local storage so the suggestion to use another language is not repeated. It remains until you clear that storage and does not contain your purchase details.
"cuenta-recargas": only while an event page shows the countdown to tickets going on sale. It is kept in the tab’s storage (deleted when you close it) so that the page does not reload more than three times a minute. It does not store your data.
In addition, when you open the page of your purchase, ticket or booking, your browser saves the link in its local storage, so that it can show it to you in "My tickets" without asking you for anything, and a copy of those pages (with their styles, fonts and images) so that you can show them at the door without a connection; when you open "My tickets", a copy of that page is saved too. It is not sent anywhere. One day after the event the copy is no longer shown, and the link and the copy are deleted the next time you open this website in that browser (nothing can be deleted while the browser is closed). You can remove them sooner with "Remove from this phone", in "My tickets". Without a connection you see what was there the last time you opened the page with a connection: if a ticket is cancelled afterwards, you will not see it until you are back online.
Paying with Stripe
Integrated payment loads Stripe.js; if you continue on Stripe’s page, its services also take part in payment. Stripe uses cookies and similar technologies to manage payments, authenticate you and prevent fraud. Its documentation includes "__stripe_mid" (1 year), "__stripe_sid" (30 minutes) and "m" (2 years).
The cookies used depend on the payment mode and browser. If Link is available, it may also use storage to recognise a session or remember preferences. See Stripe’s policy and cookie list for the current purposes and durations.
How to remove them
You can delete or block them in your browser settings. You can browse the website without them, but blocking technical cookies may prevent table bookings, recovery of a pending purchase or sign-in to the staff apps.
Last updated: 25 October 2026.