LEGAL REFERENCE

How luky games Handles Your Account Data

luky games keeps a written record of every account: the name it carries, the JazzCash or Easypaisa number you top up from, and the device you sign in...

Account data mapLocal payment railsRetention windowsSupport contacts

Explore The Lobby Read FAQ

Where This Policy Applies And Where It Does Not

luky games publishes this policy for account holders we can serve where local law permits, and it forms part of the agreement you accept when you open an account. If you sign in from a region we do not support, we may restrict access rather than hold your data. Regulators in different markets ask for different retention periods, so the windows described

here apply in supported regions and may be shortened where a local rule requires it. Nothing on this page overrides a mandatory local requirement; where the two conflict, the local rule wins and we tell you what changed. We also explain which team inside luky games can open each field, and how long a record is kept once an account closes for

good.

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

PRIVACY DESK

Reaching The Team Behind Your Records

Questions about this policy reach a small team, not a queue that closes on weekends. Write to [email protected] for a written answer...

POLICY ACCURACY

Keeping This Policy Accurate And Readable

Policy pages rot quietly, so we date every revision and say what changed at the head of the file. Our compliance lead checks the wording against live payment...

Stamped revisions

Every edit carries a date and a short line saying what moved, so you can scan the header and see...

Plain-language clauses

Each clause is written so a reader with no legal background can follow it: short sentences, named systems instead of...

Rail-by-rail checks

Twice a year we walk every path a Pakistani account can take, from JazzCash and Easypaisa through to SadaPay, NayaPay...

Support feedback loop

Agents tag every privacy question they answer and pass the list to our compliance lead monthly. When one clause keeps...

Change messages

If a revision changes how we store or share your data, you get an in-account message with a plain summary...

Internal data maps

We keep an internal map showing which team touches which field, how long it is held and who can open...

Same Rules Across Every Page We Publish

The wording here matches our sibling pages, so you are not hunting for a different definition of the same idea on each tab. Terms, cookies and account rules...

This page

Everything about collection, storage and sharing sits here. When another page mentions data in passing it points back to these clauses, so there is one source of truth.

Platform terms

The contract page carries the same definitions for account, holder and region. It covers what you may do here; this page covers what happens to the records that activity leaves behind.

Cookie notice

Cookies get their own short page because browsers ask separately. It lists each category we set, what it remembers and how long it lives, then defers here for who receives that data.

Account rules

Sign-in, device limits and verification steps sit on their own page. It explains when we ask for a fresh ID check, while this policy explains how long those verification files are kept.

Offer terms

Any running offer sets out its own eligibility window and the records it needs, then hands back here for storage rules, so one field never has two retention periods.

Security pages

Device protection, password guidance and how we handle a suspected break-in sit together on one page. It describes the controls; this policy describes the notices and log entries a triggered control creates.

Mobile app terms

The app stores a trimmed profile on your handset and syncs the rest when you reconnect. This policy explains what that cached copy contains and how to clear it.

How Our Data Pages Are Laid Out

luky games lays every policy out the same way so you can find a clause without reading every line. A stamp sits in the header, a...

Header stamp

The date and version sit in the header, above the first heading, so you can tell whether you are reading the current text or an older copy.

Summary box

Before the legal wording starts, a boxed summary gives you the short version in five or six lines, and the long clauses underneath fill in the detail.

Numbered headings

Every clause carries a number and a short name, so an agent can quote section 4.2 and you both land on the same paragraph, or you can link it onwards.

Contents rail

On desktop a slim contents rail follows you down the page, listing each heading and marking where you are. On mobile the same list collapses into a menu.

Downloadable copy

One button saves the whole policy as a file you can keep offline, handy if you want a copy before closing an account or sharing terms with family.

Contact strip

The footer of every policy page repeats the privacy inbox, chat hours and ticket reference field, so you never scroll back up to find where to send a question.

Straight Answers About Your Account Data

Your name, date of birth, contact details and the payment reference for your first JazzCash or Easypaisa transfer, plus sign-in device and IP so we can spot unfamiliar access.

Only with processors that keep the platform running: payment rails, identity checks, hosting and fraud screening. Each works under a written contract limiting them to our instructions, and nothing else.

Transaction and identity files stay for as long as a local rule requires, often five years, while marketing preferences drop off within thirty days and sign-in logs roll off sooner.

Yes. Ask for a record check from the email on your account and we send a compiled export within seven working days. Wrong addresses and mismatched references are corrected through live chat.

A small payments team and the fraud desk, both under access controls that log every view. Support sees only the last digits and the rail used, never your JazzCash or Raast credentials.

Nothing changes while the account stays open, except that routine messages pause if you disable them. Dormant accounts are flagged after a set period and we email you before any cleanup begins.

Send it to the privacy inbox with your ticket number and a short description. We acknowledge within two working days, investigate, then reply with what we found.