Privacy and cookies

Publisher and privacy contact

Loonie Lights publishes this casino offer catalogue, and this page describes what the site itself does with a visit. The answer is short: a first-party partner cookie, an age-notice entry in the browser, 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.

The age notice in your browser

The first visit opens the age notice, and accepting it, with the “I am 19 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. A fresh acceptance on the next visit starts the 30-day period again, and the notice itself carries the player-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.

The partner transition cookie

The partner cookie belongs to this site’s own domain, a first-party cookie with one job. The site sets it when you open a page and keeps it for 24 hours. It records how the visit arrived: the traffic channel, the source and the referring site. A “Claim bonus” button reads the cookie and passes those values to the casino’s offer page. It holds no name, no account and no play detail; those stay with the casino. Clearing the browser’s cookies removes it. With first-party cookies blocked, the pages stay readable and offer buttons return to the site home page. 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. How the partner route works sits in the terms of use.

Analytics and actual storage settings

The site measures its own traffic with first-party analytics served from this domain. It counts page views and clicks on offer buttons, with the page, the section and the button label, so the publisher sees which offers readers open. No third-party analytics platform, advertising network or social pixel follows the visit. The partner cookie and the age-notice acceptance live in the browser and are removable there. The pages load their own styles, scripts, images and fonts from the site’s own domain, and a visit opens connections to this domain and, after a partner click, to the casino’s domain. Browser settings control the rest: block first-party cookies and the partner route keeps no attribution, clear local storage and the age notice returns on the next visit.

Data enquiries and what the site keeps

Privacy questions reach the publisher at [email protected]: what a page stores, what the partner cookie 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, and the site keeps no visitor profiles and 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. The enquiry routes sit on the contact page, the publisher’s role sits on about the publisher, and the rules for using these pages sit in the terms of use.