How bets app Handles Your Data
One plain-English policy covers what we collect when you open an account, how long we hold it, and which partners ever see it. Everything below applies to your...
What We Collect And Why
Where local law permits, we collect only what we need: your name, date of birth, contact details, device and login data, and the transaction records tied to your account. We use those records to verify you, meet our record-keeping duties, prevent fraud and settle disputes. We store account data on secured servers, limit internal access to staff who need it, and keep
records for as long as the rules in your region require. Because access to online wagering differs across Pakistan and beyond, some features, payment rails and lobby areas are only shown in supported regions. Where a feature is not permitted locally, we switch it off for your account rather than asking you to work around it. Questions about scope, retention or a
specific clause can go to our team.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Who Maintains This Policy Page
This page is maintained by the same team that runs account operations for bets app, not by an outside agency. Every clause is checked against how our systems...
Internal Ownership
Policy wording is owned by our own operations and compliance staff, the same people who handle account checks, transaction records...
Plain Wording Rule
We avoid legal padding that hides meaning. If a clause cannot be understood by an ordinary account holder on a...
Change Log
Each update to this policy carries a short change line so you can see exactly which clause moved and why...
No Data Selling
We do not trade your records to outside advertisers. Sharing is limited to the payment and verification partners needed to...
Regional Awareness
Our team tracks how data rules differ between Pakistani provinces and other supported regions, so access wording stays accurate for...
Contactable Authors
Every policy question reaches a named internal desk rather than an anonymous form. You get a reference number and a...
How This Policy Lines Up Elsewhere
Our policy family shares one structure, so moving between pages should not feel like reading a different company. The privacy page you are on, our terms page and...
| Shared Definitions | Terms such as account, transaction record and personal data carry one meaning across every policy page, so you are not re-learning vocabulary as you move between documents on this site. |
|---|---|
| Same Numbering | Clause numbers match on the terms page and this policy, which makes it easy to quote a section when you write to our support desk about a specific rule. |
| Payment Page Alignment | Anything the payment pages say about storing transaction references is consistent with the retention wording here, so the same record is described in the same way on both pages. |
| One Update Cycle | We revise the whole policy family together. A change to how we hold records shows up on this page and the related pages in the same release, never half-published. |
| Consistent Tone | Plain sentences, short paragraphs and no hidden cross-references. If a page in the family needs a caveat, we write the caveat out rather than pointing you to another document. |
| Matching Contact Paths | The support routes listed on our other pages are the same routes for privacy questions, so you never have to hunt for a separate mailbox to raise a data concern. |
| Region Switch Clarity | Where access rules differ between supported regions, every page in the family hides the same features, so the account view you see stays consistent wherever you sign in. |
What You See On This Page
We designed this page to be scannable on a phone, where you will most likely open it. Section headers tell you what each block covers, chips name the...