Cookie policy

Last updated: 1 October 2026.

This Cookie Policy explains what cookies almacamper.es uses and how you can manage them.

What cookies are

Cookies are small files stored by your browser. They can keep a session active, remember a cart or help complete a booking.

Cookies we use

We currently use technical cookies necessary to provide the service, including WooCommerce cart/session cookies and WordPress login cookies when users access their account.

During payment, providers such as Redsys/Bizum, Stripe or PayPal may use technical or anti-fraud cookies necessary to process payment securely.

Analytics and ad measurement: your choice

Optional measurement remains blocked until you choose. You can book and pay without accepting it. The panel offers three equally prominent choices:

• Reject optional cookies: we do not load Google’s measurement tags or Microsoft Clarity.
• Analytics only: you allow Google Analytics 4 to measure visits, contact clicks and paid booking deposits, and Microsoft Clarity to analyse navigation on eligible public pages, without granting Google Ads advertising measurement permissions.
• Analytics and ad measurement: in addition to analytics, you allow Google to use events and advertising click identifiers to attribute results to ads and measure performance. This permits advertising storage and data use for measurement, not personalised advertising.

WhatsApp, email and phone clicks indicate contact intent, not a message actually sent. Paid deposit events contain the order identifier, currency and deposit amount, with taxes reported separately where applicable. Later balance payments and the refundable security deposit are not counted as new purchases. Our events do not include names, emails, messages, payment keys or card details.

Google receives technical connection and browser information, identifiers and events. This measurement is not completely anonymous. We do not enable Google Signals, personalised advertising or enhanced conversions with customer data. Tags already loaded may communicate consent changes to Google.

• Analytics: _ga and _ga_* cookies distinguish browsers and retain session state. Google specifies a default expiry of 2 years, which browser restrictions and settings may shorten. Analytics cookie documentation.
• Ad measurement: when allowed, Google may use _gcl_* cookies and click identifiers such as gclid, gbraid or wbraid to associate a visit and its results with ads. How Google Ads conversion tracking works.
• Necessary preferences: ac_consent_v2 in local storage and a first-party cookie remembers separate analytics and ad measurement choices for up to 180 days; a session-storage copy lasts for that tab. These copies help retain withdrawal if a storage method fails. Previous preferences ac_consent_v1, ac_consent_revoked and ac_measurement_denied are respected during migration and removed when a new choice is saved. Previous analytics consent is never automatically converted into advertising consent or used to activate Clarity: Clarity requires a new explicit choice in the updated panel.
• Duplicate prevention: after analytics consent, the session marker ac_purchase_v1_* helps prevent repeating the same deposit event in that tab. With ad measurement permission, ac_ads_purchase_v1_* applies the same control to the Google Ads action; the transaction identifier also helps minimise duplicates at that destination.

You can withdraw all permissions or keep analytics only using Privacy / cookies in the footer. Withdrawing permission updates the consent state, removes accessible cookies for the rejected purpose and may reload the page. It does not delete data already sent. The panel warns you if the browser cannot save your choice. See Google’s privacy policy and data use on sites using its services.

Microsoft Clarity: optional browsing analytics

Only after you explicitly accept analytics in the updated panel, we use Microsoft Clarity to understand navigation through heatmaps and recordings of interactions such as clicks and scrolling. We do not load Clarity before that choice or when you reject it. Previous Google Analytics consent does not automatically activate Clarity.

Clarity is limited to public browsing pages. We exclude the cart, payment, orders, account and contact pages, signed-in visits, and addresses containing sensitive or unsupported parameters. Form fields are masked. We do not send Clarity purchase events, names, emails, messages or customer identifiers. Microsoft receives technical and interaction data and pseudonymous identifiers; this does not make the processing anonymous. We do not grant Microsoft advertising permission.

• _clck: identifies a browser to connect visits to the same site; usual expiry of 1 year.
• _clsk: groups page views into a session; usual expiry of 1 day.

Expiry may be renewed through use or shortened by your browser. See Microsoft’s cookie information and its expiry definitions. You can withdraw analytics using Privacy / cookies in the footer: we stop Clarity and remove its accessible first-party cookies. Withdrawal does not delete data already sent. More information is available in the Microsoft Privacy Statement.

Managing cookies

You can block or delete cookies through your browser settings. If technical cookies are blocked, some booking or login features may not work.

Attribution of paid booking deposits

Only with permission for ad measurement, the first-party cookie ac_ads_attribution_v1 retains a Google advertising click identifier for up to 30 days. We save that identifier and the permission with the booking so that, when payment is confirmed, the server can report the paid deposit to the same Google Ads purchase action. The order number prevents duplicate counting with the website tag. These events do not include your name, email, telephone number, address or payment keys. Withdrawing permission in this browser deletes the cookie and cancels pending server reports associated with it. A short local queue, ac_ads_revocations_v1, retries the withdrawal if the connection fails; it is used only to apply your privacy choice.