Sports / Casino
This page sets out in plain terms what ae880 records when you open an account, add funds by bKash, Nagad, Rocket or Bank Transfer, and settle into the lobby on your phone. It also shows how to ask us for a copy of your records, a correction, or a removal where local law and eligible regions allow it.
We keep this policy plain because you should be able to read it in one sitting on your phone. When you create an account, our records hold what you type in yourself: your mobile number, the name you register with, and the payout route you pick from the wallet list. Payment context sits beside that. If you add funds with bKash, Nagad, Rocket or a Bank Transfer, we keep the reference that the wallet or bank returns so a later query can be traced to the right entry. We do not ask for details the account flow does not need. Where you are matters. Data handling rules depend on local law and eligible regions, so the protections described here apply only where the service is lawfully available to you. If a rule in your area gives you a stronger right than this page describes, that rule wins and we follow it. We also keep the record set small. Lobby activity, session timestamps and device type help us spot unusual sign-ins and keep your account wallet from being opened by someone else. We do not sell those records, and we do not hand them to advertisers to build profiles about you outside our own site.
A policy is only useful if you know where its edges are. This one follows your account across the lobby: sign-in, wallet activity, the tables you open and the support messages you send us. It also covers the small files our site sets on your browser so a session stays signed in, and the technical log we keep when a page fails to load. What it does not reach is anything you do on a site we do not run. Studios listed in the lobby, wallet apps on your phone and bank portals each publish their own terms, and their handling of your data is theirs to answer for. Read those pages when a payment leaves our site and lands in bKash, Nagad, Rocket or your bank account. If you follow a link out of our lobby, this policy stays behind with us. Inside the account area, the same rules apply whether you sign in on a phone or a larger screen.
Sign-in details, the mobile number registered to you and the session record created each time you open the lobby. This is the part of the policy you meet first, because nothing else works without it. Corrections to these fields run through your account area or a support message.
Deposits and withdrawals that pass through bKash, Nagad, Rocket or Bank Transfer, together with the reference each provider returns. The record exists so a payment can be matched to the right account if a query comes up later. It is not shared with advertisers.
Lobby pages, tables and game tiles you open, plus the cookies that keep a session signed in. This covers what happens on our own pages only. Clear your browser cookies and most of it resets, though you will sign in again on the next visit.
Studios whose titles sit in our lobby, the wallet apps on your phone and your bank each run their own privacy terms. Their handling of your data is theirs to answer for. Once a payment leaves our site, read the provider's page before you finish the transfer.
You are not stuck with what we hold. Open your account area and you can see the profile details we keep, the mobile number attached to the wallet and the payment references logged against each deposit. If something is wrong — a misspelt name, an old number, a wallet entry you no longer use — correct it there, or write to us and we will walk the change through with you. When you want a copy of your records, ask through the support route published on our site and tell us which account the request relates to. We may need to confirm the account is yours before we hand anything over; that check protects you as much as it protects us. Deletion requests are handled the same way, and we will tell you plainly if a record has to stay because a payment dispute or a legal duty holds it in place. Access rights depend on local law and eligible regions, so what we can action depends on where you are.
Open the account area and the profile block shows what we hold: your registered mobile number, the name on the account and the payout route you selected. Payment entries sit in the wallet history beside it. If a line does not match what you remember, keep the date and raise it with support.
Most fields you can change yourself in the account area, including the display name. Anything tied to a completed payment may need a support message so the wallet records stay consistent. Tell us the field, the current entry and the new one, and we will confirm when the change is made.
If you want to know why a particular record exists, ask. Send the question through the published support route with your registered mobile number and the date the entry was created. We will explain what it is for and whether it can be dropped under the rules that apply where you are.
Where a record is no longer needed, you can ask us to drop it. Some entries are held back by a payment dispute or a legal duty, and we will say so plainly rather than leave you guessing. Access rights depend on local law and eligible regions.
Questions about your data should not disappear into a void. We keep the routes below live on our site, and each one lands with a team that can act on a privacy request rather than pass it along unseen. Start from the account area when the question is about your own profile, because whoever reads it sees the same screen you do and can confirm a correction on the spot. For anything wider — a copy of your records, a question about how long a wallet reference is kept, a complaint about a message you received — use the support contact published on our site and include your registered mobile number so the request reaches the right account. We do not publish a separate private address for data requests. The published route is the one that gets logged, and the one we can follow up on. If a payment is involved, add the date and the amount shown in your wallet history.
The quickest place for a question about your own profile. The team reading it sees the same account screen you do, so a name correction or a mismatched wallet entry can be confirmed there. Include the exact field and what it should say.
For data copies, retention questions or a concern about a message you received, use the support contact shown on our site. Add your registered mobile number and the date of the payment or session you are asking about so we can locate the record.
Every privacy request that arrives through the published route is logged, so you can refer back to it if the thread needs picking up again. Quote the date you sent it and the mobile number on the account whenever you follow up.
Records only earn their keep if they are looked after. Our account wallet data sits behind a sign-in you control, and we ask you to keep that password to yourself rather than sharing it over a chat app. Cookies do a narrow job here: they hold a session open while you move between lobby pages, and they remember a language or display choice so you are not resetting it every visit. You can clear them in your browser at any time, though a cleared cookie usually means signing in again. We keep transaction references long enough to answer a dispute about a bKash, Nagad, Rocket or Bank Transfer payment, and routine session logs are dropped once they no longer help us spot a bad sign-in. Nothing in that process requires us to know more about you than the account flow already collects. If you want to know which of these records apply to your own account, ask us and we will set it out.
Account profile data, wallet references from bKash, Nagad, Rocket and Bank Transfer, and the session logs that help us flag an unusual sign-in. We keep the set narrow on purpose, and we do not pass any of it to advertisers to build profiles about you elsewhere.
A cookie holds your session open while you move between lobby pages and remembers a display choice so you are not resetting it each visit. Clearing them in your browser settings signs you out, which is expected. Nothing in the lobby breaks permanently because of it.
Your password belongs to you alone. We will not ask for it in a chat message, and you should not pass it to anyone who says they can move a payment along for you. If a sign-in looks unfamiliar, change the password from the account area and raise it with support the same day.
Transaction references stay while a dispute about a payment could still be raised. Routine session logs are dropped once they no longer help us spot a bad sign-in. To ask about a specific record, send the date and the mobile number on the account to our published support route.
Most of what reaches us is about the same handful of points: what we store, how long it stays, and who gets to see it. The answers below take each one in turn and point you to the route that settles it. Where a request depends on your local law and eligible regions, we say so rather than pretend the answer is the same everywhere.
We record what you enter yourself: your mobile number, the name on the account and the wallet or bank route you choose. Payment references from bKash, Nagad, Rocket or Bank Transfer sit with the transaction so a query can be traced. Device type helps us flag a sign-in that does not match your usual pattern.
Yes. When a deposit or withdrawal passes through bKash, Nagad, Rocket or a Bank Transfer, the reference that comes back is stored against your account wallet. That is how we match a payment to you if something goes wrong. It stays only as long as a dispute or a legal duty requires.
Use the support contact published on our site and say clearly that you want a copy of your account records. Include the mobile number registered to your account so we can find it. We may confirm the account is yours first. What we can release depends on local law and eligible regions.
Open your account area and edit the profile fields shown there. If a field is locked because a payment was made under it, message support with the correction and we will walk it through. Changing the number attached to your wallet may need a fresh verification step in the account flow.
No. Studios whose titles appear in our lobby and the wallet apps on your phone publish their own privacy terms. Once a payment leaves our site for bKash, Nagad, Rocket or your bank, that provider's handling of your data is theirs. Our policy follows your account inside ae880, not beyond it.
Send it through the support route published on our site, with your registered mobile number and a short note on what happened. We log the message and reply on the same route. If your local law gives you a further step, such as contacting a regulator, that route stays open to you.