Shared definitions
Account, wallet, transaction and session carry the same meaning on every policy page we publish, so you never have to work out whether two clauses describe the same thing in different words.
LEGAL REFERENCE
How We Handle Your Account Data
This page sets out what aviator 888 collects when you open an account, how we store it and the choices you keep. You will find our cookie practices...
Account privacy summaryCookie and tracking controlsCopy, correct or delete requestsSupport hours in PKT
Where This Notice Applies To You
aviator 888 serves account holders in supported regions, and this notice explains the data practices behind your login. Because privacy rules differ between markets, how we answer certain requests depends on where you registered and where local law permits us to act. In Pakistan, we keep records of JazzCash, Easypaisa, SadaPay, NayaPay and Raast activity so a deposit or withdrawal can be
traced against your own account if you query it. Identity details are held only while verification needs them. Once the retention window closes, records are deleted or stripped of anything that identifies you. If a body with proper authority requests details, we hand over only what the request covers and tell you first where local law permits.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
HOW WE MAINTAIN IT
How This Notice Is Maintained
This notice is written and maintained by the team that runs aviator 888 rather than an outside agency. When our handling of data changes, such as a new payment route, a new...
Drafted in-house
Every paragraph is drafted by the people who run this platform, so the detail here matches what actually happens when you register, send money through JazzCash or ask us to close an account.
Revision dates
Each revision is dated and older wording stays on file internally. If you registered months ago, we can tell you exactly which version applied to your account at that time.
Change alerts
Material changes to how we use your data are flagged inside your account before they take effect, so nothing about your login, stored transaction records or marketing preferences shifts without you seeing it.
Data mapping
We keep an internal map of every field we hold, from name and date of birth to contact details and transaction history, and each one is tied to a stated purpose and retention window.
Access control
Staff access to personal records is limited by role and every lookup is logged. Someone handling a support ticket sees the fields that ticket needs and nothing beyond them.
Escalation path
If a reply from the privacy desk does not settle your concern, ask for it to be escalated to the person responsible for data handling, and we will set out any external options where local law permits.
ACROSS OUR PAGES
Consistency Across Our Policy Pages
Our policy pages are built to be read as one set. The cookie page lists the same tools described here, the terms page uses one meaning for account, wallet and transaction, and...
One cookie list
The cookies named on our cookie page are exactly the ones described here. Nothing is stored on your device that does not appear in that list, including the analytics that show us how the lobby loads.
Matching contact routes
The privacy email and chat route on our contact page are the same ones set out above, so a data question can be raised from whichever page you happen to be reading.
Aligned retention
How long we keep a transaction record is stated once and referred to everywhere else. JazzCash, Easypaisa, SadaPay, NayaPay and Raast entries follow one retention schedule across every page.
Consistent region wording
Our pages use one phrase throughout, supported regions and where local law permits, so a change in one document never quietly widens what we claim in another.
Transaction record terms
Answers about transaction history on our payments pages match what this notice says: we keep the reference, the amount and the date, not the credentials behind your wallet.
Updated together
When one of these documents changes, the rest are checked in the same sitting. A new cookie tool or a new payment route triggers an edit here and on the matching page.
WHAT YOU SEE HERE
Layout Of This Notice
Long policy text is awkward to read on a phone, so this notice is laid out in blocks you can scan. Each heading answers one question: what we...
Jump links
Short jump links near the beginning of the page take...
Field tables
Data fields sit in plain tables with the purpose and...
Plain headings
Headings read as questions rather than legal labels: what we...
Summary lines
Every section closes with a single sentence in larger type...
Local rows
JazzCash, Easypaisa, SadaPay, NayaPay and Raast each get a named...
Saved copy
You can save the whole notice as a file from...
What You Ask Us Most
Yes. Ask through live chat or the privacy email and we will send a copy of your profile, contact details, session history and transaction references. We aim to reply within a few working days.
We store the reference number, amount, date and status of each transfer, not the credentials behind your wallet. That record is what lets us trace a payment if you query it later.
Active accounts keep their records while the account is open. After closure we hold what transaction and verification rules require, then delete it or strip the identifying fields, depending on local law.
You can ask at any time. Where local law permits, we remove everything we are not required to keep and confirm in writing. Records tied to a completed transaction may stay for the set period.
Only with providers that keep the platform running, such as payment processors and the studio partners behind our live tables, and only the fields that job needs. We do not sell your details.
Open your account settings and turn off promotional messages, or tell the privacy desk and we will handle it. Service messages about your account, verification or a pending withdrawal will still reach you.