Casino / Live
asha771 keeps this policy short and direct — you should know exactly what information we hold about your account, how it moves, and what you can do about it. Access to our platform and its features depends on your local law and eligible regions.
When you open an account with us, we collect the details you provide during registration — your contact information, account credentials and the choices you make inside the platform. When you use a supported payment method such as bKash, Rocket or Upay to fund or withdraw from your account wallet, the transaction reference and amount are recorded against your account history. We do not store your full mobile wallet PIN or any credential that belongs to the payment provider; those remain on the provider's own system. We also collect device and session data — browser type, screen size, session timestamps — so we can keep your account working consistently whether you return on Android, a desktop browser or a different handset. This device continuity data helps us detect unusual access patterns that may signal unauthorised use. We retain account data for as long as your account is active and for a period after closure as required by the obligations that apply to our operation. Where local law governs what we may collect or retain, that law takes priority. Use of our platform and any data-dependent feature is subject to your local law and the eligible regions in which we operate.
This policy covers the information asha771 processes directly. It does not extend to third-party services you connect to through our platform, and it does not override the privacy terms of external payment providers. The four areas below define the boundary clearly.
Any information you submit when opening, verifying or updating your asha771 account falls inside this policy. That includes login credentials, contact details and the account preferences you set from your profile screen.
Wallet activity linked to your account — including references generated by bKash, Rocket or Upay transfers — is recorded on our side. The payment provider's own data handling is governed by their separate policy, not ours.
Session logs, page-view data and device identifiers collected while you browse the lobby or navigate account pages are within our scope. We use this to maintain device continuity and flag access anomalies against your account.
Links or embedded content from external providers — including game studios, payment gateways and any external verification services — operate under their own terms. We do not control or represent their data practices, and this policy does not bind them.
You are not a passive subject of this policy — there are concrete steps you can take at any point. If you want to see what we hold, you can send a data-access request through our support route and we will respond with the account-level records we store against your profile. Spotted an error in your contact details or information? Log into your account and head to the profile settings screen; most fields are editable directly. For items that cannot be changed from the front end — such as your registered mobile number used for bKash or Rocket wallet verification — raise a correction request with our support team and we will walk you through the identity check required. If you have a question about how a specific piece of data is used, or you want to request that we delete information no longer needed, the support contact below is the right starting point. We handle each request individually; eligibility for deletion may be limited where we hold data for reasons required by the obligations that apply to our operation.
Submit a data-access request via support. We will confirm the account-level information we hold against your registered profile — including session history and transaction references stored on our side.
Most profile fields are editable from your account settings screen. For wallet-linked details such as your registered mobile number, contact support and follow the identity verification steps shown there.
If any part of this policy is unclear for your situation — especially around how payment references or device data are stored — our support team can clarify without requiring you to close or alter your account.
You may request deletion of personal data we no longer need to retain. We will confirm which records are eligible and which must be kept under the obligations that apply, then action the rest promptly.
If this policy raises a question specific to your account or your data, the routes below connect you to the team that can help. Use the channel that works for your situation — all three are published on the asha771 site.
Open the chat widget from any page on the site. Describe your privacy question and a team member will pick it up. This is the quickest route for account-specific data queries.
For written data requests — access, correction or deletion — email our support address listed on the Contact page. Include your registered account email so we can locate your records.
The Help Centre on the site carries published articles on account management and data handling. Check there first for common questions about session data, wallet records and cookie settings.
Our approach to data is built around what you can verify in your own account, not around statements you have to take on faith.
We use session cookies to keep you logged in across page loads and to maintain device continuity when you return on the same handset or browser. You can manage cookie preferences through your browser settings; disabling them may affect account functionality.
Login activity is logged against your account. If we detect a session from an unfamiliar device or location, we may prompt additional verification before allowing access. You can review recent login events from the security section of your account settings.
We keep account data for as long as your account remains open and for a defined period after closure. Payment transaction references — including those from bKash and Rocket — are retained as part of your account history for the retention period that applies.
When this policy changes in a material way, we will post the updated version at this URL and note the revision date at the top of the page. Continued use of your account after a posted update means you have seen the revised terms.
The questions below address what real account holders ask about data, rights and contact when they read this policy for the first time.
We collect the contact details and credentials you enter during registration, plus device and session data generated as you use the platform. We do not collect payment credentials directly — those stay with bKash, Rocket or Upay on their own systems.
When a wallet transfer completes, the reference number and amount are recorded in your account transaction history on our side. The full wallet credentials and PIN remain with the payment provider. We cannot access or modify what is held on their system.
Yes. Submit a data-access request through live chat or the support email address on our Contact page. Include your registered account email. We will return the account-level records we hold against your profile.
Log in and go to account settings — most fields are editable from there. If the field is locked, such as a wallet-linked mobile number, raise a correction request with our support team and follow the identity verification steps they provide.
No. Studios like Joker, CQ9, Microgaming and JDB supply game content and operate under their own data terms. Our policy covers what asha771 collects through your account and session — not data processed inside a studio's own software environment.
We retain records for a defined period after account closure as required by the obligations that apply to our operation. After that period, records not subject to a legal hold are removed. Contact support to ask about the retention period that applies to your account.