Cookie Policy
Last updated: October 9, 2026
This Cookie Policy explains how small browser files and similar technologies work and clarifies which of them are used by the current Caldorqessa Grand website. It supplements our Privacy Policy.
The supplied static pages do not contain a marketing pixel, analytics library, visitor-recognition identifier, advertising network code or cookie-based reservation system. No non-essential cookie consent is requested because the delivered frontend does not set such cookies.
1. What cookies are
A cookie is a small text item a website can ask a browser to store and return during later visits. Similar techniques include localStorage, sessionStorage, tracking pixels and scripts that recognize a browser across visits. These technologies can be useful for session security or preferences, but they can also be used for measurement or advertising. Their purpose and configuration matter.
2. Cookies used by this version
The website frontend has no code that creates analytics or advertising cookies and no optional tracking consent switch. Its main pages, accommodation information, experiences and legal information can be read without an account. The responsive menu does not depend on cookies or persistent browser storage.
This describes the files provided for the website. The operator must review the deployed host configuration before asserting that a live domain never creates a cookie; some hosting, load-balancing or security systems may use strictly necessary identifiers.
3. Strictly necessary functions
A server may use strictly necessary session or security mechanisms to deliver pages safely, limit malicious requests or preserve technical stability. Such mechanisms must be restricted to their essential purpose. Whether any are present on the live site depends on the production host and its settings.
The local legal-entity information is loaded from an ordinary local configuration file and is not a visitor identifier or tracking request.
4. Preferences and navigation
Opening and closing the mobile menu, following local navigation links, visiting image galleries and using accessibility controls do not store preferences in cookies. Menu state is temporary and resets on navigation. No preference cookie is currently needed for these interactions.
5. Analytics and performance tracking
There is no installed browser-side analytics service in this static version. A server may produce ordinary access and error logs, which are distinct from cookies and may still contain technical personal data such as IP addresses. See our Privacy Policy for the purposes, safeguards and rights relevant to such data.
If analytics are added in the future, this policy should be updated to identify the provider, identifiers, retention and legal basis, including a consent choice where required.
6. Advertising and third-party embeds
The delivered website does not embed social media feeds, advertising pixels, advertising iframes or remote font providers. A social preview image stored locally may be shown by messaging applications when someone shares a link, but that does not create an advertising cookie in your browser from this website.
Links to independently operated websites, if added in the future, may be governed by their own policies after you navigate away.
7. Your browser choices
Most browsers let you view, remove and restrict cookies and site storage through privacy or site-settings menus. You can also delete existing site data in the browser. Blocking essential site functions may affect sites that genuinely require them; the current informational pages do not depend on optional cookies.
Browser settings cannot remove records already retained in server logs or copies of emails you have sent. Contact us separately for rights requests concerning that information.
8. Consent and withdrawal
Where optional cookies or similar technologies require consent, an operator must provide clear notice and a genuine way to decline them before they are used. Such a mechanism is not displayed now because the supplied frontend has no optional trackers.
If optional tracking is introduced, a user should be able to withdraw consent as easily as it was provided; this policy and the actual interface would need to be revised before deployment of those technologies.
9. Retention periods
No analytics or advertising cookie lifespan can be specified for the present frontend because those cookies are not installed. A future essential cookie, if used by a deployed host, should be disclosed with its purpose and actual expiry.
Ordinary browser cache files such as locally served styles, scripts and images are not the same as a tracking cookie. Their lifetime depends on HTTP caching headers chosen by the hosting server.
10. Local fonts and image resources
The site loads its frontend from project files instead of external content-delivery services. The photographs are supplied as WebP images and icons and previews are local. No remote font download is required to use the pages; browsers may use their installed fonts to render the design.
11. Privacy legislation
Depending on a visitor’s location and applicable law, rules may arise under Canadian privacy legislation, including BC PIPA and PIPEDA where applicable, or the EU/UK data protection and electronic-communications rules. This page is intended to describe the real technical behaviour, not to replace notices that may be required after production integrations change.
12. Questions, changes and contact
If the website’s technical features or hosting configuration change, we will review this policy and update the date at the top. To ask whether the live site uses a particular identifier or to raise a privacy concern, contact the guest relations address listed on the Contact page.
Responsible organization: . Contact address: .