Your browser storage choices
What a browser preference remembers
A cookie is a small value that a site asks a browser to keep and return on later visits. Similar browser facilities, including local storage, can retain values too, but they are distinct mechanisms with different access and lifetime rules. This site’s observed consent preference is a first-party cookie. It records whether optional cookies were accepted or rejected so the shared consent interface can remember that choice.
The recorded values are “granted” and “denied”. They represent the visitor’s selection, rather than a profile of browsing activity. The inspected site storage for this policy is limited to the one consent cookie listed below. No analytics or advertising storage is declared here, and the consent preference is not mirrored into local storage. This distinction matters: a general description of browser features is not an assertion that this site uses each feature.
The consent preference inventory
The inventory describes the observed consent record and its purpose. It is set by the site for its own domain, rather than by a third-party provider. The duration is expressed in seconds in the underlying setting and is equivalent to 300 days.
The preference uses the root path, so it applies across the site. Its SameSite setting is Lax, and it is marked Secure when served over HTTPS. There is no second key or local-storage copy in the inspected consent function. These attributes describe the preference mechanism; they do not imply additional tracking or identify other storage.
Keep this inventory current
This inventory is effective 18 November 2026. It should be reviewed whenever the consent mechanism or the browser storage it uses changes. Before adding optional technologies, the site should update this inventory and explain the purpose and choice associated with each addition in the consent interface. A description of a possible future change is not a statement that such storage is currently active.
Maintaining an accurate list means checking the implemented preference behaviour rather than inferring storage from a general browser capability. Any change to the cookie name, provider, duration, attributes, or purpose should be reflected here. If the site begins using a separate storage mechanism, that use should be documented distinctly so readers can tell it apart from the consent cookie.
Remove preferences using your browser
Browser menus differ, but most provide privacy, site-data, or cookie controls. Look for the stored data associated with australiaplayvista.com and remove that site’s cookies to clear the remembered consent choice. Clearing cookies can make the consent panel appear again on a later visit, because the browser no longer has the saved “granted” or “denied” value. Removing site data may also affect other preferences the browser has kept for that site.
Local storage is a separate browser facility and can be managed separately from cookies. This consent contract does not mirror the choice into local storage, so clearing local storage alone does not remove the consent cookie. Browser labels and steps vary by product and version; consult the browser’s own help for the exact controls rather than relying on a universal menu path.
You may also configure a browser to block cookies or clear them automatically. If the consent cookie cannot be retained, the site may be unable to remember a selection and can ask again. Blocking storage is a browser-level choice and this page cannot change those controls for you.
Ask about a browser preference
For questions about this inventory or the consent preference, contact GamingPlatform Ltd at [email protected] or call +611315550824. The listed postal address is 27 George Street, Edinburgh EH2 2PA, Australia. These are the site’s supplied contact channels; this policy does not assign the enquiry to a named privacy officer.
You can also send an enquiry through the site’s contact page. Include enough detail to identify the browser preference you are asking about, but avoid sending passwords or other sensitive account credentials in an ordinary message. The contact page is the appropriate route for a follow-up about the operation described here.