Your Privacy Policy, Set Out Plainly
Everything we hold about your clickbet app account sits under this one policy. Open your account in seconds and, from that first tap, we set out what we...
How We Hold Account Records
Where local law permits, we hold only what we need to run your account: your name, your contact number, a date of birth check, and the transaction records tied to your JazzCash, Easypaisa, SadaPay or Raast transfers. We keep those records for the period local record-keeping rules ask for, then clear them on a rolling schedule. You can ask what we hold,
ask us to correct it, and ask us to close your account and wipe your profile. Requests reach our privacy desk by live chat or email and we answer each one in writing. If this policy changes, the date at the head of the page moves and we flag it inside your account.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Reaching The Privacy Desk
Questions about your data should never sit unanswered. Our privacy desk runs alongside everyday account support, so you can raise a request by live chat, by email, or through the callback form in your profile. Say what you need — a copy, a correction, or full deletion — and we route it to the right queue.
Live chat queue
Open live chat from your account and ask for a copy of your records. Our agents confirm your identity, log it, and pass the request to the privacy desk that day.
Email the privacy desk
Write to us from the email address registered on your clickbet app account. That match lets us verify you quickly and reply in writing with what we hold.
Profile callback
Would rather talk it through? Leave a callback number in your profile and our Pakistan support line rings you back to work through the request at a time you choose.
How We Protect What You Share
Guarding your details is a daily habit here, not something we wrote once. Only staff with a specific role can open account records, every admin action is logged against a named user...
Role-limited staff access
Account records open only for staff whose role needs them. Each admin action carries a named user and a timestamp, and finance queues sit behind a second approval layer.
Encrypted connections
Traffic between your device and our servers travels over an encrypted connection, covering app sessions on mobile data and browsers on desktop, so a shared network cannot read it.
Two-step sign-in
Sign-in can be locked to a code sent to your registered number. Whenever you change handset or device, we ask for that code again before the account opens.
Tokenised card records
Card and wallet references are kept as tokens. Our processing partners settle your transfer with that token, which means readable numbers never rest on our side at all.
Retention windows
We attach a retention window to every record type, from registration fields to transaction history, and clear each one as its window closes instead of holding the lot.
Deletion on request
Ask us to close your account and the delete process starts, clearing profile fields and messaging permissions while keeping only what local rules still require us to hold.
One Set Of Rules Across The Site
This policy should never contradict the rest of our site. Where another page touches your account, we use the same definitions, the same retention windows and the same...
What You See On This Page
You should be able to see how your data is handled without hunting for it. The summary strip near the start gives you the short version, the jump...