LEGAL REFERENCE

Your Privacy Policy, Stated Up Front

rollino casino publishes this privacy policy so you can see what happens to your account data before you open a wallet-backed profile. We set out what we collect...

Account data mapRetention windowsLocal payment railsCorrection requests
rollino casino Your Privacy Policy, Stated Up Front

How We Apply This Policy By Region

Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.

PRIVACY DESK HOURS

Reach Our Privacy Desk Directly

Questions about this policy go to a named desk rather than a general queue. Our support team takes data requests from 09:00 to 01:00 Pakistan Standard Time, every day, and hands anything technical to the engineers who maintain the account system. Write in English or Urdu and we reply in the language you used.

Team online

Live Chat Window

Open a chat from your signed-in account and our desk picks it up inside the published window. Keep your account number handy so we pull the right record.

Records Email Desk

Write to the privacy address in your account settings for copy, correction or deletion requests. We acknowledge within one working day and confirm once the change lands.

In-App Data Ticket

Raise a ticket inside the app if you would rather keep one thread. Attach a screenshot when a record looks wrong and we route it onward.

POLICY STEWARDSHIP

Who Maintains And Checks This Policy

We keep one owner for this document and one calendar for its checks. The wording is re-read whenever we add a payment rail or change how account records move between systems, so...

Named Policy Owner

One person signs off every change to this page, so your questions have a clear destination instead of bouncing between teams.

Revision Calendar

We re-read the policy on a set schedule and again whenever a payment rail or account system changes, keeping the published version close to what runs live.

Plain-Word Drafting

Definitions are written in everyday English first, then checked for accuracy, so you can follow the same wording our team relies on.

Data Map Kept Current

We track where account records travel between our systems and the partners we use, and that map is updated before features reach your account.

Access Rules On Record

Staff access follows a named role, and every lookup against your account is logged. You can ask which team opened your file and why.

Published Change Log

Revisions carry a date and a short reason, so you can follow what moved between versions instead of comparing two long documents line by line.

Aligned With Our Sibling Policy Pages

This policy shares its definitions and revision date with our terms and cookie pages, so one idea never carries two meanings depending on where you read it. When...

Same Revision Date
All three pages carry one revision date. If the dates differ, you hold a cached copy and a refresh pulls the current text.
Shared Definitions
Words such as account, record and retention mean the same thing on every page, so you never guess which version a paragraph is using.
One Release Cycle
Shared wording ships together, so a definition cannot quietly change here while the terms page still carries the older phrasing for months.
Cookie Page Linkage
The cookie page covers trackers and storage on your device, while this page covers account records, so the split stays clear.
Terms Page Linkage
Our terms page handles account rules and eligibility, and points back here whenever personal data is the subject, so you land in the right place.
Support Routing
A request sent from any of the three pages reaches the same desk, so you do not repeat your account number to a second team.
Consistent Headings
Sections keep the same titles across all policy pages, so a reader who learns the layout once can move through a sibling page without hunting.
PAGE COMPOSITION

Layout Elements That Shape This Policy Page

Every policy page we publish keeps the same shape, because a reader who knows where things sit finds an answer faster. Kickers mark each block, cards carry a...

Revision Date Block The revision date sits directly under the headline, so you...
Section Kickers Each block opens with a short uppercase tag that names...
One-Idea Cards Cards hold a single point under its own heading, so...
Plain-Word Glossary Terms are explained where they first appear, so you can...
Language Options The page is written in Pakistani English for readers here...
Long-Form Reading Width Body text keeps a comfortable measure on wider screens, so...

Privacy Policy Questions, Answered Plainly

We record your name, date of birth and the payment handle you use, whether that runs through JazzCash, Easypaisa, SadaPay or Raast. Login data helps us flag access from unfamiliar places.

Records stay while your account is open and then for the period local rules require us to keep them. After that we delete or anonymise whatever remains inside our own systems.

Only the fields a transaction needs, such as the amount and the wallet handle, travel to the partner handling that transfer. Your full profile is never handed over for marketing.

Yes. Send the request from your account address and we assemble the file attached to your account, then share it in a readable format once we confirm it is you.

Closing removes your access straight away and starts the retention clock on anything we must keep. The rest leaves our live systems, and you can ask us to confirm in writing.

The revision date under the headline moves and the change log lists what shifted. If a change affects how your records are used, we also flag it inside your account.