Terms link
Our Terms explain account rules, while this policy explains the data used to apply those rules. We keep the two pages aligned so privacy wording matches account operation.
LEGAL REFERENCE
Privacy Policy for Your Account
bc app links your casino account details, sportsbook activity, payment records and support chats under one Privacy Policy. Read how we handle your data, then open your account...
Pakistan privacy contextJazzCash data handlingEasypaisa account recordsSadaPay and Raast checks
How We Handle Privacy Duties
This Privacy Policy explains how we collect, use, store and share data connected with bc app in supported regions of Pakistan. We collect account details you provide, device signals needed for access security, transaction references from Pakistani payment rails, and contact history when you ask for help. We use this data to create and protect your account, process withdrawals, confirm payment matches,
detect unusual access, answer privacy requests and keep records required for lawful operation. We do not sell your personal data. Where local law permits access, we may share limited data with payment processors, identity checks, security vendors and support tools that help us run the account flow. We keep privacy wording plain so you can decide whether to join with confidence.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
CONTACT ROUTES
Privacy Help From Our Team
If you need privacy help, contact us through the same account area you use for bc app support. We route privacy requests separately so account access, payment questions and data requests are not mixed.
Team online
Account privacy request
Use the account help form when you want a copy, correction or deletion check for your personal data. We ask for matching details before sharing anything back with you.
Payment data question
If your concern involves JazzCash, Easypaisa, SadaPay or Raast records, include the transaction reference and date. We check only the data needed to trace that account event.
Security access concern
Tell us quickly if you see a login or device you do not recognise. We can secure the account first, then explain what related data appears in our logs.
CHECKED WORDING
Policy Checks Behind This Page
We keep this Privacy Policy aligned with how bc app actually works. The wording is checked against account screens, payment flows, live support handling and security logging before it appears here.
Operator voice
The policy is written by us as the brand running bc app, not by a third party describing it from outside. That helps keep the data examples tied to real account steps.
Payment rail mapping
We describe JazzCash, Easypaisa, SadaPay and Raast as transaction contexts because those names appear in payment matching. The policy avoids vague wording where a local rail is involved.
Access log clarity
Device type, IP signals and login times are explained as security data. We use them to protect your account and to trace unusual access when you contact us.
Support record scope
When you contact support, we keep the chat or message trail needed to answer your request. The policy states why those records exist and how they relate to your account.
Retention checks
We keep account and transaction data only for periods connected with service, security, dispute handling and legal duties. Older records are restricted or removed when they are no longer needed.
Plain language edits
Privacy wording is kept in clear Pakistani English so you can understand account data, payment references and sharing rules without legal guesswork before you decide to join.
PAGE ALIGNMENT
How This Policy Stays Consistent
Our Privacy Policy connects with other legal pages without repeating them. Each page has a separate job, and this one stays focused on personal data, account records and privacy rights.
Cookie link
Cookie wording covers browser storage and similar tools. This Privacy Policy connects that data to account security, preferences and analytics only where those tools affect your bc app use.
Payment page link
Payment content may describe how a transaction moves. This policy explains the personal data around that movement, including references, account matching and checks linked to Pakistani rails.
Support page link
Support content tells you how to reach us. This page explains how we handle the name, contact details, screenshots and messages you send while we answer privacy or account questions.
Security page link
Security wording covers account protection steps. This policy adds the privacy angle by naming the login, device and risk signals we process to keep access safer.
Promo page link
If you choose to receive campaign messages, this policy explains the contact data and preference records involved. You can change those choices through account settings or support.
App page link
App content may explain access on mobile devices. This policy covers the related device data, session records and permissions that help bc app load and secure your account.
Privacy Layout You Can Scan
We designed this page so the Privacy Policy is easy to read before you open an account. The layout separates what we collect, why we use...
Clear section labels
Each part of the policy uses a direct label, such as account data, payment records or support chats. You can move straight to the privacy point you need.
Local examples
We use Pakistan-based examples where they matter, including JazzCash, Easypaisa, SadaPay and Raast references. That makes the privacy wording fit the account flow you actually see.
Short legal paragraphs
Long legal blocks are split into shorter sections so you can read the policy on a phone. We keep definitions close to the data use they explain.
Actionable contact points
Privacy contact routes sit near the data rights wording, not hidden away. If you want access, correction or deletion checks, the account help path is easy to find.
Data purpose pairing
Whenever we name a data type, we pair it with the reason we use it. Account setup, payment matching, security checks and support responses are kept separate.
Update visibility
When the Privacy Policy changes, we show the current wording on this page. Material changes may also appear through account messages where that contact route is available.
Privacy Policy Questions Answered
We collect details you provide during account setup, login and support contact. We also process device signals, session records and payment references needed to secure your account and match transactions.
We keep transaction references so we can match your account with the correct payment event, answer support queries and trace failed or delayed transfers. We do not treat those references as public profile data.
We share limited data with service providers that help operate bc app, such as payment processors, security tools and support systems. Each sharing purpose is tied to account service, safety or legal duties.
Yes. Contact us through the account help path and tell us what data you want checked. We verify your identity before sending account records or acting on correction and deletion requests.
Retention depends on the record type. Account, payment and security records are kept for service, dispute handling and legal needs, then restricted or removed when those reasons no longer apply.
Login data helps us recognise your device, protect your account and investigate unusual access. We use signals such as session time, device type and location indicators for security checks.
We place the current Privacy Policy on this page and may notify you through account messages when changes materially affect your data. You should read the latest wording before continuing.