Independent comparisons — bonuses, operators, reviews · about us · play safe

Data & visitors

Privacy notice

SlotsRoll.com publishes casino comparisons — we do not host wallets, open player profiles, or move deposits. This notice covers the technical and contact data our site may process, the reasons we keep it, and how you can ask questions. Browser cookie detail sits in the separate cookies & device storage page.

Last updated September 5, 2026

Three facts before the detail

Skim these first — they clear the biggest mix-ups with casino operators.

No player account here

Reading SlotsRoll.com does not create a gambling login. Wallets, KYC packs, and payouts live only on operator sites you choose.

Mostly machine signals

We lean on request logs, optional preference keys, and aggregated traffic stats — not dossiers built from your casino play.

You can write to us

Access, correction, deletion, or objection requests go through the contact path on our About page when local law applies.

Hard nos for this publisher

Non-negotiables that shape vendors, copy, and how we handle inbound mail.

No collecting casino passwords or payment-card numbers meant for operator accounts.

No selling named visitor lists to casinos or marketing brokers.

No “shadow profiles” stitched across unrelated sites for resale.

No posing as a regulator or law-enforcement desk — editorial publishing only.

No content aimed at minors; this site is 18+ (or higher where local law requires).

Visitor signals we may hold

Light footprint by design — each row is a type of data, not a surveillance product.

Hit logs

Technical

Often-truncated IP, time stamp, URL, status code, referrer, and user-agent — used to serve pages, debug faults, and blunt abuse.

Lifespan: Rotated on a short cycle unless an incident needs a longer look.

Preference keys

Browser

Locale/region choice, closed banners, and small UI prefs so return visits feel consistent.

Reset: Clear site data anytime; see the cookies page for controls.

Usage totals

Aggregated

Page views, rough device class, scroll depth, broad geography — to learn which hubs help and which layouts fail.

Shape: Built as totals where tools allow, not named browsing histories.

Outbound credit tags

Attribution

Short campaign or article IDs on review links so referral income can fund the desk.

Limit: They do not record what you do after you leave our hostname.

Messages you send

Voluntary

Email address, body text, and files you attach when you contact editorial or privacy inboxes.

Care: Kept to answer you and keep a short audit trail, then archived or deleted.

Publisher desk vs casino vault

Two systems. Mixing them up is the most common privacy question we get.

What each side can access

SlotsRoll.com window

Pages you open here, coarse region from routing, device basics, and whether a partner link was clicked.

Blind spots for us

Casino balance, wagers, KYC uploads, payment instruments used at an operator, or anything inside a player account.

Where to send account requests

Operator holds the file

If you registered at a casino, that brand owns the player profile and compliance records.

What to do

Ask them for statements, closures, or KYC changes — we cannot edit their databases.

Retention clock

Keep only as long as the job needs — then prune.

Signal type Usual window Extra note
Security / hit logs Days → a few weeks Extended only while investigating an incident
Usage totals Months Aggregated where possible; not turned into named profiles
Outbound credit tags Months Finance and reporting — not a play log on the casino site
Email threads Until closed + short buffer Then deleted or archived
Consent / preference choices Until you change them Browser controls and cookie settings still apply

Processing grounds (where GDPR-style rules apply)

Plain labels for why a signal exists — not legal advice for your situation.

Keep the site up and safe

Legitimate interests

Abuse prevention, uptime checks, outage detection, and reliable page delivery.

Steer the product

Legitimate interests

Aggregated metrics show which hubs help and where navigation confuses people.

Answer your mail

At your request

Corrections, partnership notes, and privacy requests you choose to send.

Credit referral clicks

Legitimate interests

Attribute outbound visits so affiliate income can fund independent publishing.

Request path if you want action

Access, erasure, correction, or objection — follow this sequence when local law gives you those rights.

  1. 1

    Open the About contact block

    Use the method listed on our <a href="https://www.slotsroll.com/ie/our-team">About</a> page — that inbox reaches the right desk.

  2. 2

    Name the ask and your region

    Say whether you want access, deletion, correction, or objection, and which country you are writing from.

  3. 3

    Use a recognisable address

    Send from the same email you used with us before when that applies — it speeds light verification.

  4. 4

    Skip heavy documents unless asked

    We rarely need ID packs for a simple site request; we will say if more proof is required.

  5. 5

    Wait for a timed reply

    We answer inside the window set by applicable law and spell out what we can (and cannot) change.

Casino-account files sit with the operator. We cannot open, edit, or wipe those records.

Everyday shields on our side

No stack is flawless — these habits cut routine risk.

  1. HTTPS wraps traffic between your browser and our infrastructure so requests are harder to skim in transit.
  2. Production tools stay limited to people who publish, maintain, or secure the site.
  3. Admin actions are logged so audits and incident reviews have a trail.
  4. We avoid sensitive categories by default and never ask for casino-account passwords.
  5. Anything sensitive you paste into a message becomes part of that thread — keep mail lean when you can.

Straight answers

Do I need a SlotsRoll.com login to read reviews?

No. Pages are public. Personal data shows up mainly if you email us or if the browser keeps optional preference keys.

Can you see my deposits, bets, or KYC scans?

No. Those stay with the operator you joined. We are outside their wallet and verification flow.

Is this the same as the cookies page?

No. Cookies & device storage covers browser files. This notice covers server logs, messages, retention, grounds, and requests.

Does any technical data leave my country?

Hosting and security vendors may process logs in more than one region. Where GDPR-style rules apply, we use contracts and data minimisation to reduce risk.

How do I dial down usage totals?

Use browser privacy controls and the options described on the cookies page. Basic security hit logs still exist so we can serve and protect the site.