Slots / Live
Signing in to eo11 leaves us holding a small, defined set of details about you — your account, your wallet activity, and the phone you use — and this policy says what happens to each one. Access still depends on your local law and on eligible regions, so confirm that before you go further.
We keep this page short on purpose. What we hold falls into three groups: the details you give us when you create an account, the records that bKash, Nagad or Rocket produce when you move money through your wallet, and the technical traces your phone leaves when it loads a lobby page. The first group keeps you signed in, the second lets us match a deposit or withdrawal to the right account, and the third keeps pages loading properly on a small screen. We do not sell your details, and we do not pass them to another company so it can market to you. Where a payment rail or a game studio sits between you and us, that provider sees only what it needs to complete its own step. Game titles arrive from studios and are shown in the lobby; the studio's own handling of data sits under its terms, not ours. Your rights under this policy depend on where you live, because data rules differ between countries and regions. We follow the law that applies to you locally, and if it gives you a right we have not listed here, tell us and we will work through it. Platform access is likewise limited to eligible regions, so availability is not identical for every reader. If something in this text is unclear, send your question through the published support route and we will answer it in writing.
Your account sign-in, your wallet history on bKash, Nagad or Rocket, and the way your phone loads a lobby all sit inside this policy. The moment you tap through to a payment wallet or any page we do not run, you are on someone else's terms, and we cannot answer for what they record. Game titles come to us from studios, so a slot such as Slot ThunderStrike or a crash round such as Crash Lightning plays out on their build while we show it to you inside our lobby. That split matters when you are trying to work out who to ask about a specific thing. We also treat an anonymous browse of a public page differently from a signed-in session. If you never log in, we hold far less. Once you do log in, the account record becomes the anchor for everything after it — including any question you raise later through our published support route.
Sign-in details, the email you registered with, and the session your phone keeps open between visits all sit under this policy. Keep the device locked when you step away, because an open session is an open account.
Every deposit or withdrawal you route through bKash, Nagad or Rocket leaves a record we store against your account, so your wallet balance and history stay consistent each time you come back to the lobby.
Titles from studios such as Pragmatic Play or Spadegaming are shown here, and this policy governs how we present them to you, not how a studio builds, hosts or runs the game itself.
Tap a payment wallet or a page we do not run and you leave our policy behind. Read that provider's own terms, since we have no control over what it records or how long it keeps anything.
When you want to know what we hold, start inside your own account rather than with a support message — your wallet history there is the fastest record you have. From that screen you can correct a detail, such as a phone number attached to your bKash or Nagad wallet, without waiting on anyone. If something looks wrong, or you want a copy of what sits against your account, raise it through the support route shown on the site and say clearly which record you mean. Questions about how long we keep something, or about access from an eligible region, are answered the same way. You do not need a special form to ask; a plain message that names your account and the detail in question is enough for us to work from.
Open your account area and look through the deposits and withdrawals you made with bKash, Nagad or Rocket. That history mirrors the record we keep, so anything missing or duplicated shows up for you at the same time it does for us.
If a phone number, email or wallet reference on your account is out of date, update it from the account area. Keeping those fields accurate is the simplest way to make sure a payment confirmation reaches the right person later.
Send your privacy question through the support route published on the site, name the record you mean, and we reply in writing. You do not have to explain your whole history for us to find the entry you are asking about.
Where your local law gives you a right to change, copy or delete something we hold, tell us which one you want. We follow the rules that apply where you live and confirm back what has been done.
Privacy questions reach us through the same support route you already use for account and wallet matters — one path rather than a separate privacy desk, so you never have to guess where to write. Say what you need in plain words: the account you are writing about, the record or page involved, and the outcome you want. If your question concerns a bKash, Nagad or Rocket entry, quote the reference that shows in your wallet history so we can match it without asking twice. We answer in writing, and we will not ask you for your password in a message. Anything that turns on your local law, or on whether your region is eligible, gets explained in that reply rather than promised in advance. For a simple field change, the account area usually settles it faster than a message does.
The support route published on the site is the single place to raise anything about this policy. Include the account email and the detail you are asking about, and we come back to you in writing.
Most small corrections, such as a phone number or an email tied to your wallet, you can make yourself inside the signed-in account area, without opening a support message at all.
For a question about a bKash, Nagad or Rocket entry, quote the reference from your own transaction history. That gives both sides the same record to work from and shortens the exchange.
Your phone keeps a session open after you sign in, so the lobby loads without a fresh password on every visit. That convenience has a limit: if you hand the device to someone else, sign out first, because an open session is an open account. Cookies do the smaller jobs — remembering that you are signed in, holding a page steady while it loads, and showing us which screen a problem came from when something breaks. You can clear them from your browser settings whenever you like, though you will be asked to sign in again afterwards. We keep records only as long as the purpose they were collected for needs them: an active account record lasts while the account is open, and payment records are held so that a wallet query can still be answered afterwards. Nothing beyond that is kept without a reason, and nothing is shared for another company's marketing.
Sign-in details, wallet activity with bKash, Nagad or Rocket, and basic device details from the browser you use. That is the working set, and every part of it is tied to running your account rather than to anything else.
Cookies keep you signed in and help pages load correctly on a phone screen. Clear them whenever you like from your browser settings; the only cost is signing in again on your next visit to the lobby.
Use a password you do not reuse elsewhere, sign out on a shared phone, and glance at your wallet history now and then. If a session looks unfamiliar, raise it through the support route and we look at the record with you.
We hold an account record while the account stays open, and keep payment records long enough to answer a wallet query later. To ask about anything we hold, use the published support route and name the record you mean.
These are the privacy questions that come up most often from people using the lobby on a phone. If yours is not here, send it through the published support route and we will answer it directly.
It sets out what eo11 records when you sign in, move money through bKash, Nagad or Rocket, or load a lobby page on your phone, and what you can ask us to change. Pages we do not run sit outside it.
We do not sell your details and we do not hand them to another company for its marketing. A payment wallet or a studio receives only what it needs to complete its own step, and nothing beyond that.
Sign in and open your account area, where your wallet history mirrors the record we keep. If you want something that is not shown there, ask through the support route published on the site and name the record you mean.
Usually yes, and what you can do depends on your local law. Simple fields such as a phone number or email you can correct yourself in the account area; for anything else, send the request and we confirm what has changed.
Yes, and they do the practical jobs: keeping you signed in, holding a page steady while it loads, and showing us where a problem started. You can clear them in your browser settings at any time, then sign in again.
Use the support route published on the site, the same one you use for account and wallet matters. Include the account email and the record you are asking about, and expect an answer in writing rather than a call.