Privacy Policy for your d8888 account
d8888 keeps account data, wallet checks and privacy choices in one clear policy, so you know what we collect before you open your account. Read it first, then...
How d8888 handles your data
Our Privacy Policy explains how d8888 collects, uses, stores and shares data connected to your account, device, support chats and wallet checks. We ask for data that helps us run account access, verify transactions, respond to privacy requests, protect sessions and meet record duties in supported regions where local law permits. Payment references from JazzCash, Easypaisa, SadaPay and Raast are treated as
account records, not as open banking access. We may share limited details with service providers that help with hosting, fraud checks, customer support or legal requests. We keep access restricted, log internal handling and remove or anonymise records when they are no longer needed.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
How we keep policy text current
We maintain this Privacy Policy as an operating document, not a forgotten legal page. Product, support and security teams check the wording when account flows, wallet handling, analytics...
Named policy owner
A d8888 policy owner is assigned to keep wording aligned with real account handling. That person checks privacy requests, support...
Change record
When policy wording changes, we keep an internal record of what changed and why. You see the updated page text...
Support feedback
Questions sent through chat and email help us spot unclear privacy wording. If the same account data question repeats, we...
Security input
Session logs, login alerts and access controls shape how we describe data protection. Security staff confirm that policy wording matches...
Wallet alignment
When JazzCash, Easypaisa, SadaPay or Raast records are handled, finance and support teams use the same privacy wording. That keeps...
Plain English check
We write for clear Pakistani English rather than legal clutter. If a paragraph hides the answer you need, we shorten...
Aligned privacy language across account pages
Your privacy expectations should not change as you move from this page to account terms, cookie settings or support forms. We keep labels, request steps and retention wording...
| Cookie wording | Cookie consent, analytics tags and session storage use the same labels found in this Privacy Policy. That helps you connect browser data with account security and preference choices. |
|---|---|
| Account terms | Our account terms refer back to this policy when personal data is involved. The privacy page explains handling, while the terms explain your account use and platform rules. |
| Support forms | Support forms ask for only the details needed to answer your request. Privacy-related tickets use the same identity checks described here before access or correction steps begin. |
| Wallet receipts | Wallet receipt fields use stable labels across help pages and account screens. A Raast code or Easypaisa ID is treated as a transaction reference, not a password. |
| Login screens | Login and verification pages match this policy when they ask for contact details, device checks or one-time codes. We explain why those checks support account access. |
| Promo board | If the promo board uses account activity to show relevant offers, this policy explains that data use. You can ask us how your account preferences are applied. |
| Deletion path | Deletion requests use the same identity checks wherever you start them. We explain retained records, legal holds and removal steps in one place to avoid mixed answers. |
Privacy layout you can scan
We design this policy page so you can find the privacy point that matters before opening your account. The layout highlights scope, data categories, support routes...
Last changed marker
The page includes a visible change marker when wording is updated. You can return later and see whether the Privacy Policy has moved since your last account check.
Data category blocks
Account details, device data, wallet references and support messages are separated into clear blocks. That structure helps you see what each data category does inside d8888.
Request path cards
Privacy request cards show where to ask for access, correction or deletion help. Each route explains what we need from you and what we do not need.
Local wording
Pakistan wallet names appear where they affect privacy handling, not as decoration. JazzCash, Easypaisa, SadaPay and Raast references are linked to record care and support checks.
Security cues
Lock icons and short labels point to account access, session checks and restricted staff access. These markers help you spot privacy safeguards without reading every paragraph at once.
Choice language
Where a setting affects your privacy, we describe the choice in direct words. You see what changes, what stays required, and how to contact us if something looks wrong.