Privacy policy
This page explains personal data collection, use, sharing, storage and contact choices. It is the main place to understand how fbajee handles account-linked records.
LEGAL REFERENCE
How fbajee Handles Your Data
Live casino tables, slots and sportsbook account flows create personal, payment and device data, so our privacy policy explains how fbajee collects, uses and protects it. Read this...
Account data useWallet record careSecurity checksSupport contact privacy
Privacy Position For Pakistan Accounts
This privacy policy applies when you access fbajee.page, create an account, manage your profile, use support, or complete account-related checks linked with our lobby. We process data to run your account, protect access, confirm wallet activity and respond to your requests. Where local law permits, we may keep records required for security, dispute handling and audit trails. We do not sell your
personal data, and we limit internal access to people who need it for account service.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
CARE CHECKS
How We Keep Policy Accurate
We write this policy from the same account flows we operate: registration, login checks, wallet reconciliation, support handling and withdrawal verification. Each privacy statement is meant to match how data actually moves...
Account flow mapping
We map each policy point to a real account step, such as phone verification, password reset, wallet reference capture or support chat. That keeps the wording tied to actual fbajee processing.
Local rail awareness
JazzCash, Easypaisa, SadaPay and Raast may produce different reference fields. Our policy treats those records as account-linked data and explains why we keep them for reconciliation.
Access control checks
Staff access to personal data is limited by role. Support teams see what they need for a case, while sensitive wallet and security records require stronger internal permission.
Security wording match
Policy language is checked against login alerts, device checks and password recovery screens. If the account screen collects a new field, the privacy wording must reflect that change.
Record retention logic
We keep data for service, legal, audit and dispute reasons, then reduce or remove records when they are no longer needed. The policy explains this without vague storage promises.
Plain language edits
We avoid legal padding where a direct sentence works. You should be able to see what data is collected, why we use it and how to contact us.
POLICY MATCH
Consistency Across Legal Pages
Our privacy policy is written to sit beside our terms, cookie notice and account rules without sending you in circles. The privacy page explains personal data handling, while the other legal pages...
Terms page
Our terms explain account use and service rules. When the terms mention verification or security checks, this privacy policy explains the related data handling.
Cookie notice
Cookie wording explains browser files, session tools and device signals. This privacy policy links those signals to login safety, preference storage and account protection.
Support scripts
Support replies follow this policy when asking for identity checks or case details. We ask only for data needed to resolve the privacy or account request.
Wallet records
Legal wording stays consistent when wallet references are used for reconciliation, reversal checks or withdrawal verification. The privacy policy explains why those records are retained.
Security messages
Login alerts and password reset messages match the policy language on device data and contact use. That helps you spot why a security message was sent.
Change notices
When legal wording changes, we keep the privacy impact separate from general service wording. Material data handling changes are placed where you can find them.
PAGE SIGNALS
Privacy Layout You Can Read
This page is structured so you can scan privacy points before you share data with fbajee. The opening explains the policy scope, the middle sections show how account...
Short scope markers
Each section names the data area it covers, such as...
Action-based wording
We explain privacy through actions you actually take: joining, logging...
Local context cues
Pakistan payment names appear only where they affect privacy records...
Security callouts
Security items explain why device details, timestamps and contact checks...
Contact clarity
Privacy contact routes are placed before deeper legal comparisons, so...
Update visibility
Policy changes are written in plain sections instead of hidden...
Common Privacy Questions Answered
We collect data you provide during account creation, login, wallet activity and support contact. This can include contact details, device signals, transaction references, security timestamps and messages you send to us.
Wallet references help us match JazzCash, Easypaisa, SadaPay or Raast activity with your fbajee account. We use them for reconciliation, withdrawal checks, dispute handling and fraud prevention.
No. We do not sell personal data. We share account records only where needed for service delivery, security checks, payment reconciliation, legal duties or support partners working under our instructions.
Yes, you can ask support to correct eligible account details. We may request verification before changing contact data or wallet-linked records, because those changes can affect account access.
We keep data for as long as needed to run your account, meet legal duties, handle disputes and protect the service. Some records may be reduced or removed when no longer required.
Cookies and similar tools help keep sessions active, remember choices and spot unusual access. They may connect device signals with your account when you log in or request help.
Contact support through your account area or email us with your registered contact and a clear request. Do not send passwords, full wallet PINs or private documents unless we ask.