Account terms
The account terms set rules for using 3dm, while this Privacy Policy explains what personal data is collected, why it is used, and how privacy requests are handled.
LEGAL REFERENCE
Privacy Policy For Your 3dm Account
3dm keeps live casino, slots and sportsbook account data under one Privacy Policy, with Pakistan payment context shown before you share details. Open your account in seconds and...
Pakistan privacy scopeJazzCash data contextCookie choicesAccount access records
How We Handle Your Privacy
This Privacy Policy explains what we collect when you create a 3dm account, browse the lobby, contact support, verify a withdrawal, or use a Pakistan payment rail where local law permits. We collect account details you give us, device and session data created by your browser, payment references from supported processors, security logs, and messages you send to our team. We use
that data to open and protect your account, process requests, detect account misuse, meet legal duties, and keep records tied to payments and support. We do not sell your personal data. We share limited data only with service providers who help us run verification, hosting, fraud checks, customer care, analytics, and payment processing. We keep data for as long as needed for
account operation, legal record duties, dispute handling, and security checks.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
HELP ROUTES
Privacy Help When You Need It
If you want to ask what data we hold, request a correction, or raise a concern about account privacy, use the contact path inside your 3dm account first. That route lets us link the request to your account without asking for repeated identity details. If you cannot access the account, use email or live chat and we will verify you before discussing private records.
Team online
Account inbox
Send privacy requests from the inbox after login. We can connect your message to your account ID, recent security checks, and payment references without exposing private details in open chat.
Live chat
Use live chat for urgent privacy concerns, such as an unexpected login alert or a device you do not recognise. Our team will verify account control before discussing personal records.
Email desk
Email works when you cannot reach your account. Include your 3dm username and the privacy request type only; we will ask for any extra verification through a safer channel.
POLICY CHECKS
How We Check This Policy
We treat this Privacy Policy as an operating document, not a decorative page. When our account forms, payment flows, cookies, or support tools change, we check whether the policy still describes what...
Named data categories
We separate account details, device logs, payment references, support messages, and verification files so you can see which type of data is involved in each privacy activity.
Local payment context
When JazzCash, Easypaisa, SadaPay, or Raast appears in your account flow, the policy explains that payment references may be stored for reconciliation, security checks, and dispute handling.
Security wording
We describe practical safeguards such as access controls, session monitoring, verification steps, and restricted staff access, without asking you to rely on vague privacy promises.
Update checks
We check the wording when account forms, cookie tools, payment screens, or support channels change, so the policy stays aligned with what you see on 3dm.
Contact clarity
The policy points you to account inbox, chat, and email routes, making it easier to ask for access, correction, deletion where available, or a privacy concern response.
Retention reasons
We explain why certain records may remain after an account action, including legal duties, payment disputes, fraud prevention, security logs, and unresolved support matters.
PAGE ALIGNMENT
Consistent Privacy Across 3dm Pages
Your privacy reading should not change from one legal page to another. We align this Privacy Policy with account terms, cookie wording, support text, and payment-facing notices so the same data categories...
Cookie notice
Cookie wording covers browser storage and similar tools. This policy connects those tools to session security, preference memory, analytics measurement, and fraud prevention checks.
Payment screens
Screens for JazzCash, Easypaisa, SadaPay, and Raast may show short privacy prompts. This policy gives the fuller context for storing payment references and verification outcomes.
Support scripts
Support prompts should collect only what is needed to identify your account and answer the privacy request. We avoid asking for full payment credentials in chat.
Security alerts
Login alerts, password resets, and device checks use account and session data. This policy explains that use as part of account protection and access control.
Withdrawal checks
Withdrawal verification may require identity, payment reference, and account activity checks. The policy explains why those records are needed before funds move out.
Form prompts
Short messages near registration or verification forms should tell you why a field is requested. This policy gives the broader privacy basis for those fields.
Policy Layout You Can Read Fast
We design this Privacy Policy so you can scan key points before sharing account details. The page separates collection, use, sharing, storage, rights, and contact routes...
Scope block
The opening block explains which 3dm activities are covered, including account creation, lobby access, payment references, support messages, cookies, and verification checks.
Data list
We list data types in plain language, such as contact details, login records, device signals, payment references, messages, and documents requested for verification.
Use reasons
Each main use is tied to a practical reason: account access, security, support, payment reconciliation, dispute handling, legal duties, and service improvement.
Sharing panel
The sharing panel explains when service providers may receive limited data, such as hosting, analytics, verification, fraud checks, payment processing, or customer care.
Rights area
The rights area tells you how to ask for access, correction, deletion where available, or restriction, with verification steps before private data is released.
Contact strip
A contact strip keeps privacy routes close to the policy text, so you can move from reading to asking a data question without searching elsewhere.
Privacy Policy Questions For Pakistan
We collect account details you provide, login and device records, payment references, support messages, cookie data, and verification material when needed. The exact data depends on the account action you take.
Payment references help us match account activity with JazzCash, Easypaisa, SadaPay, or Raast records, answer disputes, verify withdrawals, and detect misuse. We do not need your full wallet credentials.
We share limited data with service providers that support hosting, verification, payment processing, analytics, fraud checks, and customer care. We require those providers to handle the data for agreed purposes only.
Send a request from your account inbox where possible. We may verify your identity before releasing records, because privacy access should not expose your account data to another person.
Yes, you can ask us to correct inaccurate account or contact details. Some records, such as payment references or security logs, may need to stay unchanged for audit and dispute reasons.
We keep data only as long as needed for account operation, legal duties, payment disputes, fraud prevention, security checks, and support records. Retention periods may vary by data type.