LEGAL REFERENCE

How rajbet app Handles Your Account Data

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...

What we record at sign-upJazzCash and Raast handles protectedCorrection and closure requestsRevision dates shown openly
rajbet app How rajbet app Handles Your Account Data

Where This Policy Applies For You

Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.

ASK THE DESK

Raise Any Privacy Question With Us

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.

Team online

In-app chat

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.

Privacy mailbox

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.

Profile controls

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.

WHO WRITES THIS

The Team Behind Every Line

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...

Privacy lead

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.

Payments team

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.

Support desk

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.

Security engineers

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.

Compliance checks

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.

Dated updates

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.

PAGE CONSISTENCY

How Our Policy Pages Line Up

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...

01

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.

02

Shared retention clock

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.

03

One request queue

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.

04

Matching service wording

JazzCash, Easypaisa, SadaPay and Raast are described the same way everywhere, and no page quietly advertises a feature that another page rules out.

05

Aligned dates

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.

06

Nothing hidden

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.

07

Shared structure

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.

PAGE LAYOUT

What You'll See On This Page

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...

Summary block The opening block hands you the short version before any...
Collapsible clauses Longer paragraphs sit inside blocks you open one at a...
Service chips Small chips name JazzCash, Easypaisa, SadaPay and Raast wherever a...
Revision date A dated line just below the title tells you when...
Plain headings Every clause carries a short heading written in everyday English...
Direct contact links Links at the foot of the page jump straight to...

Privacy Questions We Hear Often

Your mobile number, the name and date of birth you enter, the payment handle used when you add funds through JazzCash, Easypaisa, SadaPay or Raast, and basic device details that keep sign-in working.

Only what a transfer needs: the handle, the amount and a reference number. Nothing else leaves our records, and partners are bound by contract to use it for that single transaction.

Accounting and anti-fraud rules in Pakistan require some transaction history to stay for a set period. We keep that minimum, then delete the rest, including marketing preferences.

Sign in, open your profile and edit the field yourself. If the change needs proof, talk to the privacy desk on chat and we confirm it within two working days.

We tie sessions to your device and expire them after a set idle period, so a shared handset asks for your credentials again. Keep your PIN private and sign out on borrowed phones.

Send it to our privacy mailbox or in-app chat with your registered mobile number. We acknowledge within one working day and give you a written answer after the desk works through it.

Yes. We post the revised text here with a new date, and where a change affects how your data is used we message your registered number before it takes effect.