LEGAL REFERENCE

Privacy Policy for your btpro account

btpro explains how we collect, use, protect and share your account data when you access our casino and sportsbook from supported regions in Pakistan. Read this Privacy Policy...

Pakistan account dataJazzCash contextEasypaisa contextRaast context
Explore lobby Read FAQ
btpro Privacy Policy for your btpro account

How we handle your personal data

This Privacy Policy covers the data you provide to btpro, the data created when you use your account, and the records we keep to operate access where local law permits. We may process your name, contact details, login activity, device signals, payment references and support messages. Payment references can include transaction IDs from JazzCash, Easypaisa, SadaPay or Raast, but we do not

ask you to send card PINs or wallet passwords. We use this data to create your account, secure sign-ins, verify withdrawals, respond to privacy requests, prevent account misuse and meet applicable record duties. We restrict access inside our team, keep logs for operational security, and remove or anonymise data when retention is no longer required.

Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.

CONTACT PATHS

Ask us about your privacy rights

If you need help with this Privacy Policy, contact us from the same account you use on btpro whenever possible. That helps...

Privacy email Send privacy questions to [email protected] with your account...
Account inbox Use the secure account inbox when your request...
Support chat Start chat for quick privacy routing, such as...
POLICY CHECKS

How we keep this policy current

We write this Privacy Policy from our operating workflow, not as generic legal filler. The wording reflects account sign-in, wallet reference checks, live casino access logs and sportsbook session records. When our...

Data flow mapping

We map account creation, login checks, wallet references, withdrawal verification and support contact paths so this Privacy Policy matches the data flows you actually meet while using btpro.

Access controls

Internal access to personal data is role-based. Support can see what is needed for your request, while sensitive verification records are restricted to staff handling account security tasks.

Payment references

For JazzCash, Easypaisa, SadaPay and Raast, we focus on transaction references, timestamps and status markers. We do not need your wallet password to process a privacy request.

Device security

We collect device and browser signals to detect unusual sign-in behaviour. These signals help protect your account and are handled under the security purposes described in this policy.

Retention checks

We keep data only while it is needed for account operation, dispute handling, security, legal duties or fraud prevention. After that, records are deleted or anonymised where feasible.

Policy versioning

When we change this Privacy Policy, we update the page date and keep the wording direct. Material changes are highlighted through account-facing messages where appropriate.

Consistency across our policy pages

Our privacy wording aligns with the account terms, cookie notice and withdrawal checks you may see elsewhere on btpro. Each page has a separate purpose, but the privacy...

Account terms
The account terms explain your service relationship with btpro, while this Privacy Policy explains the data behind that relationship. We keep definitions aligned to reduce confusion.
Cookie notice
The cookie notice describes browser storage and tracking choices. This Privacy Policy connects those tools to wider purposes such as security, session continuity and preference handling.
Withdrawal checks
Withdrawal checks may require identity or payment matching. This policy explains why those records are processed and how access is limited during verification and dispute handling.
Support records
Support pages ask for details needed to solve your issue. This Privacy Policy explains how messages, attachments and chat records are stored, accessed and retained.
Security pages
Security wording covers passwords, sessions and account protection. This policy adds the data angle, including device signals, login logs and unusual activity checks.
Regional access
Where access is limited to supported regions, this policy explains location-related data use. We apply it to keep services aligned with local requirements and risk controls.
Promo board
If you check the promo board, we may process account status and activity markers. This policy explains that use without turning promotion details into privacy promises.
CLEAR LAYOUT

Privacy markers you can spot quickly

We designed this Privacy Policy so you can scan the important privacy markers without losing the detail. Headings separate collection, use, sharing, retention and your choices. Short labels...

Plain sections Each section uses direct wording and short labels. You can...
Local context Pakistan wallet names appear where they matter to privacy, mainly...
Choice points We point out where you can ask for access, correction...
Security cues Security-related data is separated from general account data. That makes...
Sharing limits The policy explains when data may be shared with service...
Retention markers Retention wording is tied to account operation, disputes, security and...

Privacy Policy questions for btpro

We collect data you provide, such as contact details, account credentials, support messages and verification material. We also collect login logs, device signals, session activity and payment references needed for security and account operation.

No. For JazzCash, Easypaisa, SadaPay and Raast, we use transaction references, status markers and timestamps where needed. Never send wallet passwords or one-time codes to support or privacy email.

Device data helps us detect unusual sign-ins, protect your account and keep sessions working correctly. It may include browser type, device identifiers, IP-derived region signals and security logs tied to your account.

Yes, you can ask us to correct account data that is inaccurate or outdated. We may need verification before changing sensitive fields, especially where payments, withdrawals or identity checks are involved.

We keep records while they are needed for account operation, security, disputes, support handling, legal duties and fraud prevention. When those reasons no longer apply, records are deleted or anonymised where feasible.

We may share limited data with service providers, payment processors, security vendors and authorities where required. Each sharing case is tied to a purpose described in this Privacy Policy.

Contact [email protected] or use your account inbox with your request type and account email. For safety, we may verify you before releasing, correcting or deleting account-related data.