What This Privacy Policy Covers
We wrote this policy so you know exactly what happens to the data you hand over when you open an account. It sets out what we collect at...
Where This Policy Applies
royal game keeps one policy for everyone, but the fine print shifts with where you are. From Pakistan, we handle your data under the rules that apply where local law permits, and we hold those standards across supported regions. References from JazzCash, Easypaisa, SadaPay, NayaPay and Raast are stored masked and passed only to the processor that settles the transaction. We keep
account-opening details while your account is open, then delete or anonymise them on a rolling schedule. You can ask what we hold, correct it or have it removed. Where a regulator or a court compels disclosure, we hand over only what the order names. Nothing is sold on, and no third party gets your records for advertising.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
How We Keep This Policy Accurate
Every change here follows one path. The teams that run payments, the lobby and your support tickets each sign off on wording that touches their area. A written change log records what...
Who Signs It Off
Wording is approved by the operations lead, the payments team and a privacy handler before publication, so each clause is checked by someone who runs that area.
Change Log
Each revision carries a date and a short line on what shifted. The update stamp sits near the header, and older versions stay on file for anyone tracing a clause.
Plain English
We avoid legal fog on purpose. Clauses are rewritten until a reader can follow them without a glossary, and legal terms get a plain line beside them.
Data Minimisation
We ask for what the account needs and nothing else. Your email, a payment reference and device basics are enough to run the platform, so we do not chase extra fields.
Access Control
Only staff who need your records for a specific job can open them, and every access is logged. Payment references stay masked in the tools our teams use.
Staying Current
Payment rails change, so our wording changes with them. When a new local rail goes live for Pakistan accounts, this page is refreshed before the option appears on your screen.
The Same Rules On Every Policy Page
Our policy pages should never contradict each other, so they share one writing rhythm. Where this page explains data handling, the neighbouring pages explain the account, the money...
| Terms of Use | Sets out the account rules you accept when you join. The same opening definition of personal data is used on both pages, so your records are described identically. |
|---|---|
| Cookie Notice | Covers the small files that keep you signed in and measure page speed. Its list of purposes matches our lawful-basis table here, with no hidden categories. |
| Payments Policy | Explains how JazzCash, Easypaisa, SadaPay, NayaPay and Raast transfers are handled. Retention windows quoted there are the same ones used in the storage clause you read here. |
| Account Security | Deals with passwords, device checks and session handling. When a security incident touches personal data, the notification duties described there are mirrored in the breach clause here. |
| Fair Use Rules | Covers acceptable behaviour on the platform. Data collection tied to monitoring is described in the same terms on both pages, so the scope never widens alone. |
| Claims and Disputes | Explains how to escalate a dispute. Records shared during that process are governed by the retention periods set out here, and neither page shortens the other's deadlines. |
| Update History | Lists dated revisions for every policy page. If this page changes today, the entry appears alongside the others, so you can compare what moved across the whole set. |
Layout Elements That Carry This Policy
A policy is only useful if you can find the clause you came for. The elements below are the fixed handles on this page — the summary strip...