What Our Privacy Policy Covers
Everything you hand over to caf bet — your name, your JazzCash or Easypaisa transaction references, your device details — sits under one written privacy policy you can...
The Rules Behind Every Data Request
Our privacy position is easy to state and slow to change. We collect only what running an account needs: details used to verify you, payment references arriving from JazzCash, Easypaisa, SadaPay or Raast, and technical logs that keep sessions stable on mobile and desktop. We do not sell personal data, and we share it only with processors who help us operate and
only where local law permits. Retention differs by record type — transaction history is held longer than device logs because authorities in supported regions can ask for it. If the rules in your province give you extra rights over your own data, those rights apply to your caf bet account and we follow them. Where access is restricted by local law, we
do not open or keep accounts from those areas, and we delete what we can no longer hold lawfully.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
How We Handle Your Data
This policy is written and revised by the team that runs caf bet accounts day to day, not by an outside agency. We keep a version history, log every staff look-up of...
Named Data Owner
A single internal team owns this policy, writes each revision and signs off before changes go live, so accountability never sits with an unnamed department.
Version History
We date every revision and keep earlier versions on file, so you can see exactly what the wording said when you first accepted it and compare changes side by side.
Processor List
Payment and hosting partners that touch account data are listed by function, and we update that list whenever a processor changes or stops working with us.
Access Logging
Every staff view of customer records is logged against an individual login, which lets us trace who saw what and when if a question is raised.
Deletion Calendar
Each record type carries a set retention period, and once it passes, the data is removed from live systems and from scheduled backups in order.
Training Cycles
Support and operations staff repeat data-handling training on a fixed cycle, covering request handling, verification steps and what to do when something looks wrong on an account.
Keeping Every Policy Page Consistent
Other pages on this site describe your account too, and none of them should contradict this one. Where terms, wallet wording, verification steps or support times appear elsewhere...
| Terms Of Use Page | Your account terms and this privacy policy use the same definitions for account, wallet and verified user, so nothing is redefined between the two documents. |
|---|---|
| Cookie Notice | The cookie page names each category of tracker we run, and every category matches the data types described here, with no separate list to reconcile. |
| Account Security Page | Login protection steps described there line up with the access logging described here, so the security wording stays consistent wherever you read it. |
| Payments Page | Transaction wording on the wallet pages matches the payment references covered in this policy, including JazzCash, Easypaisa, SadaPay and Raast entries for Pakistan accounts. |
| Verification Page | Identity checks explained on the verification page follow the same retention rules we apply here, so documents you upload are held for one stated period. |
| Support Page | Response times published on the support page apply to privacy requests too, which means one set of expectations covers every message you send us. |
| Policy Change Log | When any sibling page is updated, we update this policy in the same release, so the whole set of documents stays on one shared revision date. |
What You See On This Policy Page
The layout you are reading is deliberate. A short summary sits above the full clauses, a jump menu lets you skip straight to the passage you need, and...