Slots / Live
laki5 sets out how we collect, store and use the details tied to your account — from the mobile number used at signup to the records behind every Nagad or Bank Transfer entry you make. Access to our lobby and support routes still depends on your local law and eligible regions.
This policy covers the personal details you give us when you open an account with laki5, and the activity data our systems record once you're signed in — device type, session timestamps, and the payment method you select at the wallet screen. We don't sell your details to outside advertisers; the data we hold is used to run your account, confirm a Nagad transfer or Bank Transfer entry, and respond to a support question you raise. Because access to laki5 varies across different parts of Bangladesh, and because online gaming rules differ by region, what we can store, for how long, and who we can share it with depends on your local law and eligible regions — this policy doesn't override that. If a payment partner such as Nagad or a bank handling a Bank Transfer needs limited transaction details to confirm your entry, we pass only what's required to complete that step; we don't hand over your full account profile. Cookies on our site help keep you signed in across devices and remember a few display choices — nothing more invasive than that. We revisit this policy from time to time as our lobby, payment routes or local requirements change, and the version live on this page is the one that applies to your account at any given moment.
This policy draws a line around what laki5 is responsible for and what sits with a payment partner or your own device. Account access, transaction entries, the pages you browse inside our lobby, and the limited data we share with outside services each fall under a different part of this scope. Reading the breakdown below helps you know where to raise a question before you send it.
This policy covers the login details you use to reach your laki5 account — your registered mobile number, password, and the device fingerprint our system notes when you sign in. It does not extend to any outside app or browser setting you control on your own phone.
Entries made through Nagad or a Bank Transfer fall inside this policy once they touch your laki5 wallet record. The actual processing done by your bank or Nagad's own app sits under their separate terms, which we don't control or rewrite here.
Pages you browse inside our lobby — game listings, the sportsbook section, help articles — are covered when we log which pages you viewed to improve navigation. We don't track what you do on sites outside laki5 once you've left our domain.
Where we rely on a payment partner or a basic analytics tool to keep the site running, this policy explains what limited data moves across. It does not describe the privacy practices of the Nagad app or your bank directly, since those sit under their own separate terms.
You can ask us what account data laki5 holds about you at any time, and we'll point you to the record visible in your account settings or confirm it through a support reply. If a mobile number, name spelling or linked payment detail looks wrong, you can request a correction through the same support route rather than editing sensitive fields yourself. Raising a question about how we use your data, or asking us to stop a specific use, is handled case by case against your local law and eligible regions, since not every request can be actioned the same way everywhere. We keep this process straightforward: tell us what you need checked, give us enough detail to locate your account, and we'll respond through the published support channel rather than leaving you to guess.
Open your account settings to see the core details we hold, or ask our support route to confirm what's on file for your mobile number and payment history.
Spot a wrong spelling or an outdated mobile number? Flag it through support rather than retyping sensitive fields yourself, so the change is logged correctly.
If you want to know why we hold a specific entry, or ask us to limit a particular use, send that question through the same support route we publish.
Every request is tracked against your account so you're not asked to repeat the same explanation twice when a follow-up reply is needed.
A privacy question doesn't need a separate account — the same routes you'd use for a wallet query work here too. Chat from your signed-in session, open a support form from the help page, or check the help page itself for the current list of published routes. Each path lands with the team that handles account, cookie and payment-record requests, so you're not routed somewhere unrelated. Keep your account details ready when you reach out, since that's how we match a request to the correct record without back-and-forth.
Open the chat icon from your signed-in laki5 account to ask a privacy or data question directly; this routes your message straight to the team that handles account, cookie and payment-record requests, so you don't need to repeat your account details twice.
If chat isn't open, the support form on our help page lets you describe a data, cookie or payment-record question in writing, with your account reference attached so the team handling privacy requests can match it to your laki5 account without extra back and forth.
Our help page lists the published routes for account, wallet and policy questions, including how to flag a Nagad or Bank Transfer entry that looks off, or ask us to check a cookie or data record tied to your laki5 sign-in.
We keep what we collect tied to what's actually needed to run your laki5 account — nothing stored for its own sake. Cookies, sign-in details and payment records each have a defined purpose, and we explain each one below rather than bundling them into one vague statement. Retention follows how long your account stays active or how long local law asks us to keep a record, whichever applies in your region. If anything looks off, or you want a change made, the support route is the place to raise it rather than guessing at a setting yourself.
We record what's needed to run your account — signup details, session activity, device type, and the payment method you pick, such as Nagad or Bank Transfer — and we keep that scope narrow rather than pulling in data we don't need for your account.
Cookies keep your session active across pages and remember basic display settings, like your preferred language view. You can clear them from your browser any time, though some lobby pages may ask you to sign in again once they're gone.
Your password and linked payment details sit behind your sign-in, and we don't publish the exact account-level security mechanics here. If a sign-in attempt looks off to you, use the support route instead of changing payment details on your own.
We hold account and transaction records as long as your account stays active, or longer where local law requires it. If you want a change made, or want to know how long a specific record stays on file, ask through our published support route.
These are the questions that come up most when someone on laki5 wants to understand what happens to their account and payment data. If your question isn't covered here, the support routes above take it from there.
We only pass the minimum transaction detail needed to confirm your entry with the payment partner involved, whether that's Nagad or your bank handling a Bank Transfer. We don't sell your wider account profile or history to outside advertisers at any point.
Open your account settings to see the core record we hold, or send a question through our support route if you want it confirmed in writing. We'll match it against your registered mobile number and account history before replying, usually through the same channel you used to ask.
Yes — raise it through our support route rather than editing sensitive fields yourself. We log the correction against your account history so your mobile number, name spelling or linked payment detail stays consistent across every record we hold for your laki5 account.
What we can store, share or let you request depends on your local law and eligible regions, so a few details of this policy may apply differently depending on where in Bangladesh you access laki5 from and what rules sit over your account.
Cookies keep you signed in across pages inside laki5 and remember a few display choices, like your language or table view. They don't track what you do once you've closed the tab or moved to a site outside our domain.
Use the chat icon in your signed-in laki5 account, or the support form on our help page — both routes send privacy or data questions straight to the team that handles account, cookie and payment-record requests, so you get one consistent answer tied to your laki5 account.