Live / App
bet5 collects only the account and transaction data needed to run your sessions — nothing more. This policy sets out what we hold, why we hold it, and the steps available to you when you want to review or update your records. Access to this platform and its services depends on your local law and eligible regions.
When you open an account with us, we collect the details you submit during registration: your name, contact address, and the credentials you choose. When you fund your account or request a withdrawal through bKash, Nagad, or Upay, we record the transaction reference, amount, and wallet identifier linked to that payment — not your full wallet credentials. We also collect session data: the device type, browser version, and pages visited during a logged-in session. This helps us keep your account secure and spot unusual access patterns early. We do not sell your personal data to third parties. We do not share your wallet details — whether bKash, Nagad, or Upay — with any party outside the payment processing chain. Data we collect is kept only as long as your account remains active or as required to resolve a dispute or comply with a valid legal request. Jurisdiction applies: the way we store and process data may depend on the laws of your eligible region. If you have questions about what we hold for your specific account, the contact routes in the Support section of this policy are the right place to start.
Transaction references linked to bKash deposits and withdrawals are recorded against your account. We hold only the reference and amount — not your bKash PIN or login credentials.
Nagad wallet transfers are logged by reference number and value. Your Nagad account password is never stored or visible to our team at any point in the process.
Upay transactions follow the same pattern — reference and value only. If a payment query arises, support can locate the record by transaction reference without accessing your Upay credentials.
Not every interaction with bet5 falls under exactly the same data rules. This section draws a clear boundary so you know what this policy covers directly, what sits in a separate terms document, and where a third-party service has its own policy you should read independently. Understanding the scope helps you direct any question to the right place.
Login activity, session tokens, and device data recorded when you sign in are all covered by this policy. We use this data solely to verify your identity and maintain session security across your registered devices.
Wallet activity through bKash, Nagad, and Upay falls within this policy's data-handling rules for the reference data we hold. The payment processors themselves operate under their own separate privacy terms.
Your browsing activity within the bet5 lobby — game categories opened, pages visited — is logged as session data under this policy. This data informs site performance; it is not shared externally for advertising purposes.
Links to external pages or services connected to bet5 are governed by those providers' own privacy policies. Once you leave our domain, this policy no longer applies and we have no control over how that third party handles your data.
Your account record is yours to review. If you want to see the personal data we hold — your registered name, contact details, or the transaction references tied to your bKash, Nagad, or Upay activity — you can raise a data-access request through our support contact route. We will confirm what we hold and provide it in a readable format. If any detail is incorrect — a misspelled name, a wrong contact address — you can ask us to correct it. Raise the correction via the same support channel and include your account reference so we can locate the record quickly. Account deletion requests are also handled through support. We will confirm what data is retained after closure, since some records may need to be kept for a defined period to satisfy a legal obligation in your eligible region. None of these rights require you to justify your request — simply contact us and we will walk through the available steps with you.
Request a copy of the data we hold for your account. Include your registered contact detail and account ID when you write to us so we can match the request accurately.
If a name, address, or contact detail on file is wrong, submit a correction request through support. We aim to update confirmed corrections promptly.
Not sure what data we collect or how a specific transaction record is used? Send the question through our support route and we will give you a direct, specific answer.
You may ask us to close and remove your account. We will confirm which records are deleted immediately and which must be retained under applicable legal obligations in your region.
If you have a question about how bet5 handles your data, or if you want to exercise any right described in this policy, the routes below are the ones we actively monitor for privacy-related queries. Please include your account reference whenever you write so we can locate your record without delay. Availability of support may depend on your eligible region.
Open the chat widget on the bet5 site while logged in to your account. State that your query is a privacy matter and include your account reference so the support team can pull up your record immediately.
Send your privacy request to the email address published in the Contact section of the bet5 site. Write the subject line as 'Privacy Request' and include your registered contact detail and account ID.
The Help section inside your logged-in account area links to the published policy routes. From there you can submit a data or correction request using the form provided, which routes directly to the privacy team.
Data security at bet5 rests on a few concrete practices rather than vague promises. Sessions are protected by encrypted connections, and your login credentials are stored in hashed form — your actual password is not held in readable text anywhere in our system. Transaction references from bKash, Nagad, and Upay are stored in isolated records that support staff can query by reference ID without exposing your wallet credentials. Cookie data collected during your lobby session is used for session continuity and site performance measurement; you can manage cookie preferences through your browser settings at any time. Data is retained for as long as your account is active plus any period required by applicable legal obligations in your eligible region. If you believe any aspect of our data handling falls short of what this policy describes, the privacy contact routes in the Support section are the correct escalation path.
Every logged-in session on bet5 runs over an encrypted connection. This applies to account pages, wallet actions, and lobby browsing — your data is not transmitted in plain text at any point during an active session.
Your account password is stored as a hash, not as readable text. Our support team cannot see or retrieve your password; they can only assist with a reset through the published account-recovery route.
Cookies used on bet5 cover session continuity and performance measurement. They do not track your activity outside our domain. You can adjust cookie settings through your mobile or desktop browser at any time.
Account data is held while your account is active. After closure, we retain only what is required under applicable law in your eligible region. Once the retention period lapses, the data is removed from active systems.
The questions below reflect what account holders in Bangladesh commonly ask about how bet5 handles their personal data, wallet transaction records, and the steps available under this policy.
We collect the name, contact detail, and credentials you submit at registration. Once you make a deposit, we also record the transaction reference and wallet type — bKash, Nagad, or Upay — but not your wallet password or PIN at any stage.
Yes. Submit a data-access request through live chat or the email route published on the site. Include your account reference in the message. We will confirm what records we hold and share them in a readable format.
We do not sell your data. Payment references are shared only within the processing chain needed to complete your bKash, Nagad, or Upay transaction. We do not share your data with external advertising networks or unrelated third parties.
Once an account is closed, we delete active records. Some data — such as transaction references — may be retained for a period required by applicable legal obligations in your eligible region. We will tell you exactly what is retained when you submit a closure request.
Contact support through live chat or email with your account reference and the correct detail you want updated. Once we verify the request against your account, we update the record. The correction route is the same regardless of whether the error is in your name, contact address, or other profile field.
This policy covers the data we hold on our side — transaction references and wallet type. The bKash, Nagad, and Upay platforms each operate under their own privacy terms. Once a payment moves to their system, their policy governs how they handle it.