Shared definitions
Collected, stored and shared carry one meaning across this policy and the terms page, so nothing shifts when you move between documents on the same account.
LEGAL REFERENCE
Privacy Policy and the Data Behind Your Account
Our privacy policy sets out in plain English what we collect when you open an account with paid bet, and how that data moves afterwards. It covers sign-up...
Account data mapFunding referencesRetention windowsCorrection requests
What This Privacy Policy Covers
This policy applies to every part of the paid bet service you reach from Pakistan, on desktop or on your phone. It explains which categories of data we gather, why we need them, who processes them for us and the choices you can make afterwards. Where local law permits different treatment, or a supported region sets its own rules on record keeping,
we follow those rules and tell you what changes. The chips below list the rails whose transaction references may appear in your history, because each one carries its own confirmation format. Nothing here alters your account terms, and a correction request is verified before anything is removed. Your rights travel with the account wherever you sign in from.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
DATA REQUESTS
Ask Us About Your Records Directly
Privacy questions do not sit behind general chat. Write to our data desk from the email registered on your account and we reply within one working day, usually sooner during Pakistan business hours. If your request concerns a funding record, quote the transaction reference so we can trace it without asking twice.
Team online
Email our data desk
Send your request from the address tied to your account so we match it to your profile. Name the clause you mean and we answer it in full.
Chat from your account
Open chat once you are signed in and ask for a record correction. We confirm two factors before changing anything, and most fixes land the same day.
Written closure request
If you want the account closed and your records cleared, send a written request. We confirm what we remove and which funding references we keep in supported regions.
POLICY AUTHORS
Who Writes and Checks This Policy
This policy is drafted by the same team that builds accounts and funding flows, so the wording matches what the platform does with your data. A second pair of eyes checks each...
Drafted by our own team
Every clause is written by the people who maintain accounts and funding flows at paid bet, so the wording reflects how the service actually runs.
Checked against our map
Before a change goes live, a second team compares it with our internal processing map. Where wording and technical flow disagree, the text is corrected first.
Plain wording throughout
We skip dense legal phrasing when a short sentence does the same job. Each paragraph states what we collect, why it is needed and how long it stays.
Earlier versions on request
Ask the data desk for the copy that applied to your account six months ago and we send the dated version, with a line explaining what changed.
Support hours for Pakistan
Our policy desk answers from nine in the morning until eleven at night, Pakistan time, every day. Anything sent later is picked up next morning.
No unnamed processors
Any processor that touches your data is listed on request, and we never pass details to advertisers. Funding references stay inside the systems that need them.
CONSISTENT WORDING
Matching This Page to Our Other Policies
The same definitions run through this privacy policy and the terms page, so a word like collected or shared means one thing across the site. Where a sibling policy covers a narrower...
Aligned change dates
Each page carries its own date, and we update both together when one clause changes, so you never read a rule that no longer matches your account.
One contact route
The data desk handles questions for every policy page, so you write once and we trace the right clause instead of sending you between inboxes.
Same retention windows
Retention matches across our pages: account records follow one window, funding references another, and marketing preferences sit in a third until you change them.
Consistent funding wording
References from JazzCash, Easypaisa, SadaPay and Raast are described the same way here as in our account terms, so one phrase is enough when you contact support.
Matching correction steps
Verification, correction and written confirmation appear in the same order on every page that touches your records, so the process feels familiar.
Equal language options
Where we publish a clause in more than one language, the English text on this page governs, and the wording stays neutral across supported regions.
PAGE LAYOUT
What You See on This Policy Page
We keep the layout simple: a short summary near the heading, then numbered clauses you can scan on a phone. Each clause carries the date it last changed...
Summary band up front
The first block on this page states, in a few...
Numbered clauses
Every clause has a number you can quote when you...
Change dates beside clauses
Each clause shows the day it last changed, so you...
Side jump links
On desktop the contents sit to one side, so you...
Chip row for local rails
A chip row names the Pakistani rails your records can...
Single-page print view
If you prefer paper, the whole policy prints on one...
Questions We Get About Your Records
We record your name, contact details, device and connection data, plus the references attached to your first funding. Anything else is added only when you use a feature that needs it.
Transaction histories stay for the period our account terms and supported regions require, while marketing preferences are removed straight away. We confirm the exact window when you send a closure request.
Only processors that keep the service running, such as funding partners and fraud checks, and only the fields they need. We do not sell your data and no advertiser reaches your account records.
Yes. Write from your registered email and we prepare a readable export covering your profile, activity and funding references, then hand it over once we confirm it is really you asking.
Write to the data desk with the clause number and the detail you believe is incorrect. We check the source system, fix what needs changing and confirm the new entry in writing.
The same rules cover browser, mobile web and any app we publish, though a device may send slightly different technical fields. We flag which fields are device-specific whenever this page is updated.