Terms of use
Account rules, eligibility and withdrawal checks sit there. Nothing on this page changes those rules, and where a clause appears in both places the terms wording governs.
LEGAL REFERENCE
How We Handle Your Account Data
This Privacy Policy sets out what rajabets app collects when you open an account, which details travel with your JazzCash, Easypaisa, SadaPay or Raast deposits, and how long...
Account data explainedPakistani payment railsSupport hours in PKTYour choices, your account
Where Local Law Permits, Here Is Our Posture
We treat privacy as a living document rather than a fixed page, because data rules differ between supported regions. Where local law permits, we collect only what an account needs: your name, mobile number, date of birth confirmation, sign-in signals and the payment reference your bank returns. We do not sell your records and we do not pass them to advertising networks.
Your JazzCash or Easypaisa receipt number is stored so our desk can match a deposit when a transfer stalls. Verification records stay for as long as the rule in your supported region requires, then they clear on our standard cycle. If an authority asks for a specific record, we release only the fields that request names. You can ask what we hold,
request a copy, or correct anything wrong.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
PRIVACY DESK
Reaching the Team That Handles Data Requests
One team owns every privacy request, and you reach it through the same channels you already use for account help. Live chat runs while our desk is open, email is logged with a ticket number you can quote later, and in-app messages stay attached to your profile so nothing is lost between shifts.
Team online
Live chat
Open the chat panel and choose the data question option. Our desk answers in the order requests arrive and confirms in the transcript what was changed or released.
Email requests
Send from the address linked to your account and we reply with a ticket reference. That reference lets you follow one request across shifts without explaining details twice.
In-app messages
Message us from your account screen and the thread stays tied to your profile. It is the quickest way to ask what we hold, or to close an account and request deletion.
HOW WE CHECK
Who Reads This Policy Before It Ships
Every change to this policy passes three sets of eyes before it goes live. The compliance lead drafts the wording, a security engineer confirms the technical claims match what our systems actually...
Drafted by operations
The people who handle accounts daily write the first version, so the wording reflects real workflows such as deposit matching, device checks and withdrawal verification rather than abstract templates.
Checked by security
An engineer confirms every technical claim here, including how sessions are protected, how long logs stay and which internal roles can open a customer record. The sentence is rewritten whenever a system changes.
Read by support
Our desk reads each revision the way an account holder would, then flags sentences that need plainer words. Anything an agent cannot explain on live chat gets rewritten.
Revision log kept
We date every published version and keep older copies on file, so you can see what moved between two readings, and the log shows when it moved.
Regional rules checked
Because data rules differ between supported regions, we check this wording against the requirements where you hold your account instead of issuing one blanket claim worldwide. Retention lines are adjusted to match.
Your feedback counted
Questions that arrive often through chat or email become plain additions here. If one sentence keeps generating the same support ticket, that sentence is the problem and we rewrite it.
PAGE TO PAGE
How This Policy Sits With Our Other Pages
This page covers personal data only. Account rules sit on the terms page, settlement timing for each Pakistani rail sits in the payments area, and channel hours sit on our support pages...
Payments area
Settlement timing for JazzCash, Easypaisa, SadaPay and Raast lives there. The references we store and the reason we keep them are described here, so read the two side by side.
Support pages
Channel hours, languages and escalation paths live there. Our privacy desk answers through the same channels, so anything you learned about reaching us applies to a data request too.
Account security pages
Two-factor setup, device history and login alerts belong there. This policy explains why we record sign-in signals at all and how long those records survive before we clear them.
Cookie notice
Cookies, local storage and similar technologies get their own notice, because consent choices work differently from account data. We do not sell anything gathered through those technologies.
Regional notices
Where a supported region adds its own requirements, that notice sits alongside this page. Such additions narrow what we collect or shorten retention; they never widen our access.
What this page covers
Personal data, retention, sharing and your requests are all handled here. Keeping them together means you always know which document to cite when you contact the privacy desk.
ON THIS PAGE
The Elements You Will See on This Page
Structured headings, short summaries and expandable answers make this policy easy to skim on a phone. You will find the revision date near the start, plain summaries ahead...
Revision date shown
Every published version carries the date it took effect, so...
Plain summary blocks
Long clauses are preceded by two or three sentences in...
Retention table
One table lists how long each record type stays on...
Choice toggles
Optional messages and preference cookies have switches beside them, and...
Request form
The form at the bottom routes a copy, correction or...
Local rail context
Because you add funds through rails such as JazzCash, Easypaisa...
Data Questions We Hear Most
Your name, mobile number, date of birth confirmation, device and sign-in signals, plus the reference your bank returns for each deposit. We collect nothing beyond what an account needs to run and be verified.
We share only with processors who keep the service running, such as payment rails and hosting providers, and only the fields each one needs. We do not sell records or hand them to advertising networks.
Retention follows the rule that applies in your supported region. Sign-in signals clear on a short cycle, while transfer references stay longer so a disputed deposit can still be traced after settlement.
Yes. Submit the request form or message the desk from your account, and we confirm in writing once the copy is ready. Asking never restricts your account or changes your access.
Closing stops new activity and starts deletion of anything we are not required to keep. Records tied to a settled transfer may stay for the period your region requires, then they are removed.
Access is limited by role. Support agents see enough to resolve your ticket, security staff see sign-in history when investigating, and every internal view of a customer record is logged for audit.