Privacy choices for your base 99 account
base 99 keeps your account data, device checks and payment references in one Privacy Policy so you can see what we collect before you join. Open your account...
How we handle your account data
Our Privacy Policy explains the data we collect when you create or access a base 99 account, including your name, contact details, login records, device signals and transaction references. We use this data to run your account, confirm access, detect unsafe account activity, process payment records and answer your privacy requests. For Pakistan access where local law permits, JazzCash, Easypaisa, SadaPay and
Raast references may appear in account checks, but we do not publish your payment details on public pages. We keep records only for operational, legal, security and dispute handling needs, then limit or delete them when retention is no longer required. You can ask us to correct, access or limit certain data, subject to identity checks and legal duties.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Contact us about privacy choices
Privacy requests need a clear route, so we separate account help from data rights requests. Tell us what you need changed or checked, and we may ask for matching account details before acting. This keeps your privacy request tied to you, not another account.
Email request
Send a privacy request from the email linked to your base 99 account. Include your account name, the data point involved and whether you want access, correction, restriction or deletion where available.
Live chat handoff
Use chat to ask where to send a privacy request, not to share sensitive identity files in the thread. Our team can move your case to a safer channel when documents are needed.
Account verification
Before we release or change account data, we match your request against login, contact and payment reference records. This step reduces the chance of another person reaching your private account details.
Trust signals behind this policy
We write this Privacy Policy from the way base 99 actually handles account records. The wording is checked against sign-in flows, payment reference handling, live casino access records and support case logs...
Account data mapping
We connect policy wording to actual account fields, such as contact details, sign-in records, device signals and verification status. That keeps the Privacy Policy aligned with what you see inside your account area.
Payment reference separation
JazzCash, Easypaisa, SadaPay and Raast references are handled as account records, not public profile details. We use them for reconciliation, fraud checks and support queries tied to your own account.
Access logs
We record security events such as sign-ins, device changes and failed access attempts. These logs help us protect your account and answer privacy questions about when your account was accessed.
Support case handling
Privacy messages are handled with tighter internal access than routine lobby questions. We limit staff visibility to the details needed to identify your account and resolve the specific privacy request.
Retention checks
We keep different record types for different periods, based on legal, payment, security and dispute needs. When a record no longer needs to be kept, we restrict or remove it under our internal process.
Policy change control
When we change how account data is collected or used, this Privacy Policy is checked before the change reaches you. The date and wording should match our current account handling practice.
Consistent privacy wording across pages
Your privacy rights should not change from page to page. We keep account, cookie, payment reference and support wording consistent so the same data practice is described the...
Privacy layout you can read quickly
We designed this Privacy Policy page to make important data choices easy to find. The layout separates collection, use, sharing, retention and request rights so you...
Clear section labels
Each privacy area is labelled around a real account action, such as creating an account, signing in, making a payment request or contacting support. That makes the policy easier to scan before you join.
Short data examples
We use practical examples like contact details, device signals and transaction references instead of vague legal wording. These examples help you understand what data may sit behind each account action.
Rights placement
Access, correction, restriction and deletion requests are grouped near the contact path. You should not need to search across unrelated pages to find how to raise a privacy request.
Local context chips
Pakistan payment names appear only where they help explain account records. JazzCash, Easypaisa, SadaPay and Raast are shown as context for references, not as a privacy distraction.
Security language
Security wording is placed beside data use, not buried at the end. We explain why login records, device checks and verification steps are part of protecting your private account.
Change notice area
Policy updates are handled in a visible area so you can tell when wording changes. We aim to make privacy changes readable before they affect how your account data is handled.