Account form wording
The account form asks only for details linked to access, contact, verification and payment records. The Privacy Policy explains those same purposes without adding hidden meanings.
LEGAL REFERENCE
Privacy Policy for your 3dd account
3dd keeps its Privacy Policy beside the account flow so you can see how your data is collected, used and protected before you join. Open your account after...
Pakistan privacy contextJazzCash recordsEasypaisa recordsRaast checks
How we handle your account data
Our Privacy Policy explains what we collect when you create an account, confirm your device, enter the lobby, contact support or request a payout where local law permits. We use account details, session logs, payment references and security signals to operate 3dd, protect access, answer you properly and meet record duties in supported regions. We do not write this policy as a
vague legal page; we link each data use to a real account action. JazzCash, Easypaisa, SadaPay and Raast references may appear in records so we can match cash-in and payout requests, but we keep payment handling separated from public page activity.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
CHECKED COPY
Why this policy stays practical
We write the Privacy Policy around the systems you actually touch on 3dd: account creation, login checks, lobby sessions, support tickets and Pakistan payment references. The policy is checked when forms, verification...
Local record context
Pakistan payment names appear only where they help explain account records. JazzCash, Easypaisa, SadaPay and Raast references are used to match your requests accurately.
Device checks
We explain device and session data because it helps secure account access. Browser type, login time and location signals support account checks and misuse detection.
Support separation
Privacy requests are not mixed with promo questions. When you ask about stored data, our support path directs the case toward account record handling.
Clear retention language
We describe why some records stay longer than others, including payout references, support replies and security logs needed for account operation.
Access controls
Internal account records are limited to staff roles that need them. The policy explains that access depends on support, security or payment record duties.
Change tracking
When we adjust the Privacy Policy, we keep the page dated and readable so you can spot policy changes before continuing with account actions.
PAGE MATCH
Consistency across our privacy pages
3dd keeps privacy wording aligned across the account area, support forms and legal pages. This helps you see the same data purpose wherever you read it. If a screen asks for a...
Login page wording
Login screens mention device checks because session security matters. The Privacy Policy expands that point by explaining timing, browser signals and unusual access checks.
Payment record wording
Cash-in and payout pages use references from JazzCash, Easypaisa, SadaPay and Raast. The policy explains how those references support matching and account history.
Support form wording
Support forms ask for enough detail to answer you safely. The policy explains why screenshots, account names or contact numbers may be requested.
Security message wording
Security alerts may mention device, password or location checks. The Privacy Policy explains those signals without exposing internal checks that could weaken protection.
Cookie wording
Cookie text stays linked to session continuity, language choice and performance checks. We avoid vague labels and explain how browser storage supports account use.
Update wording
When legal text changes, the policy page carries the updated wording. We keep account prompts consistent so you do not face conflicting privacy statements.
Policy layout built for quick reading
The Privacy Policy page is arranged so you can scan account data topics before opening the lobby. Short sections cover collection, use, sharing, storage, security and...
Plain section headings
Each policy heading uses direct wording, so you can jump from account data to security records without reading legal filler or unrelated platform copy.
Short record examples
Examples mention real account actions, such as login checks, support tickets and payout references. This keeps privacy language tied to what you actually do.
Readable on mobile
Policy text is broken into compact blocks for phone screens. You can check data use before joining, without pinching through long legal walls.
Local naming
We use Pakistan payment names as written in your account flow. JazzCash, Easypaisa, SadaPay and Raast stay consistent across privacy wording.
Action links
Support links sit close to privacy topics, so you can ask about correction, access or security records right after reading the relevant section.
Policy date
The page includes a clear update marker. When wording changes, you can compare the new version with your recent account activity.
Privacy Policy questions we hear
We collect account details, contact data, device signals and security records needed to create access, protect your login and connect support replies to the right profile.
JazzCash, Easypaisa, SadaPay and Raast references help us match cash-in and payout requests to your account records. They are used for tracking, support and verification.
Yes. Device and session signals help us spot unusual access, confirm account activity and protect sensitive changes. The policy explains these checks in plain terms.
You can contact support about correction requests. We may ask for account proof before changing stored details, so the update is linked to the correct profile.
Retention depends on the record type. Support tickets, payment references, login logs and verification records may remain while needed for account operation and legal duties.
We place updated wording on this page and keep the change visible near the policy text. Check it before account actions if privacy wording matters to you.