Same retention rules
Every page that mentions how long we keep something points back to the retention table here, so you never have to guess which page applies to your account.
LEGAL REFERENCE
How brav bet Handles Your Account Details
Open your brav bet account and your details stay tied to one profile — name, mobile number, wallet reference and the history of rounds you play. This page...
One profile per numberSupport in English and UrduRecords matched to payoutsChanges you can request
Where This Policy Applies To You
We run brav bet for people in Pakistan and in other supported regions where local law permits online play. Where a local rule differs from this page, the local rule decides what we may hold and for how long. JazzCash, Easypaisa, SadaPay and Raast each settle through their own provider rails, so the receipt data we see depends on the rail you
chose at the cashier. When a lawful request arrives from a Pakistani authority, we hand over the smallest set of records that answers it.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
WHO WRITES THIS
Who Maintains This Policy Text
The wording on this page is written and dated by the team that runs our account systems, not lifted from a template library. It is checked whenever we add a payment rail...
Revision dates
Every version carries the date it took effect and a short line on what moved, so you can see whether a change touches your wallet records or your play history.
Named owner
One colleague signs off each update and stays accountable for it. If you ask who set a specific retention rule, we can point to that person and the date.
Plain en-PK wording
We write in the English our Pakistani readers use instead of heavy legal phrasing. The strict sentences stay for the parts that genuinely bind your account, such as payout matching and fraud checks.
Rail accuracy
Before publishing, we walk through every rail we support to confirm which reference fields reach us and which never do. Guessing there would mislead you about what we actually hold.
No profile sales
We do not sell your profile, wallet handle or play history to advertisers or data brokers. When a studio receives lobby signals, they arrive without the details that identify you.
Retention clock
We keep records only as long as a payout, a tax rule or a fraud check needs them, and we name which clock applies to each record type instead of holding everything.
POLICY CONSISTENCY
How Our Policy Pages Line Up
We publish this policy beside our terms, our cookie page and our complaints route. Read together they describe one account: the terms set what you may do in the lobby, the cookie...
One account definition
We use the words your account the same way everywhere: the brav bet profile tied to your mobile number, wallet handle and login, never a shared session.
Consistent rail naming
JazzCash, Easypaisa, SadaPay and Raast appear under one set of names across the site, so a receipt reference you see at the cashier matches our own wording exactly.
Shared support route
Each policy page ends at the same help route. Whichever page raised your question, you land in one place and a colleague picks up the thread with the history attached.
Shared revision schedule
When one policy page changes, we check its siblings the same week and refresh any cross-reference that has gone stale, which keeps the wording aligned instead of drifting page by page.
Cookie boundary
Storage files, session tokens and analytics belong to the cookie page. Anything that identifies you as a person belongs here, so each page answers its own question cleanly.
Complaints route
If you disagree with a decision we made about your data, the complaints page carries the escalation steps and the timescale, and this text stays the background to that process.
What Stands Out On This Page
Scroll this page and you will notice the shape we use for every rule: a short summary line first, the fuller sentence underneath, then a chip...
Summary first
Each clause opens with the one-line version you can read on a phone in the lobby, then the fuller sentence for anyone who wants the detail behind the rule.
Chip row
Small tags sit above each block showing which part of your account is affected, from your registered mobile number to the wallet handle your receipt carries.
Jurisdiction flags
Rules that change outside Pakistan are marked inside the text rather than listed separately, so you always know when a clause applies to you and when it does not.
Dated footer
A revision line closes the page with the date the wording last moved, and the archive link keeps the earlier version reachable for anyone comparing two readings.
Language choice
Sentences use the English our Pakistani readers work in, with Urdu terms left in place where a payment rail or a document name has no natural translation on this side.
Nothing hidden
Nothing important sits inside a collapsed panel or an image. Everything a reader needs to understand their own account appears as selectable text on the page itself.
Questions We Get About Your Data
Your name, mobile number, the wallet handle you fund with, and a log of the rounds you play. We also keep a device marker so a login from a new handset can be checked.
Usually not. These rails send a masked reference and a transaction identifier rather than the full number, and we keep the identifier because a payout or a disputed receipt must be matched against something.
Yes. Send the request from your registered mobile number or email and we compile the profile, wallet references and play log into a readable file within our published turnaround.
No. We do not trade profiles, wallet handles or play histories with advertisers or data brokers. Studios that supply lobby content receive gameplay signals carrying no name, number or payment reference.
We hold payout, tax and fraud records for the period each rule requires, then delete the rest. Support threads clear earlier, and you can ask which clock applies to a named record.
A small group on our account and payments teams, working on a need-to-know basis, plus the automated checks that flag unusual activity. Every lookup is logged, so internal access stays traceable afterwards.
Where local law does not permit play, we block the account until the position is settled. Your stored records stay intact, support keeps answering, and you can ask us to correct anything that looks wrong.