Casino / Live
r88888 keeps this Privacy Policy centred on how your account, wallet activity and support history move through our systems, not on generic platform promises. Access to any personal data we hold depends on your local law and the eligible region you're signing in from.
This policy sets out how r88888 treats the information tied to your account once you sign in on mobile or desktop. We collect what's needed to keep your session running — login details, device identifiers, and the transaction records created when you move funds through bKash, Nagad or Rocket. None of this is sold or shared for marketing outside our own support and account-security purposes. Because Bangladesh players reach us from different regions and devices, the exact rules that apply to your data can shift depending on your local law and whether your region is eligible to hold an account with us; we don't assume one jurisdiction applies to everyone reading this page. Where a payment rail like Rocket or bKash writes a transaction entry to your account, that record sits alongside your login history so our support line has one place to check when you raise a question. We keep this policy written in plain terms rather than long legal paragraphs, and we update it when the data we handle changes, not on a fixed schedule we haven't published. If a term here feels unclear against your own region's rules, treat the local law as the final word, and reach out through the support routes listed further down this page.
Not every part of r88888 touches your personal data the same way, so this policy draws a line between what sits inside its scope and what doesn't. Signing in, moving money through a payment rail, reading a lobby page and using an outside service each carry a different data footprint. Below is how we split those four areas, written plainly rather than in dense legal phrasing, so you can tell at a glance which part of your activity this policy actually governs.
Covers how we log sign-ins across mobile and desktop, including device sessions created when you return to r88888 after a network drop. This part of the policy does not extend to game content, only the record that you accessed your account.
Covers wallet activity tied to bKash, Nagad and Rocket when those rails write a transaction to your account. We hold the record of the transfer, not the card or bank detail behind it, and it stays in your account history for support reference.
Covers the lobby pages, game listings and editorial text you browse on r88888 — browsing a slot page or a sportsbook category doesn't create a personal record the way submitting account or payment data does.
Covers services outside our direct control, such as the payment rail processing a bKash or Rocket transfer, or a game studio's own systems. Their handling of your data falls under their own policy, not this page.
You hold a few practical choices under this policy, and most of them start from inside your signed-in account rather than a separate request form. You can review the login and transaction history attached to your profile, check which device sessions are active, and flag anything that looks wrong through our support routes. If a name, contact detail or linked payment record needs correcting, raise it with support rather than editing it blind — account-security checks mean some fields need a verification step before a change is applied. You can also ask us directly what data point a particular record came from, such as a Rocket transfer entry or a login timestamp, and we'll point you to where that record sits. None of this depends on which device you're using; the same account, viewed on mobile or desktop, shows the same history.
Open your account's activity or transaction section to see login history and payment entries tied to bKash, Nagad or Rocket. It's the fastest way to check what we've logged without raising a separate request.
If a detail on your profile is wrong, tell support rather than guessing at a fix yourself — some fields are locked behind a verification step for account-security reasons before any change goes live.
You can ask what a login timestamp or a Rocket/bKash transaction entry refers to, and we'll explain where that record sits in your account history and why it was created.
Questions about how this policy applies to your region, or to a record you don't recognise, go through the same support routes listed on this page rather than a separate privacy desk.
A privacy question travels through the same support routes you'd already use for an account or payment query — we haven't built a separate desk for it. Below are the paths published on r88888 for reaching us, whether you're signed in on mobile between errands or sitting at a desktop later in the day. Mention clearly that your message concerns this policy so it reaches the right queue without extra back-and-forth.
Open the support page linked from the footer or your account menu to raise a privacy question the same way you'd raise an account or payment query.
Once signed in, the help section inside your account carries the same support route and keeps your question tied to your login, so we can check the right record without extra back-and-forth.
Use the contact form linked from the site when you'd rather describe the issue in writing — mention that it's a privacy question so it's routed to the right place.
How we handle data and how we keep your account secure are two sides of the same question, so this section covers both together. From the session marker that keeps you logged in, to the verification step guarding a changed detail, every piece here exists to protect the record attached to your account rather than to promise something we can't evidence. Retention and contact routes sit at the end, so you know how long a record stays and where to ask about it.
We keep account, device and transaction data in the systems needed to run your session and support your history, not spread across unrelated marketing tools outside r88888's own account flow.
Your device holds a session marker so returning to r88888 doesn't mean logging in from scratch every time; this is the same mechanic behind account continuity after a network drop on mobile.
Login and payment entries sit behind your account credentials, and a verification step applies before certain details, like a linked bKash or Rocket record, can be changed.
We hold account and transaction records for as long as your account stays open and support needs them; questions about a specific record go through the support routes above.
A handful of questions come up more than others once a player opens this page looking for specifics rather than general wording. The answers below stay tied to what you can actually check inside your account or through our published support routes, not to assumptions about speed or coverage we can't back.
No — a bKash or Rocket transaction creates a record inside your account history for support and account-security reference. We don't pass that record outside r88888's own systems for marketing purposes.
Yes. Open your account's activity section on mobile or desktop to see login sessions and payment entries tied to bKash, Nagad or Rocket, the same history our support team checks when you raise a question.
Your account history follows your login, not the device. Sign in on mobile browser or desktop and the same transaction and session records show up, since continuity sits with the account, not the screen.
Not necessarily — what applies to your data can depend on your local law and whether your region is eligible to hold an account with us. Treat your own region's rules as the final word over this page.
Raise it through the support page or in-account help section rather than editing it directly. Some fields, including anything linked to a payment record, carry a verification step before a change applies.
Use the support page linked from your account menu or the contact form on the site, and mention it's a privacy question so it reaches the right place without a separate desk.