LEGAL REFERENCE

How bb44 game Handles Your Account Data

Everything bb44 game does with your account data sits on this page: what we collect when you open an account, why a JazzCash, Easypaisa, SadaPay or Raast transfer...

Data you give usWhy we keep itHow we protect itYour choicesWays to reach us
bb44 game How bb44 game Handles Your Account Data

Our Policy Posture Across Supported Regions

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

REACH THE DESK

Where Data Questions Go at bb44 game

Data questions reach a real desk, not a script. Tell us which part of this page you mean and we will route...

Live chat Open chat inside your account between 09:00 and...
Written request Send your registered email, the section you are...
Account settings Several updates you can make yourself: change contact...
HOW WE OPERATE

Who Writes and Checks This Page

The people who run the platform write this page: compliance staff, payment engineers and the support leads who handle data requests daily. We keep the wording close to what we actually do.

Written in-house

Nobody outside bb44 game drafts these words. Compliance writes the policy, payment engineers check the wallet paragraphs, and support confirms it matches what they say on chat.

Dated changes

Every edit carries a date and a short summary of what moved, published before the change takes effect, so you can set the earlier version beside the current one.

Plain words

We use the same words here that support uses on chat: account, record, reference, request. Where a term needs a legal definition, we define it once and keep using it.

Working contact routes

There is a working address behind every route on this page and a named team that owns it. Ask who holds your request and we will name the team, not a ticket.

Controls described

We describe what we actually run — hashed passwords, two-step logins and restricted staff access to wallet references — rather than vague assurances, and we say where a control has a limit.

Local context

Because we serve Pakistan, the staff who handle JazzCash, Easypaisa, SadaPay and Raast daily read this page, so the wallet behaviour here matches what you see on your phone.

How This Page Fits Our Other Policies

This page sits in a small set of policies meant to be read together, and each one owns a single subject. Record questions stay here rather than hiding...

Terms of useThe terms page covers your agreement with bb44 game: accounts, payments and how disputes are handled. Come here when the question is about records rather than rules.
Cookie pageCookies and the small files your browser stores are listed on their own page. Here we explain why we keep the data those files create and how long records remain.
Wallet pageHow JazzCash, Easypaisa, SadaPay and Raast payments are made sits on the wallet page. This page covers the data trail: what your provider confirms and what we keep.
Security pageLogins, two-step verification and reporting a problem sit on the security page. This page states the data rules behind those controls, including what we log from a new phone.
Shared definitionsEvery policy page defines account, record and request in the same way, so a term means one thing across the site. Spot a mismatch and we will align the wording.
One contact pathData questions always reach the same desk, whichever page you started from, so you never guess which team owns the reply. The desk forwards internally and answers you.
Update rhythmAll policy pages are checked on one schedule, so a change in another area prompts a fresh look here. When wallet requirements shift, both pages move together.
INSIDE THE POLICY

What You See on the Page Itself

The layout is built so you can find one rule in seconds: a fixed menu on the left, short titled blocks, and a summary line above the detail...

Sticky menu A fixed list on the left jumps to collection, sharing...
Summary lines Each block opens with one sentence stating the rule in...
Retention table A simple table shows how long account records, wallet references...
Request tracker When you ask for a copy, a correction or a...
Version banner A slim banner carries the date of the last change...
Local wallet names Wallets are named the way you name them — JazzCash...

Questions We Get About Your Data

The details you type in — name, date of birth, contact email and phone — plus the wallet reference for your first transfer. We also record device type and sign-in times.

We keep the reference attached to each transfer so a payment can be matched to your account. We do not keep your wallet PIN or the one-time approval code.

Yes. Ask through the support desk and we close the account, then delete or anonymise what we are not required to keep, such as settlement records.

References and settlement records stay for the period our payment partners require, which is set out in the retention table here. Chat transcripts clear sooner.

Payment partners, identity checks and the hosting and messaging suppliers that keep the platform running, each limited to what the job needs. We do not sell details on.

Two-step login protects the account itself, but a shared phone can remember an open session. Sign out when you finish and ask us to end active sessions.

A new version goes live here with a date and a short summary, and we message account holders before it takes effect. Using the account means you accept it.