LEGAL REFERENCE

How We Handle Your Data at geely slots

We keep this page in plain English so you can see exactly what we record when you open an account, fund it with JazzCash, Easypaisa, SadaPay, NayaPay or...

Sign-up record rulesWallet reference handlingSession and device logsHelp chat retention
geely slots How We Handle Your Data at geely slots

Where Our Privacy Terms Apply

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

REACH OUR TEAM

Questions About Your Stored Data

You do not need to hunt for a form. Message us from the help tab inside your account and we route privacy...

In-account help tab Send your request from the help tab once...
Email the data desk Write to the address shown in your account...
Callback within hours Ask for a callback and we ring the...
HOW WE CHECK

Who Writes and Checks This Policy

This policy is drafted by the same operations team that runs your account, then passed to our compliance and payment colleagues before it goes live. When a wallet provider changes how it...

Drafted by operators

The people who write these clauses also configure the payment flow, so the wording matches what happens when your JazzCash or Raast transfer lands in our ledger.

Payment team sign-off

Colleagues who reconcile Easypaisa, SadaPay, NayaPay and Raast settlements read the retention clauses before publication and flag anything that no longer matches the records we hold on file.

Version history archived

Every published draft is stored with its effective date, so you can ask which wording applied on the day you registered and get an answer that matches.

Plain-language pass

A second reader turns legal shorthand into everyday English before the page goes live, because a clause you cannot follow helps neither you nor us when a question comes in.

Support feedback loop

Questions that keep arriving in the help chat are logged, and when the same confusion shows up often we reword the section instead of repeating an answer each month.

Scripts listed by name

Our analytics and fraud tooling is named in the cookie section with the purpose of each script, so you can see what runs while you browse the lobby.

How This Page Matches Our Other Policies

We publish a small set of policy pages and they are read together. The terms page sets the rules of use, the cookies page lists what runs in...

Personal data rules
Matches the terms page on account eligibility, so the age and region conditions you accepted at sign-up appear in both places without rewording, now and after the next update.
Cookie scripts named
Lists the analytics, fraud and session scripts in the same order as the cookies page, so you can cross-check any entry without chasing a second list or table.
Payment clearing detail
Repeats the JazzCash, Easypaisa, SadaPay, NayaPay and Raast timing shown on the payments page, because settlement speed decides how long we retain a transaction reference on your file.
Account access terms
Uses the same login, device-binding and password-reset wording found in the security section of the terms page, so one set of rules covers every screen you open in the lobby.
Support hours aligned
Keeps the 9am to 9pm Pakistan time help window identical across every policy page, so you are never told two different things about when a reply arrives back.
Device and app behaviour
Describes mobile browser sessions, push permissions and cached lobby images in the same terms used in our app section, keeping one description whether you play on a phone or a desktop.
One date stamp
Carries the same last-updated date as the other legal pages published that day, so you can tell at a glance whether you are reading the current set of documents.

What You See on This Policy Page

Everything that matters sits on one screen, so you can skim it before you create an account. A short summary card opens each subject, a chip...

Summary card per section

Each heading opens with a two-line summary before the full clause, so you get the gist of how we store account and wallet data without reading every paragraph.

Wallet chip row

A single row shows JazzCash, Easypaisa, SadaPay, NayaPay and Raast, and each chip opens the clause explaining the reference we record from that rail once a transfer settles.

Numbered clause list

Every clause carries a stable number, so when you write to support about one paragraph you can quote that number and we both know which wording is under discussion.

Sticky section tabs

The tabs on the left stay in view as you scroll, letting you move from data storage to contact routes in a single tap instead of scrolling back and forth.

Language toggle

The page is written in Pakistani English, with the same wording used across our Pakistan-facing screens so a clause you read here matches what appears inside your account.

Printable version

A print-friendly view keeps headings, numbering and the effective date together on a few sheets, useful if you keep your own copy of the terms you accepted here.

Privacy Questions We Hear Often

We collect the name, date of birth, mobile number and email you enter, plus the wallet number you use with JazzCash, Easypaisa, SadaPay, NayaPay or Raast at sign-up.

Only what a rail needs to settle a transfer. JazzCash, Easypaisa, SadaPay, NayaPay and Raast each receive the reference and amount, never your lobby activity or stored card details.

As long as your account is open, then for the retention period our payment partners and applicable local rules require, after which the records are deleted or anonymised on schedule.

Yes. Message us from the help tab and we send a readable export covering your registration details, wallet references and support history to the email address on file.

We close the lobby and payment access immediately, keep the minimum transaction record that our payment partners require, and remove the rest in full once that window ends.

No. Our analytics scripts run on geely slots pages only, and the cookie clause names each one so you can see what fires before you accept or decline.