Cookie Policy

1. What cookies are

Cookies are small values stored by a website in a browser. Similar storage and access technologies can perform related functions. This policy describes the technologies currently used by this application.

2. Essential and requested-function cookies

• Supabase administrator authentication cookies — session and security functions needed when an authorised administrator signs in. Names and lifetimes are managed by the authentication system and may vary by environment.
• dmm_chat_session — a random bearer token used to return a visitor only to the public Chat conversation they started; stored for up to 30 days and created only when Chat is used. Only its SHA-256 hash is stored in the database.
• dac_public_locale — remembers EN or PL after a visitor actively selects that language; stored for up to one year.
• dac_admin_locale — separately remembers the administrator interface language after an administrator selects it; stored for up to one year.
• dmm_cookie_information_decision_v2 — stores only accepted or rejected in localStorage after a visitor explicitly chooses OK or Reject optional on the cookie information bar. It contains no identifier or personal data, is shared across EN/PL, and remains until browser storage is cleared.

3. Security and rate limiting

Public rate limiting currently uses server-side, short-lived hashed request identifiers rather than an advertising cookie. Technical logs may still contain personal information and are covered by the Privacy Policy.

4. Optional technologies and browser storage

The application does not currently activate optional analytics, advertising or cross-site tracking cookies and does not use advertising pixels. Other than the anonymous acknowledgement described above, application code does not use localStorage and does not use sessionStorage. The displayed bar is information about necessary technologies, not an optional-cookie consent banner.

5. If optional technologies are introduced

We will update this policy and assess whether consent is required before activating a new technology. Where consent is required, optional technology will remain off until the visitor makes a choice, with clear Accept Optional, Reject Optional and Settings controls. Withdrawing consent will be as easy as giving it.

6. Controls, objection and reset

Authentication storage and the Chat token are necessary only when you request those secured features. The language cookies use the current UK exception for a selected appearance preference. We provide clear information and a free, simple control below to remove both saved language preferences. You can also remove or block cookies in browser settings. Blocking authentication prevents administrator login; removing the Chat token prevents the browser from reopening that conversation; removing a language preference means the default language may appear again.

7. Contact

Questions about storage technologies or personal information can be sent to a configured contact method shown on this website or in your booking communications.