COOKIES / DEVICE STORAGE

ONLY WHAT
WE NEED.

This notice explains cookies and similar browser storage used by the current LAZE website and the rule that optional tracking remains off unless valid consent is obtained.

VERSION 1.0-CePRIVACY / GDPR5 OCTOBER 2026

1. The Irish cookie/device-storage rule

Irish ePrivacy rules generally require consent before information is stored on, or accessed from, a user's device through cookies or similar technology. Limited exemptions apply, including storage that is strictly necessary to provide an information-society service explicitly requested by the user and storage used solely to transmit a communication.

If information obtained through a cookie or similar technology is personal data, the GDPR also applies to the subsequent processing. A different GDPR lawful basis cannot be used to bypass the ePrivacy consent requirement for non-exempt device storage.

2. Strictly necessary account session

When a user signs in, LAZE uses a secure session cookie named laze_session to keep the user authenticated and protect access to customer, technician and administrator areas.

  • Purpose: authentication, session continuity and access security.
  • Current design: HttpOnly, Secure and SameSite=Strict.
  • Current maximum lifetime: approximately 7 days unless the session ends earlier.
  • Consent position: treated as strictly necessary to provide the signed-in service requested by the user; it is not used for advertising or analytics.

3. Unfinished booking draft in localStorage

The booking builder uses browser localStorage under the key laze-booking-draft-v2 so an unfinished enquiry can survive a refresh or accidental tab closure. The draft can contain contact and vehicle information but intentionally excludes exact GPS coordinates.

The draft stays on that browser/device and is not sent to LAZE merely because it is stored there. After a successful Save Request operation the booking script removes the local draft. The user can also remove it through browser site-data controls. Users of a shared device should clear the draft if they do not want later users of that browser to see it.

This local storage is used only to provide the booking-draft function requested by the user and not for profiling, advertising or cross-site tracking.

4. Cloudflare security and delivery technology

LAZE uses Cloudflare for site delivery, security and backend infrastructure. Cloudflare can use technical mechanisms in connection with network security, challenge/abuse prevention and service delivery. LAZE does not intentionally configure those mechanisms to create advertising profiles.

If Cloudflare or another infrastructure provider introduces a technology outside the applicable necessary/communications exemption for LAZE's use, the site must reassess the consent position before relying on it.

5. Links, routing and third-party services

Clicking an external link, opening WhatsApp, or using a third-party service can take the user into another provider's environment where that provider applies its own cookie/storage rules. LAZE's cookie notice does not control storage placed independently by another website after the user leaves laze.ie.

Server-side route calculations do not, by themselves, authorise LAZE to place advertising or analytics identifiers on the user's device. If an embedded map or other client-side third-party feature is later added and it stores or accesses non-exempt information, it must be assessed before deployment.

6. Analytics, advertising, remarketing and conversion tracking

The Irish Data Protection Commission states that analytics cookies require consent. Targeted advertising and conversion-tracking cookies are also non-exempt. Accordingly, if LAZE later adds analytics, remarketing, advertising pixels, social-media tracking or equivalent local-storage/device identifiers, those technologies must remain disabled until the required consent has been obtained.

Consent must be freely given, specific, informed and unambiguous. Optional purposes should not be bundled into a forced acceptance, and refusing optional tracking must not prevent access to core website functions that do not need it.

7. Consent controls, withdrawal and browser controls

Where consent is used, withdrawing or changing it must be as easy as giving it. Any future LAZE consent interface must therefore provide a persistent way to revisit optional choices and must actually stop the relevant storage/processing when consent is withdrawn, subject to data already lawfully collected and any separate lawful retention basis.

Browser controls can delete cookies and local storage. Deleting laze_session will sign the user out; deleting the booking-draft key removes the unfinished draft from that browser.

Questions can be raised through the contact details in the trader-information panel or through the privacy-request form where the issue concerns personal data.