Lucky Block Privacy Policy

Last updated: March 28, 2026 · Effective immediately upon publication

1. Data Collection Scope

This is a static review website. No user registration required. No form-submitted personal data collected (exception: direct email correspondence via [email protected]). Analytics implementation: privacy-respecting, cookie-minimal. Personally identifiable information (PII) storage on our infrastructure: none. Server logs: standard HTTP access logs retained for 30 days, then purged automatically.

2. Cookie Policy

Cookie categories deployed: (a) essential — site functionality, session management; (b) analytics — aggregated traffic measurement, no PII correlation. Advertising/tracking cookies: none. Third-party cookie injection: none authorized. Browser-level cookie management does not restrict content access.

3. Affiliate Link Data Flow

On March 28, 2026, all affiliate links on this site route through /go/offer to the Lucky Block casino platform. Upon redirect, the destination site may deploy its own cookies for referral tracking. This processing is governed by Lucky Block's privacy policy — not ours. We do not receive, store, or process any data from user activity on the casino platform. Users are advised to review the casino's privacy terms prior to account creation.

4. Third-Party Services

External service dependency: Google Fonts (typography rendering via CDN requests to fonts.googleapis.com and fonts.gstatic.com). No advertising networks. No social media tracking pixels. No CRM integration. No marketing automation.

5. GDPR Rights (EU/EEA Residents)

Under Regulation (EU) 2016/679: right to access, rectification, erasure, and data portability applies. Practical scope: this site holds no personal data unless you have initiated direct email correspondence. Data subject requests: [email protected]. Statutory response deadline: 30 calendar days per Article 12(3).

6. Policy Updates

This privacy policy was last reviewed and updated on March 28, 2026. Material changes will be published on this page with an updated effective date. No prior notification mechanism exists — users are advised to check this page periodically. Historical versions are not archived publicly.