Cookies
Dravessianluxelodge uses cookies to enhance your luxury casino experience and ensure our digital services operate with the same precision as our gaming floors.
15 May 2026. This policy explains our commitment to data minimisation and your control over essential and functional cookies.
Cookie Management & Settings
Site Banner Preferences
Use our on-site preference center to accept or decline non-essential cookies. Your choice is remembered for your next visit.
Browser Configurations
Most modern browsers allow you to block all cookies through settings. Note that disabling essential cookies may impact site functionality.
Analytics Opt-Out
You can specifically reject analytics cookies while keeping functional settings. This ensures your navigation remains private and untracked.
Third Parties, Retention & Security
We maintain the highest standards of data security to protect our guests. Cookie data is handled with precision and discarded when no longer required.
Detailed Cookie & Consent Information
This Cookie Policy explains how the Dravessianluxelodge casino hotel website operated by Dravessianluxelodge Limited, 42 Victoria Street West, Auckland 1010, New Zealand, uses browser storage and similar technologies. The policy should be read together with our Privacy Policy. The locally packaged website does not require remote advertising scripts, external font services or third-party marketing trackers to display its core content.
What cookies and browser storage are
Cookies are small data files or values that a website can ask a browser to remember. Similar functions can be provided by local storage or session storage. These technologies can remember a consent choice, maintain a user-interface preference, support security or help a service understand how it is used. Not every stored value identifies a person and not every browser-storage mechanism is technically a cookie, but we explain them together for clarity.
Strictly necessary storage
Strictly necessary storage supports functions that a visitor has requested or that are essential for security and operation. Examples include remembering whether the cookie notice has already been answered, maintaining accessibility preferences or preserving a locally created form submission. These functions do not require consent where applicable law recognises them as strictly necessary, although we still describe them transparently.
Functional storage
Functional technologies can remember optional display or convenience preferences. They are not required to read the casino website. Where consent is legally required, functional storage is activated only after the visitor makes an affirmative choice. Declining optional storage should not prevent access to public information about the casino hotel, responsible gaming, location or guest services.
Analytics
A production deployment may use privacy-conscious analytics to understand aggregate usage, such as which pages are visited, broad device categories and technical errors. Optional analytics must be configured in accordance with applicable consent rules. This static package does not load a remote analytics library by default. We do not use the casino website to build advertising profiles or to sell browsing data.
Consent under GDPR and similar rules
Where GDPR or comparable ePrivacy rules apply, non-essential cookies are used only after a valid consent choice where consent is required. Consent must be freely given, specific, informed and unambiguous and should be as easy to withdraw as it is to give. The cookie notice provides an Accept option and a Decline option, and the Cookie Policy provides a route to reopen settings.
Changing your choice
You can reopen the on-site cookie settings using the Open Settings control in the Cookie Management section. You may also clear site data through your browser. Browser menus differ by product and version, so consult the privacy or site-data section of your browser's own settings. Clearing storage may cause the casino website to ask for your preference again on the next visit.
Duration
Some browser values exist only for the current session; others may remain until a defined expiry period or until you delete them. Consent choices may be remembered for convenience and periodically requested again when the policy or purposes materially change. Locally stored form submissions remain in the browser until the user deletes them, clears browser data or the browser removes storage.
Third parties
The frontend delivered in this project has been localised so that styles, scripts, images and icons are stored inside the project. It therefore does not need third-party CDN requests to render the casino website. If a future production operator introduces a third-party processor, the relevant purpose, category and consent requirement should be assessed and this policy updated before deployment.
Do Not Track and browser signals
Browser privacy signals are evolving and are not implemented consistently across all environments. We treat an explicit choice made through our preference interface as the primary website-level instruction. Where law requires recognition of an additional valid signal, the production implementation should honour that requirement. Essential security functions may continue where they are legally permitted and technically necessary.
Security
Cookie and local-storage values should not be treated as a place to store payment-card data, passwords or highly sensitive information. The website's demonstration forms do not request payment details. Visitors should not enter unnecessary confidential information in free-text fields. We use reasonable measures to reduce the risk of browser-storage misuse, but the security of the visitor's device also remains important.
Contact and policy updates
Questions about cookie use may be submitted through the contact form. The general email is info@dravessianluxelodge.com and the telephone number is +64 9 889 2746. We review this policy when the casino website's technologies, purposes or legal obligations change. The current page should always describe the technologies actually enabled in the production version.