Cookie Policy

1. Purpose

This Cookie Policy explains how morquellianprestigestay.com uses cookies and similar browser technologies. It should be read with the Privacy Policy. The website is designed to minimise unnecessary tracking and to use only technologies supporting legitimate functions unless optional tools are introduced with appropriate notice and consent.

Cookies are small text records stored through a browser. Similar technologies may include local storage, session storage and comparable identifiers. Their legal treatment depends on purpose and jurisdiction.

This provision applies to information connected with the casino experience described on this website.

2. Current approach

The website operates primarily with local assets and limited dependencies. Basic navigation, styling and the contact interface do not require advertising cookies. A local JSON file displays legal company and address information consistently and does not require a tracking cookie.

If a future third-party feature stores non-essential identifiers, the provider notice and any legally required consent mechanism will apply before optional activation.

Where a casino service is subject to a separate venue notice, that notice should be read together with this policy.

3. Strictly necessary technologies

Strictly necessary technologies support functions explicitly requested by a visitor or essential for security, navigation and basic operation. Depending on deployment, this can include session controls, load balancing, fraud prevention or security protections.

Where a technology is strictly necessary, consent may not be required under some regimes, but transparency obligations can still apply.

References to the casino describe the on-premises gaming and entertainment context of Morquellianprestigestay.

4. Preference technologies

Preference technologies may remember language, interface or accessibility choices. The current website does not need broad profiling to preserve basic choices. If optional preference storage is introduced, this policy will be updated with purpose and duration.

A casino-related enquiry may require additional verification where law, safety or venue rules require it.

5. Analytics

Analytics can help understand aggregate performance, device types, loading issues and popular content. We do not describe analytics as necessary merely because it is commercially useful.

If non-essential analytics is introduced, we will assess prior-consent requirements, data minimisation and relevant provider and retention disclosures.

Information generated through a casino booking or guest request is handled only for legitimate operational purposes.

6. Advertising and profiling

Core website information does not require behavioural advertising cookies. Future retargeting or cross-site profiling technologies will be treated as optional where applicable law requires consent. Refusing optional advertising should not block unrelated general information.

The casino context does not reduce any privacy, consumer or accessibility rights that apply to a visitor.

7. Consent and withdrawal

Where GDPR or another rule requires consent for non-essential storage or access on a device, consent must be freely given, specific, informed and affirmative. Pre-ticked acceptance is not treated as valid consent.

Visitors should be able to reject non-essential categories and later withdraw consent as easily as it was given.

Any casino promotion shown on the website remains subject to eligibility, availability and applicable law.

8. Browser controls

Most browsers allow users to view, delete or block cookies and site data. Blocking all storage can affect authenticated sessions or saved preferences on websites generally. Browser instructions vary by product and version.

Where a legally binding browser privacy signal applies to our processing, we will assess and honour it as required.

A casino guest may contact us using the details below about this policy or service.

9. Third-party embedded content

If a page later embeds content supplied by another provider, loading it can disclose technical information such as IP address, browser information and the requested page. A provider may independently use cookies or similar technologies.

We seek to avoid unnecessary third-party dependencies and, where consent is required, optional content should remain blocked until the required choice is made.

We apply this policy consistently across hotel, entertainment and casino-related website interactions.

10. Duration

A session cookie normally expires when a browser session ends while a persistent cookie remains until expiry or deletion. Duration should be proportionate to purpose. If optional persistent cookies are introduced, their purpose and expected lifetime will be disclosed.

The casino sections of the website are intended for adults and may include age-related access information.

11. Cookie-derived data

Depending on technology, data may include an identifier, timestamps, page paths, device information, language settings, referral information or security events. Collection is limited to what is relevant.

Cookie data linked to an individual may be personal information under Australian law or personal data under the GDPR; the Privacy Policy explains broader rights and safeguards.

Nothing in this policy permits casino activity that is prohibited by applicable Australian or Victorian law.

12. Security

Security technologies may protect against automated abuse, malicious requests, unauthorised access or service disruption. Controls should be proportionate and avoid unnecessary collection where feasible. Security records may be kept for a limited period for incident response or legal claims.

Where casino operations involve a regulated third party, that party may provide its own legally required notices.

13. Your rights

Depending on applicable law, rights may include access, correction, deletion, objection, restriction, portability and withdrawal of consent under the GDPR, and access or correction rights under Australian privacy law. We may verify identity before disclosing personal information.

The casino venue context may involve security and safety measures that are explained where required by law.

14. Changes

We may change website technologies for performance, security or service improvements. Before introducing a materially different optional tracking purpose, we will assess updated transparency and consent needs. Publication of a new policy does not itself create valid consent where affirmative consent is required.

Website content about the casino is informational unless a specific service is expressly offered for booking.

15. Questions

Contact us with the page and approximate time of an interaction if you have questions about browser storage, optional consent or a technical component. For broader personal-information issues, refer to the Privacy Policy.

Questions about a casino-related service can be directed to the contact details stated in this policy.

16. Technology inventory and governance

We periodically review technologies loaded by the website to identify their provider, purpose, whether they store or read information on a device, whether they transmit data to another party and whether they are necessary for a function requested by the visitor. This review helps prevent obsolete scripts, duplicate tags and unapproved trackers from remaining in production. New optional technologies should be assessed before deployment rather than being added first and documented later.

17. Local storage and session storage

Web storage technologies can hold data in a browser without using a traditional cookie. Session storage is generally scoped to a browser tab or session, while local storage can persist until it expires through application logic or is deleted. Where these technologies are used for a purpose that is legally treated in the same way as non-essential cookies, the same transparency and consent principles apply. We do not use a different technical label to avoid an applicable consent requirement.

18. Consent records

Where consent is required, a site may need to retain a limited record showing that a choice was made, which categories were accepted, the policy version presented and when the choice occurred. Such a record should contain no more information than reasonably necessary to demonstrate and honour the preference. Consent records are not a licence to expand tracking beyond what the visitor was told at the time of the choice.

19. Updating preferences

If optional categories are introduced, a preference control should allow visitors to revisit their decision without searching through unrelated pages. Withdrawal should stop future use of the relevant optional technology as soon as reasonably practicable. Previously stored identifiers may also need to be deleted or disabled depending on technical capability, the provider involved and the requirements of applicable law.

20. Deployment and testing

Before website changes are released, technical testing should confirm that necessary resources still load, optional tags do not activate before any required consent, preference choices persist for an appropriate period and withdrawing a choice has the intended effect. Testing should include common desktop and mobile browsers. A configuration error that causes an optional tracker to fire too early should be treated as a compliance issue and corrected rather than merely described in policy text.

21. Data minimisation and retention

Technical identifiers should not be retained longer than necessary for their stated purpose. Security data may require a different retention period from preference data, and aggregate performance statistics may be retained differently from identifiable event logs. When an identifier is no longer needed, it should be deleted, rotated or de-identified as appropriate. Retention decisions are reviewed when a provider, purpose or legal requirement materially changes.