Privacy Policy for your d77 account
d77 keeps your account data, verification records and Pakistan payment traces under one clear Privacy Policy before you open the lobby. Read how we collect, use, store and...
How this policy applies
This Privacy Policy explains how d77 handles data linked to your account, device, location signals, identity checks, support chats and transaction records in supported regions of Pakistan. We collect only what we need to run your account, protect access, meet legal requests where they apply and resolve payment queries with providers such as JazzCash, Easypaisa, SadaPay and Raast. We do not sell
your personal data. Some records are kept for security, audit, dispute handling and required retention periods. When a payment partner or verification service is involved, we share the minimum data needed to complete that specific check or trace.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
How to reach our privacy team
If you want to ask about your data, request access to account records or question a privacy decision, contact us through the channels shown inside your d77 account. We route privacy matters away from general lobby queries so your request reaches the right team.
Account message centre
Use the secure message area after login for privacy requests tied to your account. It lets us confirm ownership before discussing identity checks, payment traces, device access records or profile changes.
Support chat handoff
If you start in live chat, ask for a privacy handoff. Our support team can tag the conversation, collect the basic context and move the matter to staff trained on data handling.
Email follow-up
For longer requests, we may continue by email linked to your account. That route helps us send status updates, ask for missing details and keep a written trail of privacy actions.
How we keep policy wording reliable
We write this Privacy Policy from the way d77 actually operates account access, verification and Pakistan payment support. The wording is checked against our internal workflows, not copied from a generic template...
Operational checks
Policy wording is matched against real account actions, including login checks, password resets, payment references and support tickets, so the page describes processes we can actually follow.
Payment trace mapping
We map JazzCash, Easypaisa, SadaPay and Raast records by reference number, time stamp and account link, helping our team explain what data is kept when a transaction query appears.
Access control
Staff access to personal data is limited by role. A support agent can view only the details needed for a case, while sensitive verification material receives tighter handling.
Change tracking
When we alter this Privacy Policy, we track the reason, section affected and approval path. That makes updates easier to explain if you ask why the wording changed.
Local context
The policy reflects Pakistan account flows, including mobile wallets, bank transfer references and local support language, rather than assuming a payment setup from another market.
Plain wording
We avoid legal clutter where possible and state what data is collected, why it is used, how long it may be kept and how you can question a record.
Privacy wording across d77 pages
Your privacy position should not change depending on where you read it. We keep the Privacy Policy aligned with account screens, support replies and transaction forms, so data...
What the privacy page shows
We structure this page so you can scan the main privacy controls before creating an account. The layout focuses on collection, use, sharing, retention and contact...
Collection snapshot
This area explains the categories we collect, including account details, device signals, transaction references and support content. Each category is tied to a clear operating purpose.
Use reasons
We state why data is used, such as account setup, security checks, transaction handling, support follow-up and legal response where local law permits in supported regions.
Sharing boundaries
The sharing section names practical partner categories, including payment processors, verification providers and technical vendors, while making clear that sharing must support a defined account purpose.
Retention window
Retention wording explains that some records are removed when no longer needed, while others may remain for audit, dispute handling, security checks or required legal periods.
Your choices
We explain how you can request access, correction or deletion where available. Some requests may need identity confirmation before we change or release account records.
Update marker
Policy changes are shown through revised page wording and internal change records. If an update materially affects your data, we aim to make the change visible.