Privacy

Privacy policy

KeenCasinos.com is an editorial affiliate website. We do not run casinos, open player accounts, or process deposits. This policy explains what our website can learn about visitors (mostly technical data), what we use it for, and the choices you have. Cookie-by-cookie detail lives in our cookie notice.

No mandatory login
Mostly technical data
Requests welcomed

Last updated August 12, 2026

Scope: what we can and cannot see

This avoids the most common misunderstanding: an affiliate site is not the operator holding your wallet history.

Data we can access

KeenCasinos.com

Pages you open, approximate region (from IP routing), device/browser basics, and whether a partner link was clicked.

Data we cannot access

Your casino balance, wagers, KYC documents, payment details used at an operator, or any information stored in your casino account.

Where casino data lives

Operators

If you opened an account on a casino, that operator controls your player profile and compliance records.

Your next step

For casino-account requests (statements, closures, KYC), contact the operator directly — we cannot change their systems.

What we collect (and examples)

We minimise personal data. Most entries below are technical and short-lived.

Category	Examples	Why it exists
Request log data	IP address (often truncated), timestamp, URL, status code, referrer, user-agent	Deliver pages, troubleshoot errors, block abusive traffic
Cookie and local storage	Language/region choice, dismissed banners, UI preferences	Remember settings so pages behave consistently
Analytics events (aggregated)	Page views, scroll depth, device type, broad geography	Understand which hubs work and which layouts break
Affiliate click parameters	Short tags on outbound links (campaign / article identifiers)	Attribute traffic so we can fund editorial work
Messages you send us	Email address, message content, attachments you choose to include	Respond to questions, corrections, privacy requests

How long we keep it

Retention depends on purpose. We aim for the shortest window that still keeps the site stable and secure.

Data type	Typical retention	Notes
Security / request logs	Days to a few weeks	Rotated and pruned; extended only for incident investigation
Analytics (aggregated)	Months	Stored in aggregated form where possible; not used to build named profiles
Outbound click tags	Months	Used for reporting and finance reconciliation; not a record of what you do on the casino site
Email threads	Until resolved + limited period	Kept to answer follow-ups and keep an audit of decisions; deleted/archived afterwards
Consent choices (where used)	Until you change them	You can revisit cookie settings and your browser controls anytime

How we protect data

No system is perfect, but we use practical controls that reduce everyday risk.

HTTPS encryption

Always on

Traffic is encrypted between your browser and our infrastructure so third parties cannot trivially read page requests in transit.

Tip: Check the padlock in your address bar before submitting a form.

Access control

Restricted

Production tools are limited to staff who need them for publishing, maintenance, or security.

Note: Administrative actions are logged to support audits and incident response.

Least data by design

Policy

We avoid collecting sensitive categories and do not ask visitors for casino-account credentials.

Reminder: If you include sensitive details in a message, it becomes part of that correspondence thread.

Why we process data (legal bases)

Where GDPR/UK GDPR concepts apply, these are the usual legal bases we rely on.

Run and secure the website

Legitimate interests

Prevent abuse, monitor performance, detect outages, and keep pages loading reliably for everyone.

Improve content and UX

Legitimate interests

Use aggregated metrics to see which hubs help readers and where navigation causes confusion.

Respond to you

At your request

Handle messages, corrections, partnership enquiries, and privacy requests you submit.

Measure referrals

Legitimate interests

Attribute outbound clicks so affiliate revenue can fund independent publishing.

What we never do

Clear boundaries that guide our publishing and vendor choices.

We do not ask for or store casino passwords or payment card numbers for operator accounts.

We do not sell identifiable visitor data to casinos or marketing list brokers.

We do not build “shadow profiles” that follow you across unrelated websites for resale.

We do not claim to be a regulator or law-enforcement body — we only publish editorial information.

We do not knowingly publish content targeting minors. This site is for adults only (18+).

How to make a privacy request

If your local law provides a right (access, deletion, correction, objection), this is the fastest way to reach the right team.

Go to our About page and use the contact method listed there.
Tell us what you want (access, deletion, correction, objection) and which country/region you are in.
Send the request from the same email address you used to contact us previously, if applicable.
Do not send sensitive documents unless we ask — we may only need minimal verification.
We reply within the timeframe required by applicable law and explain what we can (and cannot) do.

If your request is about a casino account you opened elsewhere, contact the operator. We cannot access or delete operator-held player data.

Privacy questions we hear often

Do I need an account to read KeenCasinos.com?

No. Our content is public. We only store personal data if you message us or if your browser stores optional preferences (cookies/local storage).

Do you see my wagers, deposits, or verification documents?

No. That data is held by the casino operator you signed up with. We are not part of their player wallet or KYC process.

Is the cookie notice the same thing as this policy?

No. The cookie notice focuses on browser storage. This policy covers server logs, messages you send, retention, and privacy requests.

Do you transfer data internationally?

Our hosting and security vendors may process technical data in different countries. Where GDPR-style rules apply, we use contractual safeguards and data minimisation to reduce risk.

Can I opt out of analytics?

Use the cookie settings (see the cookie notice) and your browser privacy controls. Some basic logs are still required for security and to serve pages.