Privacy and cookies

Publisher and privacy contact

Bonus Marquee publishes this casino offer catalogue, and this page describes what the site itself does with a visit. The answer is short: first-party analytics on the site’s own domain, a partner gate cookie, an age-notice entry, and the standard workings of a web server delivering pages. Questions about any of it go to [email protected], with the page and the browser behaviour in question. The publisher holds no casino accounts, no balances and no play history, so there is nothing of that kind to ask about here; the account questions a casino answers sit with the casino’s own support.

Visit attribution and the affiliate gate

The partner gate cookie belongs to this site’s own domain, a first-party cookie with one job. On a visit it stores the values that describe the arrival, the channel, the source and the referring host, and when you click a “Get bonus” button, the gate passes those values to the casino’s offer page so the visit lands where it started. The cookie carries visit values only: it holds no name, no account and no play detail, because the site never receives those. The cookie lasts up to 24 hours; a later attributed arrival may update it, and clearing the browser’s cookies removes it. What the casino does after the click belongs to the casino: its own pages describe its data handling, and the account you open there stays between you and the operator.

Age-notice acceptance for 30 days

The first visit opens the age notice, and accepting it, with the “I am 18 or over” button, stores that acceptance in the browser’s local storage. The site then keeps the notice away for 30 days, and when the period ends the notice returns and asks again. The entry stays in the browser: it names the acceptance and nothing more, and clearing the site’s local storage in the browser settings brings the notice straight back. The 30-day period is the only clock the entry keeps, a fresh acceptance on the next visit starts it again, and the notice itself carries the support route for anyone under the age rule. The age rule behind the notice belongs to casino play itself, and support for keeping play in control sits on responsible gambling.

Analytics and actual storage settings

Visits are measured by first-party analytics served from the site’s own domain, and no advertising network or social pixel follows the visit. The browser also keeps the gate cookie and the age-notice acceptance, both removable there. The pages load their own styles, scripts and images from the site’s own domain, and the partner button leaves only when you click it. Fonts arrive from the site’s own files as well, so a visit opens connections to this domain and, after a partner click, to the casino’s domain, and to nothing else. Browser settings control the rest: block first-party cookies and the gate keeps no attribution, clear local storage and the age notice returns on the next visit. The site stays readable either way.

Data enquiries and retention

Privacy questions reach the publisher at [email protected]: what a page stores, what the gate passes, how the age notice behaves. Name the page and the behaviour in the message, a cookie that surprises you or a notice that returns too soon, and the answer addresses that exact spot. Both entries live in your own browser: the gate cookie for up to 24 hours, and the age-notice acceptance, which hides the notice for 30 days and stays in local storage until the browser’s data for this site is cleared. The site builds no audience lists. Delivering a page leaves the standard server-side request records every web server keeps to answer the request; the publisher uses them to run the site. How the partner route works sits in the terms of use, the publisher’s role sits on about the casino offer service, and the enquiry routes sit on the contact page.