How lunabet casino Handles Your Account Data
Your account at lunabet casino collects only what keeps your sign-in, payments and game history working. This page explains what we store, why we store it, how long...
Privacy Terms That Follow Supported Regions
Where local law permits, we operate under the data rules of the supported regions we serve, so this policy sits alongside those requirements rather than replacing them. If you open an account from Pakistan, our handling of your sign-up details, device data and payment references follows the standards that apply in your province, and we say plainly when another jurisdiction changes how
long a record stays with us. JazzCash, Easypaisa, SadaPay and Raast each pass back a limited reference, usually a transaction ID and a masked mobile number. Where a local rule asks us to hold a record longer, we do; where it lets us delete sooner, we delete sooner.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
What Keeps Your Data Handled Properly
Account access sits behind practices we can point to, not vague promises. Records move over encrypted connections, staff accesses are logged against a name, and every data category carries a written retention...
Encryption in transit
Every page you load and every reference you send travels over an encrypted connection, so details handed to us by JazzCash, Easypaisa, SadaPay or Raast cannot be read in transit.
Named staff access
Our staff accounts are named individually, and every look-up of a customer record is written to a log holding the time, the operator and the reason given.
Data kept minimal
We ask for your name, mobile number and one payment rail, and we do not request salary slips or utility bills unless a supported-region rule requires that record.
Deletion on request
You can ask us to erase sign-in records and game history at any time, and we complete those requests inside the window set by the province where you registered.
Written retention periods
Each data type carries a set period, from thirty days for device tokens up to five years for payment records that Pakistani financial rules ask us to keep.
Plain wording
We write this policy in short sentences and skip legal padding, so you can tell what we collect, why it is needed and who else may see a copy.
How This Page Matches Our Other Policies
Nothing on this page should contradict what you read elsewhere on lunabet casino. Terms, cookie handling, financial record keeping, payment timings and verification all share the same retention...
| Terms of use | Our terms page sets out account rules and closures, while this policy sets out the data behind them; both share one retention table so a date never conflicts. |
|---|---|
| Cookie page | The cookie page lists what your browser stores, and here we explain account-side data; both name the same consent choices you can change in settings. |
| Anti-money-laundering page | Financial rules drive some record keeping, so that page and this one quote the same five-year figure for payment trails rather than two different numbers. |
| Payments page | Rails, timings and references sit on the payments page; the privacy side explains how long we keep a JazzCash reference and which staff can open it. |
| Bonus rules | Promotional conditions live on their own page, but the data each promotion collects, usually a wager log and a device token, is described here in the same wording. |
| Sportsbook rules | Settlement rules sit separately, yet the personal details behind a settled bet are covered here, including the match history we store and for how long. |
| Account verification | Verification steps appear on their own page and match this one: the same document list, the same deletion windows, and the same contact address if a request stalls. |
What You See On This Policy Page
We lay this page out so you can find your answer without reading every line. A summary strip opens it, a single retention table carries the timings, and...