Terms of Service
The terms explain how your account works, what we expect from you and when we can close a profile. This page covers the data side of that same relationship.
LEGAL REFERENCE
How indian bet Looks After Your Data
This page explains what indian bet collects when you open an account, and how we look after it. You can see which details we ask for, why we...
What we collectWhy we askHow long we keep itHow to make a request
The Rules We Apply To Your Data
Where local law permits, indian bet acts as the controller of the personal data you hand to us when you register, verify a payment or use the lobby. Pakistani account holders are served under the rules that apply in supported regions, and where a rule in your province differs, the stricter of the two is the one we follow. We collect only
what an account needs: your name, contact number, date of birth, device identifiers and the transaction records created by JazzCash, Easypaisa, SadaPay, NayaPay and Raast transfers. We keep records for as long as a regulator or a payment partner requires, then delete or anonymise them. You can ask to see, correct or erase what we hold, and we answer those requests in
writing. This policy governs the indian bet website and any app build we release for Pakistan, and it is read together with the terms that sit on the same footer.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
HOW WE DRAFT
Why You Can Rely On These Words
A policy is only worth reading if somebody stands behind it. We write this page ourselves, keep it short enough to finish in one sitting and revise it...
Written in-house
Our own team drafts and maintains this page rather than an outside agency. It means the person who answers your...
Checked against Pakistani practice
Before any change goes live we compare it with the payment rules JazzCash, Easypaisa, SadaPay, NayaPay and Raast partners expect...
Dated on every edit
The date stamp above the first paragraph shows when this page last changed. We add a short line to the...
Plain wording, no fine print
We keep clauses short and avoid legal padding. Where a term has to be precise, we explain what it means...
Staff access is limited
Only the colleagues who handle accounts, fraud checks and payments can open your records, and every lookup is logged. We...
You can see your own copy
Ask once and we will send a plain summary of the data tied to your account, including the timestamps on...
SIDE BY SIDE
How This Page Fits With Our Others
This policy does not stand alone. It shares language, dates and definitions with the other notices on our footer, so you never have to reconcile two versions of the same promise. Where...
Cookie Notice
The cookie notice lists every small file we set in your browser and what each one does, from holding your sign-in to remembering the language you picked. It sits beside this page on purpose.
Verification Policy
Verification sets out which documents we ask to see and why. The records produced during that step, and how long they stay on file, are described on this page. Both pages are updated together.
Account Security
Security covers passwords, device checks and what to do if you think someone else has your login. What we learn during a check is handled under the rules written here.
Complaints Route
If a request is not settled the way you expected, the complaints route shows the next step and the timeline we work to. The same desk answers both threads.
Promotional Terms
Promotion clauses spell out what happens to an entry when an account closes. Any personal data linked to those entries is removed on the schedule set out here, so the two pages never pull in opposite directions.
Contact and Notices
Contact and notices carries our postal address, email and the hours the team replies. Use it for anything connected to this page and we will route the request to the right colleague.
Layout Choices That Keep This Policy Readable
Long clauses get skipped, so we designed this page to be finished rather than abandoned. Headings tell you what is coming, tables carry the numbers and...
Summary strip up front
Five short chips sit right under the headline and name the ground this page covers: what we collect, why we ask, how long it stays and how to request a change.
Side menu that follows you
On desktop the section list stays pinned while you read, so you can jump to the clause on retention or staff access without hunting through the whole page.
Date stamps on every clause
Each block carries the date it was last touched. Compare that stamp with the change log and you can see what moved between one visit and the next.
Retention in one table
A single table shows how long each record type stays with us, from profile details through to transfer rows, and what happens once that window closes. It is the simplest block on the page to read.
Straight answers at the end
Seven short entries near the bottom cover the points people ask about most, written as direct answers instead of clauses that need a second pass to understand. Start there if you are in a hurry.
Built for small screens
The layout reflows for phones and tablets, keeps text selectable for screen readers and swaps cleanly between English and Urdu labels without losing your place on the page.
Questions We Get About Your Data
We ask for your name, contact number, date of birth and the payment handle you use. Once you start playing, we also record device details, session timestamps and the transactions that pass through JazzCash, Easypaisa, SadaPay or Raast.
Only where it is needed to keep the account running. Payment partners see the transfer reference, and a regulator may ask for a record where local law permits. We never sell your details to advertisers or data brokers.
Profile data stays while your account is open and for the period our payment partners and local rules require afterwards. Transaction rows are held longest because they back up audits. After that we delete or anonymise them.
Yes. Send the request from your registered email and we will confirm what can be removed. Records tied to a completed transfer may have to stay for a set period, and we will tell you which ones.
Sessions run over encrypted connections, and we ask for a fresh sign-in when we spot a new device. You can add a PIN to the app build and sign out of any session from your profile at any time.
We set a small number. They keep you signed in, remember your language choice and show us which pages load slowly. The separate cookie notice lists each one, and your browser settings let you block them.
Use the data desk address in the footer or open live chat between 9am and midnight Pakistan time. Give us your account number, say what you need and we will reply in writing within two working days.