How pubg bet Handles Your Account Data
Every account you open with us starts with a short data notice, not a wall of legal text. We explain what we collect — your registration details, region...
Our Policy Posture on Your Personal Data
This page sets out how pubg bet treats personal data where local law permits and in the supported regions you register from. We collect the minimum needed to verify you, run your account and settle transactions: your name, contact details, date of birth, region, login and device data, plus the payment references returned by JazzCash, Easypaisa, SadaPay, NayaPay or Raast. We keep
those records while the account is active and for the retention window local rules require, then delete or anonymise them. We do not sell your personal data. We share it only with payment and technical partners who process transactions or keep the platform stable, and only as far as each task needs. You can ask what we hold, request a copy, correct
anything wrong, or close the account; verified requests are answered within the timelines that apply in your region.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Who to Contact About Your Data
When something looks wrong on your record, tell us directly and we will trace it. We handle access requests, corrections, account closures and any question about this page, in English or Urdu, through the channels below. Every request gets a reference you can follow up on.
Live chat
Open our help widget on desktop or mobile while you are signed in. Share your account email and the record you want checked, and the agent can pull it up while you wait.
Email requests
Write to our privacy mailbox and we reply to the address registered on your account. Useful for formal access or correction asks where you want a written trail.
Account settings
Once signed in you can update contact details, download a summary of the data we store, and submit a closure request yourself rather than waiting for an agent.
The People Who Keep This Page Current
Our compliance and support leads write this page together, and we revise it whenever a data rule, a payment rail or an internal process changes. Nothing here is copied from a template...
Written in-house
The wording here comes from the team running account operations, not an outside agency. Change a process and the paragraph describing it changes the same week.
Version history kept
We keep earlier drafts on file. If you are comparing today's text with an older copy, support can tell you exactly what was altered and when.
Plain-language edit
Before publishing we read each paragraph back and strip legal padding. If a sentence tells you nothing useful about your own data, it does not stay on the page.
Payment partners briefed
Our JazzCash, Easypaisa, SadaPay, NayaPay and Raast integrations follow the data rules those providers set, and we edit this page whenever their requirements shift.
Security checked
Account access runs over encrypted connections, and staff who can view your record are limited and logged. We check those permissions on a fixed schedule.
Feedback welcomed
If a section reads unclearly, write in and say so. Reader questions shape the next revision, and the answers often end up in the question list below.
How This Page Lines Up With Our Others
This page sits alongside our terms and payment pages, and the three are written to agree. Where they overlap — account data, transaction records, closure requests — the...
The Elements You Will Spot on This Page
Layout matters when you are hunting for a single clause. We built this page with a short summary near the start, a clear list of what we store...