Same definitions everywhere
Terms such as account, settlement record and retention mean the same thing on this page, in our terms of use and in our payment terms, so a request never depends on which document you opened.
LEGAL REFERENCE
How luck 888 Protects the Details You Share
Your account at luck 888 runs on a simple promise: we collect only what a deposit, a wager or a withdrawal actually needs, and we say plainly what...
What we collectWhy we hold itHow to ask for changesSupport across Pakistan
How We Handle Records Across Supported Regions
Where local law permits, luck 888 stores your account records in the regions we serve and follows the rules that apply to you when you open the account. Your name, date of birth, contact details and identification document are held so we can confirm you are old enough to hold an account and so withdrawals match the person who funded them. References
from JazzCash, Easypaisa, SadaPay, NayaPay and Raast sit in your file as settlement records, never as advertising material. We do not sell your details. In supported regions we share the minimum needed with payment partners, verification providers and authorities that make a lawful request. If a rule in your area changes and we can no longer serve you, we tell you before
it takes effect.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
POLICY OVERSIGHT
How We Keep This Policy Accurate
A policy is only worth reading if it matches what the platform does. Our compliance and engineering teams read this page beside the live product each quarter, and it is amended whenever...
Checked against the live platform
Every version of this page is read beside the working product rather than from memory. When a rail such as Raast changes how settlement references return, the wording here is corrected.
Owners named for each clause
One compliance lead and one engineering lead sign off each amendment. If you ask who set a retention period, support can name the role responsible and the date recorded.
Amendment date you can follow
We print the date of each change at the foot of the page and mark which clauses moved. Earlier versions stay available if you ask for them.
Plain words, twice checked
The drafting rule is that a sentence must survive being read aloud. Legal phrasing is kept to a minimum, and any clause that cannot be explained simply is rewritten again.
Support feedback feeds the page
Questions that arrive again and again through chat and email are treated as a sign that a clause is unclear. Those subjects go on a list for the next pass.
An escalation that ends somewhere
If a data request is refused, you are told which clause applies and who to write to next. Escalations go to a named manager rather than the same queue.
MATCHED WORDING
How This Page Lines Up With Our Others
This page sits alongside our terms of use, our cookie notice and our payment terms, and the wording is kept consistent across all of them. Words such as account, settlement reference and...
Retention periods that match
The retention windows quoted here tie back to the periods named in the payment terms, and both pages state the same number of years for a settlement record.
One set of support routes
Chat, email and callback are the same routes on every policy page, so a question about your data never sends you to a channel that only handles transactions.
Device wording kept in step
The cookie notice explains what sits on your device, while this page explains what we hold on our side. Read together they describe the full picture.
Updates land together
When a change touches more than one policy, the edits are published in the same release rather than staggered. That keeps every cross-reference between pages accurate for you.
Contact details kept identical
The data desk address, the chat route and the callback request match across every page. If a channel closes, all pages are corrected in the same update.
Consistent language support
Pages are drafted in Pakistani English and the same rules apply to each. Urdu replies from support follow the same definitions, so meaning does not drift.
The Layout You See on This Policy Page
The page is built to be skimmed before it is read properly. A dated header shows when the text last changed, short headings group related clauses...
Dated version header
The date in the page header marks the last change to any clause. If you saved a copy earlier, compare the two dates to see what moved.
Short clause headings
Each block of clauses carries a brief heading so you can find retention, sharing or device data without reading the whole page. Headings use ordinary language rather than legal shorthand.
A request form in your profile
A short form raises an access, correction or deletion request and files it against your account, so you never describe the same problem to two teams.
Language options explained
The text is written in Pakistani English and support replies are available in Urdu. Where a term is unclear, the same definition holds in both languages and support can explain either version.
Export of your own records
You can pull the account and settlement history we hold from your profile at any point. The export arrives as a readable file rather than a raw database dump.
Links that open the right clause
Every mention of the terms of use, the cookie notice or the payment terms opens the exact paragraph referred to, so you can check how two documents fit together.
Questions We Get About Your Data
Your name, date of birth, contact details, one identification document and the settlement reference from each transaction you make through JazzCash, Easypaisa, SadaPay, NayaPay or Raast.
Only payment partners, identity verification providers and authorities making a lawful request in a supported region. We do not sell account records or hand your documents to advertising partners.
Settlement and identification records are held for as long as local rules require, while chat transcripts are kept for a shorter period. The exact window is confirmed when you close the account.
Yes. Raise a request inside your profile, we verify your identity, then the export arrives as a readable file. We explain in writing if any part has to stay withheld.
Access runs over encrypted connections, sessions expire when you sign out, and payment references sit against your account rather than in open text. Two-step verification on your email adds another layer.
We publish the updated text with a new date and flag which clauses moved. If a change alters how your data is used, you are told before it takes effect.