Terms of use
The terms page explains how an account works, while this notice explains the data behind it. Both define account, record and request the same way, so a clause cannot mean two things.
LEGAL REFERENCE
How rajaeropa slot Handles Your Account Data
Open an account and this notice spells out which details we keep, why we keep them and how you ask us to change them. It is written for...
Account records onlyWallet rails namedRemoval on request
What This Notice Covers In Pakistan
This notice sets out the data practices attached to your rajaeropa slot account, in the form they take where local law permits. When you register we collect your name, contact address, date of birth and the payment references tied to your funding rail, such as a JazzCash transaction number, an Easypaisa record or a Raast reference. We also log device and browser
signals to spot sign-ins that break your usual pattern. Access, storage and sharing rules differ between supported regions, so the wording here follows Pakistani requirements first. You can ask for a copy of what we hold, ask for a correction, or ask us to close the account and delete whatever we are not obliged to keep. Retention periods vary by record type,
and we state the span for yours when you write in.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
PRIVACY DESK
How To Reach Our Data Desk
Privacy questions reach a small team sitting with account support. Live chat is the quickest route during Pakistani business hours, and email is answered within one working day. When you write in about your records, include the address on your account and any reference number from the rail involved.
Team online
Live chat
Open the chat window from any lobby page and ask for the data desk. We keep a written copy of the conversation and send it to your account email once the session closes.
Write to our support address with data request in the subject line. Messages are logged, answered inside one working day, and any follow-up stays on the same thread.
In-account requests
Signed-in accounts can raise a request from the settings area. The form asks which record type you mean and whether you want a copy, a correction or a removal.
DATA STEWARDSHIP
Who Maintains This Notice
A named operations group owns this wording, and every change is versioned rather than quietly edited. We revisit the clauses on a fixed cycle, and sooner whenever a funding rail, a live...
Accountability
One operations group writes and signs off the wording, so a question about a clause reaches the people who drafted it rather than a general help queue or a scripted reply.
Version history
Every published change carries a date and a one-line summary of what moved. Older versions stay readable, so you can compare the wording that applied to your account earlier.
Plain language
We drop legal filler wherever a normal sentence works. Where a term has to stay technical, the sentence after it explains what that term means for your account.
Record access
Staff reach account records only where a support or fraud check needs them, and those sessions are logged. We describe the controls without publishing anything that would weaken them.
Local rails
The team maps how JazzCash, Easypaisa, SadaPay, NayaPay and Raast references move through our systems, because that is where most questions about stored records begin.
Desk access
You can reach the data desk without going through sales, and you never have to explain why you want a copy of your records or a correction made to them.
SIBLING PAGES
Keeping Policy Pages Aligned
This notice sits in a small family of policy documents, and we keep the definitions identical across them. Account terms, cookie wording and the fair-use page use the same vocabulary as this...
Cookie page
The cookie wording lists the small files a browser stores and the reason for each one. It links back here for the wider picture of what we hold and how long.
Account rules
Sign-in steps, checks and closure requests appear on the account rules page. Where those steps create a record, this notice explains the storage side of them.
Funding rails page
Each wallet and bank rail has its own page covering timing and reference formats. This notice covers what those references leave behind in our systems after a transfer clears.
Help centre
The help centre answers everyday account questions in short form. Anything touching stored data is mirrored here in fuller wording, with the same contact routes listed at the foot.
Fair use page
That page describes what keeps the lobby working smoothly for everyone. It points here whenever a check creates or reads a record attached to your account, and names the same desk.
Contact page
General contact details sit on one page and the privacy routes sit here. Both feed the same support queue, tagged so data questions reach the right team first time.
What You See On This Notice
The notice is built to be read on a phone between other tasks. A summary strip near the header states the scope in one line, jump...
Summary strip
One line near the header states what the notice covers and when it last changed, so you can judge in seconds whether the rest matters to you.
Jump links
A short list of anchors moves you straight to storage, sharing, removal or contact wording, so you skip clauses that have nothing to do with your own question.
Date stamp
Each card shows the day its wording last changed. When a rail such as Raast or Easypaisa updates its own rules, the matching card here is reissued with a fresh stamp.
Language toggle
Pakistani English leads, and the toggle keeps any translation beside the original rather than replacing it, so you can check a phrase against the wording we published.
Contact block
The footer block repeats the chat, email and in-account routes to the data desk, because the moment you want to ask something tends to arrive mid-clause.
Printable copy
A print-friendly layout drops the navigation and keeps the clauses intact, useful if you want a copy in your own files or for a family member who reads on paper.
Privacy Questions From Pakistani Accounts
Your name, contact address, date of birth and the payment references tied to your first transfer. We also record device and browser signals, which help us flag a sign-in that breaks your usual pattern.
We store the reference number and amount attached to a transaction, never your wallet password or PIN. That reference is what lets our support team trace a transfer when you contact us.
Yes. Write from the address on your account and say which period you mean. We send everything we hold in a readable format, usually within a few working days.
It depends on the record. Payment references are held longer than chat transcripts because of accounting rules, and we state the exact period for your account when you ask.
Only with providers who help us run accounts, such as payment processors and support tooling, and only where local law permits. Account records are not sold to outside advertisers.
Raise a closure request from your settings page or through the data desk. We close the account, delete whatever we are not required to keep, then confirm in writing what stays.