How loyal casino handles your account data
When you open an account with us, your details move through a documented flow: what we collect, why we need it, and how long we keep it. This...
Where this policy applies and where it stops
This policy covers the loyal casino account and wallet you hold with us, the pages you browse after signing in, and the chats you start with support. It does not cover third-party sites you reach through a link, or the messaging app you use to confirm a transfer. Access depends on where local law permits, and residents in supported regions follow the
same rules as every other customer there. Where a local requirement differs, that rule shapes how we handle your record. JazzCash, Easypaisa, SadaPay and Raast transactions sit inside this policy because each reference ties back to your account. We keep one text for the whole brand, so nothing changes just because you switch between your phone and a desktop browser.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Who writes and maintains this page
Anyone can say a policy is fair; we would rather show the habits behind ours. The text is written by the team that runs the platform, checked against what support can actually...
Written by the operator
Written by the team that runs loyal casino, not copied from a template. That means the wording matches how we actually store account data day to day.
Plain Pakistani English
Plain Pakistani English throughout, so you are not reading legal phrasing borrowed from another market. Payment names such as JazzCash, Easypaisa and Raast appear exactly as you know them.
Visible change dates
Every edit carries a visible date near the heading, with a short summary of what moved. You are never left guessing whether older wording still applies.
Checked with support
Front-line agents read this page before it goes live, so what it promises matches what chat can actually do for you. Disagreements get fixed in the policy.
Escalation route
A question that chat cannot settle moves to our privacy contact under the same ticket reference. Nothing gets repeated, and you can follow the trail from start to finish.
Readable wording
Headings stay descriptive and key points never hide in dense paragraphs. You can read the whole page in a few minutes on a phone, which matters when checking something quickly.
One set of rules across every page
You will meet our other policy pages as you use the account, and they need to agree with this one. Terms of use, cookies, wallet pages and fair...
| Same rules everywhere | Our privacy wording does not change between the lobby, the sportsbook and the live tables. Wherever you sign in, the same collection and retention rules follow your account. |
|---|---|
| Terms of use | The terms page explains how your account works and how disputes are handled. This page covers what we store, so the two describe your relationship without repeating each other. |
| Cookies and sessions | The cookie notice lists the tags that keep you signed in and remember your language choice. Nothing there overrides what this page says about personal data or retention. |
| Wallet pages | Wallet pages explain what JazzCash, Easypaisa, SadaPay and Raast do on their side. Here we set out which details we keep and how long the reference stays with your account. |
| Fair play rules | The fair play page covers game rules and how we treat unusual patterns. If a check there touches your personal data, the rules on this page still govern the handling. |
| Promotional terms | Promotional pages state what you accept when you opt in, and they never widen how we may use your stored details. Opting in gives us no broader rights than this page allows. |
| Help and contact pages | Contact details on our help pages match the routes listed here. If a channel ever changes, both pages change together, so you are never pointed at a closed route. |
What you will see in this policy
This page is built for scanning rather than endurance. Short summaries open each clause, examples use rails you already have, and region reminders flag when a rule shifts...