Privacy Policy and data handling

Last updated: 9 November 2026.

This page explains what happens to data when you open liralucky.com. The short version: this is a two-page reading site with no accounts and no forms, so there is very little to explain. The long version is below, section by section, because "we respect your privacy" tells you nothing useful.

1. Who runs this site

liralucky.com is an independent guide to the Liraluck brand for players in Canada. It is not the casino, it is not owned by the casino, and it cannot open, close, fund or verify an account for you. Write to hello@liralucky.com for anything on this page.

2. What this site does not collect

There is no registration, no login, no contact form, no newsletter, no comment section and no upload field anywhere on these pages. Nothing asks for your name, email, address, date of birth, document scans or payment details, so none of that reaches us.

There is also no analytics on this site. No Google Analytics, no Tag Manager, no advertising pixel, no heatmap or session-recording tool. You can confirm it yourself: view the page source and count the scripts. There are two, and both are listed in section 6.

3. Server access logs

The web server records a line for each request, the way web servers have since the 1990s: IP address, timestamp, the path requested, the HTTP status, the referring URL if the browser sent one, and the user-agent string. These logs exist for diagnostics and abuse handling. They are not joined to any profile, not used for advertising and not sold.

4. Cookies and browser storage

This site sets no cookies of its own. It writes nothing to localStorage or sessionStorage. That is why you see no cookie banner here: there is no consent to collect, because there is no tracker to consent to.

Cloudflare, described next, may set its own operational cookies such as __cf_bm or cf_clearance. Those are bot-management and challenge cookies, not analytics, and they are governed by Cloudflare's own policy rather than ours.

5. Cloudflare in front of the site

All traffic to liralucky.com passes through Cloudflare, which terminates TLS, caches static files and filters automated traffic. In doing so Cloudflare processes your IP address and request metadata as our service provider. It is also why a small share of visitors occasionally sees a verification interstitial before the page loads.

6. Outbound clicks to the operator

Buttons that lead to Liraluck are affiliate links. They do not point straight at the advertiser. Your browser posts to /go/ on this domain, and that endpoint answers with a redirect to the brand's tracking link. Attached to that redirect are four labels: this domain, the page you were on, the block the button sat in, and the button's position in that block.

Those labels describe the page, not the person. They carry no identifier for you, and they exist so the operator can tell which page sent a visitor and so we can see which sections are worth rewriting. After the redirect you are on the operator's infrastructure, under the operator's privacy policy, and what happens there is outside our reach.

7. Who else receives data

Three parties, in this order: the hosting provider that runs the server and stores the logs, Cloudflare as the edge layer, and the affiliate tracking service that receives the click labels in section 6. Nobody else. There is no data broker, no ad network and no list anyone is sold to.

8. Purposes and legal bases

Serving the pages you asked for, keeping the site available, defending it against automated abuse, and attributing outbound clicks. Where the GDPR applies, the basis is legitimate interest under Article 6(1)(f) for logs and security, and the same for click attribution, which is limited to page metadata. There is no profiling and no automated decision-making.

9. How long data is kept

Access logs rotate on the hosting provider's schedule, which is weeks rather than years. Click records live in the affiliate tracking service under its own retention rules. We hold no database of visitors, because we never built one.

10. Your rights in Canada

Under PIPEDA you may ask what personal information we hold about you, ask for a correction, and complain to the Office of the Privacy Commissioner of Canada. If you are in Quebec, Law 25 adds rights of access and portability. In practice the honest answer to an access request here is usually "server log lines containing your IP address, if any are still within the retention window" — and we will say so in writing rather than pretend the file is richer than it is.

11. Your rights elsewhere

Visitors from the European Economic Area and the United Kingdom have the GDPR rights of access, rectification, erasure, restriction, objection and portability, and may complain to their national supervisory authority. California residents have the CCPA and CPRA rights to know, delete, correct and opt out of sale or sharing. We sell and share nothing, so the opt-out is already the default.

12. Children, changes and contact

Gambling content is for adults. This site is not directed at anyone under 18 (19 in British Columbia, Alberta and several other provinces) and we do not knowingly process a minor's data. If this page changes, the date at the top changes with it; material changes will be visible on this page rather than announced by email, since we have no mailing list to announce them to. Questions go to hello@liralucky.com.

Play responsibly. 18+. Help in Canada: ConnexOntario, the Gambling Support Line in your province, or your provincial health service.