apk488 Privacy Policy: Your Data, Explained Plainly
apk488 keeps its privacy terms on a single page: what we collect when you register, how the transaction records behind your bKash and Nagad transfers are stored, and the cookie settings that keep you signed in. Read the sections below, then use your account or our support page if you want a detail changed — what we can offer you depends on your local law and the regions we are able to serve.
Account details
Wallet records
Cookie settings
Device and browser data
LOCAL LAW FIRST
How We Handle Personal Data at apk488
Privacy at apk488 starts with a simple posture: we collect what your account needs, and we say why. When you register, we hold the details you enter — your name, your contact number and the wallet number you link. When you move money, the record shows the bKash or Nagad transfer you approved, the amount and the time it was posted, because that trail is what you and we both rely on if a payment ever needs tracing. We also keep basic device and browser data: the phone you signed in from, the pages you opened and the session cookie that keeps you logged in between visits. How much of this we may hold, and for how long, depends on where you are. Data rules differ by country, so access to our services and the way we handle personal details follow the law that applies to you and the regions we are able to serve. If local law does not permit a feature, we do not offer it there. Where the law requires a record to be kept longer, we keep it longer. We do not pass your details to another company for its own marketing, and any provider that helps us run the platform handles them on our instructions only. When this page changes, the updated wording is what applies, so check back before you rely on an older copy.
bKash
Nagad
Rocket
Upay
Bank Transfer
INSIDE THE SCOPE
What This Policy Covers and What It Leaves Out
Two sides of the same account. This policy covers the details you hand over when you register, the sign-in session that keeps you inside your account, the wallet records created when you move money through bKash or Nagad, and the basic device and page data we gather while you browse the lobby. It applies wherever you reach us from, as far as the law where you are allows. What falls outside matters just as much. Payment providers such as bKash or Nagad run their own systems, and what they do with a transfer you start is described in their terms, not ours. Pages you reach from a link in the lobby belong to whoever runs them. Games supplied to our lobby carry their own rules on play and outcomes, which sit apart from how we treat personal details. Know which notice you are reading at each step, and write to us if a boundary is not clear.
Your account and sign-in
This policy covers the details you give us at registration — your name, contact number and linked wallet number — plus the sign-in session that keeps you inside your account. If you share a phone with someone else, remember that an open session lets them see the same wallet and lobby pages you can.
Deposits, withdrawals and wallet records
Every bKash or Nagad transfer you make through the account wallet creates a record we hold: the amount, the time and the reference you can match against your own wallet history. That record sits inside this policy. What your payment provider does with the same transaction is governed by that provider's own terms.
Lobby and game activity
Pages you open inside the lobby sit inside this policy too — the sportsbook markets you browse, the live tables you join and slot pages such as Dhaka Hot Slots. We use that activity to keep the account working and to understand which sections get used, not to build a profile we sell on.
Pages run by other companies
Some links in the lobby lead to services we do not run, and this policy ends at the edge of our own pages. Once you leave for a third-party site, that company's privacy terms apply to whatever you do there. Read their notice before you share anything with them.
YOUR CHOICES
Choices You Can Act On From Your Account
Your account gives you the first line of control over your own details. Open your wallet history and you can see the deposits and withdrawals we hold a record of, each one matching the bKash or Nagad transfer you made. If a contact number or a spelling is wrong, tell us and we will set it right; keeping those details accurate is what lets us reach you about your account. You can also ask what we hold, ask for a copy, or ask us to delete details that the law does not require us to keep — we will explain what can and cannot be removed in your case. If you would rather not receive account messages by email, you can switch them off without losing access to the wallet and the lobby. Where you are, and the regions we serve, decide how far each of those choices goes, so check your local law if you are unsure.
Check your transaction history
Sign in, open the wallet area and your payment records are listed in order: what arrived, what left, the time it was logged and the reference number. That same reference is what you quote when you raise a question about a bKash or Nagad transfer, so save it before you write in.
Correct your account details
Names get mistyped and numbers change. If something in your profile is out of date, open the account details area and follow the fields shown there; if a field is locked, our support page is where you ask for the change and explain what needs correcting.
Ask what we hold
You can ask us for a summary of the personal details tied to your account and how we use them. Send that request through the support route on this site, and we will answer it using the contact details already on your profile rather than an address you have not confirmed.
Turn off account emails
Account messages keep you posted on your wallet, your sign-in and any change to this policy. If you would rather not get them by email, switch them off from your account settings without losing access to the wallet or the lobby; messages about a payment you have made may still arrive.
REACHING OUR DESK
Where to Raise a Privacy Question
Privacy questions rarely arrive at a convenient time, so we keep the route plain: one place to send them, and people who read them. Start from the support page published on this site. Say which part of the account you are asking about — a bKash transfer you cannot match, a name spelt wrongly, a request to see what we hold — and include the contact details we should reply to. If you are already signed in, opening the request from your own account saves a step, because your profile details are attached to it. We answer using the phone number and email address recorded on your profile. That is deliberate: it keeps a discussion about your account attached to your account. If those details are out of date, correct them first, then send the question. Where you live and the regions we serve can affect what we are able to do, so say so if your question depends on local law. We will tell you plainly what we can and cannot action.
Support page on this site
Our support page is the main route for anything privacy-related: a wallet record you want explained, a detail you need corrected, or a request to see what we hold. Open a ticket there and name the account or the transfer you are asking about so we can find it quickly.
Requests from inside the account
Already signed in? Start from your own account pages. The email and phone number on your profile are the contact points we use to reply, so keep them current before you send a question through the support route on this site, because a message from inside the account carries its own context.
Written contact we publish
The email address we answer privacy questions from is the one listed on the support page of this site. Use it when you want your request on record, and quote your account reference so we can match it to your profile.
DATA AND ACCESS
Our Practice on Data, Cookies and Access
How we treat what you hand over. Registration details, wallet records and the device data behind your sessions exist so the account can run: signing you in, showing what moved, answering your questions and meeting the record-keeping rules that apply where you are. Inside our own team, access is limited to the people whose work needs it. Cookies are part of that picture. They hold your sign-in, remember your language and tell us when a page loads slowly on a phone. You can clear or block them from your browser, and some conveniences will change if you do. On security, your side matters: use a password you do not reuse elsewhere and sign out on a shared handset. Retention follows the law that applies to you. We keep account and payment records while the account is open and for the period local rules require afterwards, which is why closing an account does not always remove everything. If you want a change made to your details, send it through support and we will confirm what can be done.
How data is handled
Details you give us are used to run your account: to sign you in, to show your wallet records, to answer your questions and to meet the record-keeping rules that apply where you are. Access inside our own team is limited to the people who need it to do that work.
Cookies on this site
Cookies do unglamorous work here. They hold your sign-in so you are not typing a password on every page, they keep your language setting, and they let us see which pages load slowly on a phone. You can clear or block them in your browser, though parts of the account may then behave differently.
Keeping your account secure
Your sign-in details are yours to protect: use a password you do not reuse elsewhere and log out on a shared phone. If your wallet shows activity you do not recognise, change the password from account settings first, then write in through the support page.
How long records stay
We keep account and transaction records while your account is open and for the period local rules require afterwards. When you close an account, some records tied to payments may remain, because the rules around financial records do not switch off with the login. Ask through support if you want to know what still applies to you.
POLICY QUESTIONS
Privacy Questions You Might Ask Us
Most of the questions we get about this policy are practical ones: what we hold, how long it stays, who sees it and how to get something changed. The answers below cover those, and they follow what actually happens when you use your account — signing in, moving money through the wallet with bKash or Nagad, browsing the lobby and writing to support. If your situation differs, because of where you live or how you use the account, send the question through the support page and we will answer it against your own records rather than a general rule. Where local law limits what we can do, the reply will say so plainly. Read the sections above for the full wording; what follows is the practical side of the same policy.
What details does apk488 collect when I open an account?
What you enter at registration — your name, contact number and the wallet number you link to the account — plus the sign-in session that keeps you logged in. As you use the lobby, we add basic device and page data, and every bKash or Nagad transfer you make leaves a transaction record.
Can I see the payment records you hold for my wallet?
Yes. Sign in and open the wallet area of your account; deposits and withdrawals are listed with the amount, the time and a reference number. Compare that list with the bKash or Nagad statement on your own phone — if two entries do not match, raise it through support and quote the reference.
How do I ask apk488 to change or delete my details?
Send the request through the support page and say which detail needs changing. We use the contact details already on your profile to confirm it is you. Not everything can be removed — records tied to payments may have to stay under the rules that apply where you are.
What happens if I block cookies in my browser?
Blocking or clearing cookies is your choice, and the browser will do it. Expect some change: you may be asked to sign in again on each visit and your saved language may reset. The wallet and the lobby still work, but conveniences that depend on cookies will not follow you between sessions.
Who inside your team can see my account details?
Only the people whose work needs them — the ones answering support requests, checking payments and keeping the platform running. We do not pass your details to another company for its own marketing, and providers that help us operate the site handle them on our instructions.
How do I raise a privacy question with your team?
Use the support route published on this site. Tell us what you want to know, which part of the account it concerns and the contact details we should reply to. A written request is easier for us to track, and we answer using the number and email already on your profile.
Sports / App