LEGAL REFERENCE

How We Handle Your Account Data

We keep this page plain: your account data stays with us unless a payment check or verification step genuinely needs it, and you can ask what we hold...

Account dataPayment referencesCookie choicesAccess requests
cash casino How We Handle Your Account Data

The Data Behind Your Login

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

REACHING OUR DESK

Where Privacy Requests Land

One desk owns every privacy request, so nothing slips between teams. Write from the email tied to your account and a privacy...

Privacy email Send your request to our privacy desk and...
Live chat Use chat inside your account for a quick...
Help line Call our help line for anything urgent about...
WHO SIGNS THIS OFF

Oversight Behind Every Clause

Privacy copy here is owned, not outsourced. A named policy owner walks every clause each quarter against how the platform actually behaves — payment flows, verification steps, support...

Policy owner

One named lead signs off every change to this page and answers for how the wording matches what our systems...

Quarterly wording check

Four times a year we test each clause against live platform behaviour, then publish a revision stamp. Anything that no...

Partner confidentiality

Payment partners handle settlement data under contract and we audit what they return to us. We never hand your contact...

Access logging

Every internal view of your account leaves a trace with a name, a timestamp and a reason. Spot checks run...

Retention schedule

Active accounts keep records for as long as the account lives. Closed accounts move to a shorter window, then get...

Regional rule watch

We track privacy and payment rules across the regions we support, so a change in one market updates the practice...

SAME RULES ELSEWHERE

How This Page Matches The Rest

This page never argues with our other policy pages. Where a sibling page covers the same ground, the wording matches and only the level of detail changes. If you spot a clash...

01

Terms of use

The account terms set the contract, while this page explains how the data behind that account is handled. Read together, they stay consistent from sign-up to closure.

02

Promo rules

Promo conditions use the same definitions for eligibility, verification and record keeping, so a rule that applies to an entry also applies to the data we keep for it.

03

Account verification

Verification pages list which documents we ask for; here we cover how those documents are stored, who can open them and when they leave our systems.

04

Cookie notice

Cookie choices and the consent banner follow the retention logic described here, so switching a preference off in one place holds everywhere else on the platform.

05

Payment records

Settlement pages describe timing and references, while this page explains the data trail those references create and how long we hold it for reconciliation and disputes.

06

Device and app data

The app pages list supported devices and updates; here we explain the device signals we read, such as browser type and region, and why we keep them short-lived.

07

Complaints route

Complaint handling shares the escalation ladder used for privacy requests, so a data concern needing a second look reaches the policy owner through the route described here.

HOW THIS PAGE READS

Layout Choices That Keep It Clear

We built this page to be read once and understood, not skimmed and forgotten. Short blocks, plain headings and a chip row for each settlement route mean you...

Plain summary row Three short lines at the top say what we collect...
Rail chips JazzCash, Easypaisa, SadaPay and Raast each appear as a chip...
Jump links A sticky row of links takes you straight to collection...
Revision stamp Every update carries a date and a short changelog line...
Reading length The full text runs to a few screens on desktop...
Download and print Open the page in any browser and you can print...

What You Ask Us Most

Your name, mobile number, date of birth and login credentials, plus the reference behind each top-up. Documents are only requested when a local rule or a verification step needs them.

No full wallet or card numbers sit with us. JazzCash, Easypaisa, SadaPay and Raast pass through licensed partners, and we keep a transaction reference, an amount and a status.

Active accounts keep their data for as long as the account runs. After closure we hold records for a shorter window for reconciliation and dispute checks, then delete or anonymise them.

Yes. Write from your registered email to our privacy desk and we confirm receipt with a reference. Copies arrive within thirty days, and deletion follows once any open query clears.

Only with settlement partners that need a reference to complete a payment, and with an authority where a court order or regulator requires it. We never sell contact details.

Cookies keep your session and language choice steady, while device signals such as browser type and region help us spot odd logins. Both are covered in the cookie notice.