LEGAL REFERENCE

Your Data at prime bet, Plainly Put

This page sets out exactly what prime bet records when you open an account from Pakistan, why we hold it, and how wallet references from JazzCash, Easypaisa, SadaPay...

What we recordWhy we hold itYour controlsRevision dates
prime bet Your Data at prime bet, Plainly Put

Where This Privacy Position Applies

Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.

ASK OUR DESK

Reaching the Team About Your Data

Questions about this policy reach our account desk directly, and we answer in English and Urdu. Send your registered email address with...

Live chat Sign in and open a chat from your...
Privacy mailbox Email our data contact with your registered address...
In-app request form On mobile, the help tab links to a...
WHO MAINTAINS THIS

The People Who Maintain This Page

This policy is maintained by the same team that builds the account flow you use, so the wording tracks what the platform genuinely does. Each clause is checked against our engineering records...

Operations check

Our account operations team reads each revision before it publishes and flags any clause that no longer matches how registration, verification or withdrawals actually run across supported regions.

Engineering input

The engineers who build our storage layer confirm what gets captured, how long it sits and what the deletion job removes, so nothing is described here the system does not do.

Local law checks

Before a clause applies to Pakistan, we check it against local rules, including how wallet references from JazzCash, Easypaisa, SadaPay and Raast must be handled in our systems.

Plain-English pass

A final edit strips legal padding so you can follow the page without a dictionary. If a sentence needs a lawyer to decode it, that sentence does not ship.

Revision log

Every update carries a date and a short line on what moved, so you can see whether a change touches your account data, your wallet references or only the wording.

Desk feedback

Tickets you raise about stored details feed into the next revision. When several people ask the same thing, we answer it on this page rather than in private replies.

HOW IT FITS

How This Page Lines Up With Others

This page sits beside our other legal pages and is written to agree with them. Where account rules and this one overlap, the wording stays consistent, so you never get two answers...

01

Account terms

The terms page covers what you may do in the lobby and how an account closes. This policy continues from there and explains what happens to the details left behind.

02

Wallet terms

Wallet terms list the rails we accept and how withdrawals clear. Here we explain which of those records we keep afterwards, where they sit and for how long.

03

Cookie notice

The cookie page lists the small files this site sets. This policy explains what those files report back to us and how you can switch them off in your browser.

04

Verification rules

Verification rules describe the documents you upload. This page states where those files are stored, which teams can open them and when they are removed from our systems.

05

Promo rules

Promo rules say who qualifies for what. Here we explain how we use your activity data to decide eligibility and how long those records stay on file afterwards.

06

Complaints channel

Our complaints route handles disputes about your account. This policy tells you how to ask for the underlying data a dispute is built on, and in what format.

07

Language settings

Language settings decide whether you read the site in Urdu or English. This page states which regional rules apply once you choose a supported region in your profile.

What You Can See and Control

The layout of this page is built for skimming on a phone. Every clause carries a heading that says what it covers, a plain-language summary first...

Summary blocks

Every heading opens with two or three sentences in everyday language, followed by the fuller clause. You get the gist quickly and the long wording only if you want it.

Data control panel

Inside your dashboard, one screen gathers the switches that matter — marketing messages, saved wallet references and session history — each labelled in plain words you can act on.

Revision banner

When anything material changes, a dated banner sits at the head of this page for thirty days, linking straight to the altered clause so you can compare the two yourself.

Storage table

A short table lists each kind of detail we hold, the reason we hold it and how long it stays. References from JazzCash and Easypaisa sit in their own row.

Copy of your file

You can ask for a copy of your account data from the dashboard. It arrives as a readable file rather than raw database fields, and we email you once it is ready.

Support shortcut

A link at the foot of every clause jumps to our desk with that section already filled in, so you never have to explain which part you are asking about.

Points We Get Asked About Data

Your name, contact details, date of birth and the region you register from, plus any verification files you upload. We also log sign-in times and device type.

We store the transaction reference and the last digits of the wallet account, never your PIN. That reference lets our desk trace a wallet movement when you raise a query.

While your account is open, we keep it for as long as you use the platform. After closure we hold a slim record for the period local rules require.

Yes. Raise the request from your dashboard or through the desk. We confirm it came from you, then send the file to your registered contact within a few working days.

Access sits with the teams that run your account: verification, wallets and support. Every lookup is tied to a staff identity, and marketing never sees your live profile.

We date every revision and raise a banner on this page for thirty days. If a change affects how your data is used, we also email you before it takes effect.