Identical definitions
Wherever account data or payment handle appears on this site, it carries the same meaning on the cookie page, the account page and here, with no quiet exceptions.
Your rajbet app account comes with a privacy policy you can actually read: what we record when you register, why we hold it, and how you ask us...
This policy covers your use of rajbet app from Pakistan and from any supported region where local law permits online account access. We decide why your account data is held: the name and contact number you give, the date of birth you enter, and the payment handle you use when you add funds through JazzCash, Easypaisa, SadaPay or Raast. Where a provincial
or federal rule differs from this page, the local rule wins, and we write to you before changing how your records are treated. Payment partners and hosting teams only receive what a task needs and are bound to use it for nothing else. Close your account and we keep a small set of records for as long as accounting and anti-fraud rules
demand, then delete the remainder. Any change to this policy appears here with a fresh date.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Privacy requests should not mean a long queue. Our support desk handles policy questions in English and Urdu through in-app chat and email every day, and most data requests get a written answer inside two working days. Bring your registered mobile number and tell us which clause you want explained or changed.
Open the help tab inside rajbet app between 9am and 1am Pakistan time and ask the desk what we hold on your account. Replies land in the same chat thread.
Write to our privacy mailbox with your registered mobile number and the change you want. We confirm receipt within one working day and follow up by email afterwards.
Sign in and open your profile to see the contact details on file, fix a mistyped number yourself, or start an account closure request without waiting on anyone.
A named privacy lead keeps this page current, working with the payments and support teams that handle your account every day. We check each paragraph against how the platform genuinely behaves before...
One named person owns this policy, signs off every revision, and sits with the payments team whenever a clause about JazzCash or Easypaisa transaction records is drafted or rewritten.
The people who watch JazzCash, Easypaisa, SadaPay and Raast settlements wrote the sections explaining which transaction records we store, what we pass to a payment partner, and when we destroy the copy.
Our agents read this page every week, so the answer you receive in chat follows the policy wording rather than a separate script that was written once and never touched again.
The team running encryption and sign-in controls confirms each sentence about access, retention and our deletion schedule, and flags anything the platform cannot honestly promise to a reader.
Where Pakistani rules or a processor contract set a stricter term, we amend the wording here before release instead of leaving an outdated clause sitting on a live page for months.
Every revision carries the month it went live, so you can spot what moved since your previous read and ask us about any single line you disagree with.
Cookies, withdrawals and account rules each get their own page, and all of them read from the same definitions. A term that appears twice means the same thing in both places, so...
Wherever account data or payment handle appears on this site, it carries the same meaning on the cookie page, the account page and here, with no quiet exceptions.
The record-keeping periods quoted in this policy match the ones printed on our withdrawal page, so a timeline you read once stays true wherever you find it.
Data requests and complaints reach the same desk whether you start from this policy, the account page or an in-app help link, and they keep the same reference number.
JazzCash, Easypaisa, SadaPay and Raast are described the same way everywhere, and no page quietly advertises a feature that another page rules out.
When we revise one policy page we date the change across the whole set, so no older copy lingers online carrying a different revision month or wording.
No side page quietly overrides this policy; any extra condition links back to the exact paragraph it changes, so you can read both together and see the full picture.
Our pages use the same headings and reading order, which makes moving between them feel like switching tabs inside one document rather than starting over each time.
This page is built for reading on a Pakistani mobile connection: a short summary right after the heading, collapsible clauses underneath, and chip rows naming the services that...