LEGAL REFERENCE

Privacy Policy for your bv99 account

bv99 gives you a clear Privacy Policy before you open an account, so you can see what data we collect, why we use it and how long we...

Account dataPayment recordsDevice checksSupport privacy
Explore Lobby Read FAQ
bv99 Privacy Policy for your bv99 account

How our Privacy Policy applies

This Privacy Policy explains how bv99 handles your personal data when you create an account, enter the lobby, contact support or use payment rails available in supported regions. We collect details you provide, records created by account activity, device and browser signals, security logs and transaction references connected with JazzCash, Easypaisa, SadaPay and Raast. We use this data to run your account,

verify access, process requests, protect balances, answer privacy questions and meet legal duties where local law permits. We keep records only for the period needed for these purposes, then remove or anonymise them when retention is no longer required.

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

CONTACT ROUTES

Privacy help from bv99 support

If you want to ask about your data, we keep privacy contact routes separate from general lobby chat. Send the account email, the payment reference if relevant and a short request, and our team will check the record before replying. We may ask for extra account proof before sharing or changing personal data.

Team online

Privacy inbox

Email [email protected] for access, correction or deletion requests. Include your account email only, not passwords, card screenshots or full wallet PINs, so we can handle the request safely.

Live chat handoff

Start with chat if you are already signed in. Our agent can mark the issue as privacy related, record the time and move the case to the correct data team.

Payment record queries

For JazzCash, Easypaisa, SadaPay or Raast data questions, share the transaction reference and date. We use those details to locate the record without exposing extra account data.

CHECK SIGNALS

How we keep privacy checks clear

We write this Privacy Policy from the way bv99 actually handles account flows. Each point is tied to data we collect, store or delete during sign-in, payment checks, support contact and security...

Named data points

We list account details, device signals, payment references and support messages separately, so you can understand which record is created at each step instead of reading vague privacy language.

Local payment context

Where a payment rail is involved, we refer to JazzCash, Easypaisa, SadaPay or Raast by name. That helps you match our privacy wording to your own receipt trail.

Access protection

Before sharing personal data, we check account ownership through signed-in status, email control or transaction details. This prevents another person from using support to view your record.

Retention wording

We explain why certain records remain for security, accounting or legal needs. When a record is no longer needed, we remove it or detach it from your identity.

Policy change trail

When we edit the Privacy Policy, we update the page date and keep the wording plain. Material changes are placed where you can see them before continuing account use.

Support accountability

Privacy requests are logged with request type, date and response status. This lets us track whether access, correction or deletion matters have been handled by the right team.

Consistent wording across bv99 policies

Our Privacy Policy works alongside other bv99 legal pages without mixing their roles. Terms pages set account rules; cookie pages explain browser tools; this page explains personal data...

Account terms
The account terms explain conduct and access conditions. This Privacy Policy explains which personal data supports those checks, including identity signals and security records linked to your account.
Cookie wording
Cookie language covers browser storage and session tools. Here, we connect those signals to privacy purposes such as keeping you signed in and detecting unusual account access.
Payment terms
Payment pages describe transaction steps. This policy explains the related data trail, including wallet references, status updates and support messages connected with a Pakistan payment request.
Security page
Security wording explains account protection tools. The Privacy Policy explains how logs, device details and access alerts become personal data handled under limited internal access.
Support rules
Support pages tell you how to contact us. This policy explains what we record from that contact, including message content, timestamps and the outcome of your request.
Promo terms
Promo pages may set campaign conditions. This Privacy Policy only covers the data side, such as eligibility checks, account status records and message preferences linked to your profile.
Update handling
All linked policy pages use dates and clear section labels. That structure helps you see whether a privacy change affects account data, payment data or contact records.
LAYOUT MARKERS

Visible privacy cues on this page

We designed this Privacy Policy page so important data points are easy to scan before you continue with an account. Short labels, clear sections and named request paths...

Plain section labels Each section name tells you the exact privacy issue being...
Short data lists We group account, device, payment and support data into compact...
Contact placement Privacy contact options appear near the policy explanation, not buried...
Change date area The page keeps a clear date marker when the Privacy...
Security callouts Important security points are called out in simple language, including...
Pakistan context Where local access is discussed, the wording refers to supported...

Questions about bv99 privacy handling

We collect account details you provide, sign-in records, device signals, payment references, support messages and security logs. We use these records to run your account, protect access and answer privacy requests.

Payment references help us match JazzCash, Easypaisa, SadaPay and Raast activity to your account. They also support dispute checks, security monitoring and accounting duties where local law permits.

Yes. Email [email protected] from your account email and describe the data you want to access. We may ask for proof of account control before sending any personal record.

You can request correction if account data is wrong or outdated. We check the request against account ownership, then update eligible records while keeping required security and transaction logs intact.

We share data only when needed for account operation, payment processing, security checks, support handling or legal duties. Internal access is limited to teams that need the record for their task.

Retention depends on the record type and reason for collection. Security, transaction and support records may remain for set periods, then we delete or anonymise them when no longer needed.