Shared definitions
Account data, verification record and payment reference mean the same thing here as they do on our terms page, so you do not relearn the language on every document you open.
Open this page and you will see exactly which account details aabet game records, why each field matters, and the controls that stay in your hands. We wrote...
Where local law permits, aabet game holds the role of controller for the account data you give us when you register from Pakistan. That covers your name, mobile number, email, date of birth and the JazzCash, Easypaisa, SadaPay, NayaPay or Raast reference attached to a balance load. We keep those references to match your ledger, never to profile how you spend. If
you reach us from outside Pakistan, or a supported region adjusts its own rules, this page still applies but retention windows, reporting duties and access rights shift with that jurisdiction, which is why we flag the region-dependent parts rather than treating one rule as universal. Verification files, chat threads and device signals stay only while a dispute, tax duty or fraud check
needs them. When a lawful request arrives, we answer it through a documented route and tell you where we are permitted to. Any change lands here first, dated, with older wording kept on request.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
The team answering your support tickets also maintains this page, so the wording describes what we actually do rather than what a template says. Each revision is dated...
This page is kept up by the aabet game team that handles accounts, not an outside agency. When a rule...
Every change carries the date it took effect, so you can compare what applied when you registered with what applies...
We describe JazzCash, Easypaisa, SadaPay, NayaPay and Raast handling the way our finance team processes it, including how long a...
We write for readers across Pakistan, so we drop imported legal phrasing where a short sentence works better. If a...
Before a revision goes live, a second team member reads it against the live account flow to confirm that the...
Sign-in uses a one-time code to your registered Pakistani mobile number, and our team will never ask for your password...
This page follows the same structure as our terms and cookie pages, so a clause moved in one place does not leave a stale sentence in another. When something changes, we edit...
Account data, verification record and payment reference mean the same thing here as they do on our terms page, so you do not relearn the language on every document you open.
The periods we keep transaction references and verification files are stated on this page alone, and the cookie page links back here instead of quoting a different number.
The chat, email and written-request paths listed here are the same ones shown on our support page, so no request ends up in a queue that nobody watches.
Where a rule depends on your province or country, we say so once and reuse that phrasing across pages, so supported regions never contradict each other in writing.
When a payment flow changes, we edit the privacy page, the terms page and the help articles in one working session, then publish the batch with the same date.
Cookie categories named on this page link straight to the page explaining them, so you move from a policy sentence to the actual control in two clicks.
The English version is the one we maintain and the one our team is trained on, so if any translated summary drifts, this page carries the wording we stand behind.
Every block on this page stands on its own, so you can jump straight to the part that touches your account. The order runs from what...
The first block states plainly what aabet game records when you register and what we leave alone, so you can judge in seconds whether the rest of the page is worth your time.
One block notes where provincial or national rules change retention, reporting or access rights, so you know which parts apply to an account opened from Pakistan and which do not.
Chat, email and written requests sit together with the reply times we hold ourselves to, so you never hunt through menus to find a person who can act on your question.
We list who writes and checks the wording, when it last changed, and how corrections are made, which gives you a reason to treat the page as current rather than archived.
A block explains how long verification files, chat threads and payment references stay on our systems, and what triggers an earlier deletion once a dispute has closed.
The closing block answers the queries our support desk fields most often, from what a one-time code proves to how a Raast reference is stored and who inside the company can see it.