Casino / Live
a6888 keeps your profile, wallet history and lobby activity tied to one email login, and this page sets out what we collect, why we hold it and how you ask us to correct or remove it. Using the account depends on your local law and the regions we can serve, so read this together with the terms shown at sign-in.
Privacy on a6888 follows the way our lobby actually works. You sign in with an email address, you fund your account wallet, and each step leaves a record you can ask about later. We hold the details that keep that flow running: your email, your saved account settings, transfer references from bKash, Upay or Bank Transfer, and basic device data such as the browser you opened. We do not sell your details to other businesses, and we do not pass them on for anyone else's marketing. How much we keep, and how long we keep it, depends on the law that applies where you live and on the regions we can serve. Some places allow an online account, others do not, which is why eligibility is checked at sign-in. Where local rules require transaction records to be held for a set period, we hold them. Where those rules call for deletion or anonymisation instead, that is what we do. Two points stay constant. We ask only for what the account flow needs, nothing extra to open a wallet or send a request. And you can use a published support route to ask what we hold, correct a detail, or request deletion where the law allows it. The service itself, and any payment route such as bKash, Upay or Bank Transfer, remains subject to your local law and eligible regions.
This policy covers what happens on a6888 while you browse the lobby and after you sign in with your email: your account profile, your wallet balance and transfer history, the games and tables you open, and the cookies that keep a session alive. It does not cover what another company does with data it collects on its own. The moment you leave us for a wallet app, a bank page or any linked outside site, that company's own privacy terms apply instead of ours. Everything inside the account shares one record. A cricket market or a table such as Teen Patti Rollout sits in the same profile as your transfer history, so a question about one entry can be traced against the same login. Where this page and the terms you accept at sign-in touch the same ground, the terms shown at sign-in decide that point. Nothing here widens what we collect or shortens what the applicable law protects.
Signing in with your email, the fields you save and the preferences attached to your login sit inside this policy. So does the security of that login, which is why we remind you to keep the password private and sign out on a shared phone.
Every transfer you make through bKash, Upay or Bank Transfer, and every movement in your account wallet, is recorded against your login. Open that history yourself, and send us a question if an entry does not match what you see in your own app.
Slot rooms, live tables and sports categories you open while signed in form part of your account activity, and session cookies make that browsing possible. Clear cookies in your browser and you will be signed out of the lobby.
Wallet apps, bank pages and sites you reach through a link belong to other companies. Their privacy terms apply to what they collect, and asking us about their data handling will not get you a useful answer.
You are not stuck waiting on us to see what we hold. The account area is the first stop: sign in with your email, open your profile and check the fields we keep, from your contact address to the wallet history tied to your transfers. If something reads wrong, fix it there yourself. For anything you cannot edit, send the request through a published support route and say plainly which detail is wrong and what it should say instead. Asking a question counts as a valid step too. You can request a copy of the account data linked to your login, ask how a particular entry was created, or ask us to close the account and remove whatever the applicable law lets us remove. We answer through the same route you wrote in, following the process the rules for your region set out, so treat the reply you receive as the confirmation rather than assuming an outcome on your own.
Sign in with your email and open the account area to see the fields we hold: contact address, saved preferences and the wallet history tied to your transfers. Reading it costs nothing and needs no request, so start there before you message us.
Most profile fields are yours to edit. Update the value, save it, and the change appears on the account straight away. If a field refuses to save, write down what you tried and send it to us through a published support route.
If a transfer made through bKash, Upay or Bank Transfer looks wrong, quote the reference from your own app along with the date. We check it against the record attached to your login and reply on the same route.
You can ask for the account data linked to your login, or ask us to close the account and delete what the applicable law lets us remove. Send it in plain words through the published support route.
Privacy requests reach us fastest when they arrive through one of the routes we publish on this site. Use the support link shown on our pages, the form in the footer, or the help section inside your signed-in account, and put the request in plain words. State the email address on your account, describe the entry or field you are asking about, and add the date you noticed it. That is usually enough for us to locate the record and reply without going back and forth. Two habits keep a request clean. Send it from the email address tied to the account where you can, and never type your wallet PIN or password into a message. If your question is about a payment made through bKash, Upay or Bank Transfer, include the reference shown in your own app so we can match it to the right entry. We answer through the same route you used.
Policy questions go through the support link published on our pages. Tell us the email address on your account and the exact entry you are asking about. That single route keeps your request with the people who can read your account record.
The footer form takes the same kind of request when you are signed out or cannot reach the lobby. Write your question plainly, mention the date you noticed the issue, and never send wallet PINs or passwords through any form.
Once you are signed in, the help section inside your account shows the routes we publish for policy and wallet questions. Start there if you want to check what you agreed to before you send anything to us.
Looking after this policy area comes down to a few steady habits rather than a slogan. We keep account data inside the systems that run the lobby and the wallet, limit who can read it, and tie every lookup to the login it belongs to. Cookies do the session work you can see for yourself in your browser: keeping you signed in and remembering the view you left. We do not use them to follow you around other sites for advertising. Retention follows the rules that apply to your region. Where a period is set for account and transfer records, we hold them for that period; where deletion or anonymisation is the requirement, we do it instead. You can ask about any part of this. Start in the help section of your account, or use the support route in the footer, and tell us what you want changed. Questions about a stored field, a cookie or a transfer entry all travel the same path, and the reply comes back from the same place you wrote in.
Your email login, saved account preferences, wallet activity and any request you send us are stored so the account can run and so we can answer you. We ask for the minimum the flow needs, nothing more.
Session cookies keep you signed in while you move between slot rooms and live tables, and remember the lobby view you left. Clearing them in your browser signs you out and resets those saved views until you sign in again.
Keep your password to yourself, sign out on shared phones, and use the account page to update your details when they change. If you think someone else has your login, contact us through a published support route straight away.
We keep account and transfer records for as long as the rules that apply to your region require, then remove or anonymise them. To ask for a copy, a correction or deletion, use our published support route.
The questions below are the ones we get most often about this policy, and they stay close to what you can check yourself. You will find where your profile data sits, how cookies behave on a mobile browser, what happens to your transfer history when you close an account, and which route to use when you want a copy of what we hold. Each answer points back to a page you can open rather than asking you to take our word for it. Where a local rule changes the outcome for your region, we say so instead of pretending one answer fits every country. If your situation is not covered here, send the question through a published support route and we will answer it against your own account record.
Your email login, the preferences you save, your wallet balance and transfer history, and the games or tables you have opened while signed in. We also keep basic device data such as the browser you used and the session cookies that hold your sign-in. Anything you send us through a support route stays on the same record.
No. We hold your data to run the account, handle transfers made through bKash, Upay or Bank Transfer, and answer your requests. We do not sell it, and we do not pass it to unrelated businesses for their own marketing. Outside services you visit yourself fall under their own privacy terms.
Send the request through a published support route, using the email address on the account where you can. Say clearly that you want a copy of the account data tied to that login. We reply through the same route, and what we can release depends on the law that applies in your region.
Yes, you can ask. We close the account and remove or anonymise what the applicable law allows us to remove. Some records, such as transfer entries connected to payments, may need to be held for a period that local rules decide, so ask us and we will confirm what applies.
Cookies keep you signed in while you move between slot rooms and live tables, and remember the last lobby view you opened. If you block or clear them in your browser settings, you will be signed out and those saved views reset. Signing in again restores the session.
The transfer itself is handled by the provider you choose. bKash, Upay or Bank Transfer each run under their own terms, and we receive the reference needed to credit your account wallet. Which of those routes you can use depends on your local law and eligible regions.