Account Terms
Our account page covers what you agree to when you register, and it points back to this page for anything about personal data instead of repeating it.
Before you open an account or fund it the first time, you deserve to know what we record and why. This page sets out the data oro casino...
Where local law permits, we run this page as the single place you check for how oro casino treats personal data. We act as the controller of what you submit at registration, and we process it for the purposes described here rather than for anything hidden. Supported regions may carry extra requirements, so if a local rule gives you stronger rights than
this page, that local rule wins. We keep our wording plain because you should not need a lawyer to follow it. Retention periods follow the type of record: payment references tied to JazzCash, Easypaisa, SadaPay and Raast are held only as long as settlement and accounting duties require. If you disagree with any part of this posture, you can close your account
and ask us to delete what we are not obliged to keep.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
We write this page in-house, from the systems we run day to day, and we date every revision so you can see what moved. Each paragraph is checked against the flows that...
Our own legal and operations staff draft this text rather than an outside agency, so the wording lines up with the account flows you actually meet here.
Every revision shows the day it took effect and we flag what moved, so you can compare the older wording with the current text yourself.
Before anything goes live, each claim about data handling is traced through our registration, payment and support tools to confirm the description still holds true.
We skip legal padding and write in everyday Pakistani English, because a policy you cannot follow protects nobody, and least of all you.
Where a rule inside a supported region gives you stronger rights than this summary, that local rule takes priority over anything written here.
You can challenge any paragraph and we will explain the thinking behind it, or amend the wording when it no longer matches how we work.
Our policy set is one document split across pages, so terms should not shift depending on where you land. What you read on the account, payment and cookie pages says the same...
Our account page covers what you agree to when you register, and it points back to this page for anything about personal data instead of repeating it.
The payment page explains how JazzCash, Easypaisa, SadaPay and Raast references sit with us, using the same retention wording you read here.
Our cookie page lists the storage we set for sign-in and preferences, and the categories match the switches shown inside your account settings.
Sportsbook and table pages describe activity records only, and any data handling they mention points back to the sections set out on this page.
Promotion conditions live on their own page and never widen how we use your data; permissions always come back to what this page allows.
Help articles explain how to raise a request and how long a reply takes, without duplicating the legal wording that belongs here.
Our contact page routes complaints, data questions and account closures to the right team, using the same categories you have just read.
Everything here is laid out so you can reach one answer fast. Categories of data sit under clear headings, each with the reason we hold it...
Headings group what we hold: account details, device and sign-in logs, table and market activity, chat transcripts, and the payment confirmations your wallet sends us.
Beside every category we state the reason it exists, from keeping a session secure to settling a JazzCash or Easypaisa transfer and meeting accounting duties.
Each block shows how long a record stays and what triggers deletion, so you are never left guessing how long a sign-in log or transcript remains.
One area lists the switches you own, covering cookie categories, marketing messages, and the request types you can raise from within your account.
Terms such as controller, processor and personal data are defined the first time they appear, so the rest of the text reads without a glossary.
Links from each heading open live chat or email, so a question about one section reaches the right team without hunting for a contact form.