Account terms link
Our account terms explain service use, while this page explains personal data handling. Where both pages touch the same event, such as account closure, we keep the wording consistent.
LEGAL REFERENCE
Privacy Policy for your pl3 account
pl3 gives you casino, live tables and sportsbook access in supported regions, and this Privacy Policy explains how your account data is handled before you open the lobby...
Pakistan account privacyJazzCash and Easypaisa contextCookie controlsSupport contact paths
How we handle account data
This Privacy Policy applies when you use pl3.app, open an account, access your wallet, contact support or use our casino and sportsbook areas where local law permits. We collect the details needed to run your account, verify identity, process payments, secure access, respond to requests and meet legal duties that apply to our service. Payment references may show the rail you choose,
such as JazzCash, Easypaisa, SadaPay or Raast, but we do not publish your wallet details inside public areas of the site. Device data, cookie signals and session records help us detect account misuse, remember language choices and keep the lobby stable. We keep data only for operational, legal and safety reasons, then remove or anonymise it when retention is no longer required.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
CONTACT ROUTES
Contact us about privacy
If you want to ask about your personal data, correction requests, account access records or cookie choices, use the contact path that matches your case. We route privacy messages separately from lobby support so your request reaches the team handling account records.
Team online
Privacy email
Email privacy requests from the address linked to your pl3 account. Include your username and the request type so we can match your message with account records without asking for extra data.
Live chat handoff
Use chat when you are already signed in and need help finding privacy contact details. Our support agent can pass your request onward, but privacy decisions are handled through the dedicated channel.
Wallet query path
If your privacy question concerns JazzCash, Easypaisa, SadaPay or Raast references, tell us the transaction date and masked reference only. We do not need your full wallet access credentials.
CARE CHECKS
Policy checks inside pl3
We write this Privacy Policy from the way our service actually works. The policy is checked against account opening, identity checks, payment routing, cookie use, support handling and security logs so the...
Account flow matching
We compare policy wording with the fields you see when opening your account, including phone, email and identity checks. If a field changes, the related privacy wording is checked again.
Payment data mapping
Wallet references from JazzCash, Easypaisa, SadaPay and Raast are mapped to account ledgers, not public profiles. The policy explains this separation so you know where payment data sits.
Cookie purpose check
Cookie categories are tied to practical purposes such as session security, language display and fraud detection. We avoid vague labels and state why a browser signal may be read.
Access control
Internal access to account data is limited by role and work need. Support can view request context, while sensitive verification records have tighter handling and separate logging.
Retention review cycle
We check whether stored records are still needed for account operation, payment reconciliation or legal duties. When a record is no longer required, removal or anonymisation is applied.
Clear update signals
When policy wording changes in a meaningful way, we update the date and make the revised text available on this page. You can revisit it before continuing account activity.
POLICY PARITY
Consistency across pl3 policy pages
Privacy wording should not change depending on which legal page you open. We keep this page aligned with account terms, cookie wording and support procedures, while still making this Privacy Policy the...
Cookie wording link
Cookie text focuses on browser storage and tracking choices. This Privacy Policy connects those signals to wider account security, analytics limits and your ability to manage settings.
Support script match
Support replies about privacy are aligned with this page, so you receive the same route for access, correction and deletion questions whether you ask by email or chat.
Payment reference match
Wallet and bank reference handling is described in one consistent way across finance help and privacy text. We state that payment rails are used for reconciliation and account checks.
Security wording match
Security pages may discuss sign-in protection, while this policy explains related data use. Login records, device signals and risk flags are described without turning them into public account details.
Regional access wording
Where access depends on supported regions or local law, we keep that wording consistent. The privacy effect is simple: eligibility checks may require location and account status signals.
Update date alignment
When a connected legal page changes, we check whether this Privacy Policy also needs an update. That keeps related privacy details from drifting across the site.
Visible privacy markers on this page
This page is laid out so you can scan the privacy points that matter before opening or using your account. The visible markers help you find...
Collection labels
We group personal data by purpose, such as account access, identity checks, security and support. The labels show why the data is requested instead of leaving each field unexplained.
Local context chips
Short chips mention JazzCash, Easypaisa, SadaPay and Raast only as privacy context. They show where wallet references may appear in records, not as a separate product pitch.
Choice language
Privacy choices are written in plain Pakistani English so you can ask for correction, access or deletion without decoding legal jargon. Some requests may depend on retention duties.
Security cues
The layout calls out account security data, including sign-in logs and device signals. These cues explain why certain technical records are kept when you access the lobby.
Retention markers
Retention wording explains that records are kept for account operation, legal duties and payment reconciliation. It also states that removal or anonymisation follows when storage is no longer needed.
Contact prompts
Contact prompts sit near privacy topics so you know which route to use. The page separates routine account help from privacy requests that need dedicated handling.
Privacy Policy questions answered
We collect account details such as name, contact data, sign-in records, device signals, wallet references and support messages. The exact data depends on how you use the account and which checks apply.
Identity checks help us confirm that an account belongs to the person using it, protect withdrawals and meet legal duties in supported regions. Verification records are handled separately from public lobby activity.
No. We do not ask for your wallet password or app login. We may keep transaction references, dates, amounts and masked details where needed for reconciliation, support and account security checks.
Cookies help keep you signed in, remember display choices, protect sessions and measure site performance. Some cookies are necessary for account access, while optional categories depend on your browser settings.
Yes. Contact us from the email linked to your account and tell us which detail appears incorrect. We may ask for verification before changing records that affect identity, payments or account access.
We keep records for as long as needed for account operation, security, payment reconciliation and legal duties. When those reasons no longer apply, records are removed or anonymised where practical.