App / Mobile
777aya handles your information with care, and this page sets out exactly what data we collect, how we use it, and what choices you have. Access to our platform and the rights described here depend on your local law and eligible regions.
When you register an account or make a deposit, we collect the details you provide — name, contact information, and the payment method you choose. For local payments like bKash and Bank Transfer, we record transaction references to match deposits to your account wallet and to handle any queries you raise with our support team. We do not store your bKash PIN or Bank Transfer credentials; those remain between you and your payment provider. Beyond registration fields, we collect device and session data — browser type, IP address range, and navigation timestamps — to keep your account secure and to understand how our lobby is used. This helps us show you the sections you visit most and flag unusual access patterns. We may share limited data with payment processors and identity verification services where account activity requires it, but we do not sell personal data to third parties for marketing. Our cookie policy is separate and accessible from your account settings page. All data handling is subject to the laws and regulations applicable in your jurisdiction; availability of this service depends on local law and eligible regions. If you have questions about a specific data point we hold, the support contact routes listed on this page are the right starting place.
Not every interaction with 777aya falls under this policy in the same way. Understanding the boundaries helps you know where to direct a question — whether that is to us, to your payment provider, or to a third-party service you reached through our platform.
Login activity, device fingerprints and session logs tied to your registered account are fully within this policy. You can request a summary of this data through the support routes we publish.
When you use bKash or Bank Transfer, we hold the transaction reference and amount for account reconciliation. The full transaction record sits with your payment provider, not solely with us.
Game results, RTP figures and studio content are governed by the game providers — Spadegaming, Habanero, CQ9, Microgaming and Bigtime Gaming — rather than this privacy policy. We display only what those providers expose.
Links to external sites, payment gateways or identity verification tools operate under those services' own policies. We are not responsible for data practices outside the 777aya platform boundary.
You are not a passive holder of an account — this policy gives you real steps you can act on. Start by reviewing the data tied to your account: your registered contact details, your linked payment methods (bKash or Bank Transfer), and your session history are all visible or request-able through your signed-in account area. If any detail is wrong — a misspelled name, an outdated contact number — you can submit a correction request directly through our support channel, and we will update the record once we verify your identity. Where you believe we hold data we should not, you can raise a formal data query; we will review it and respond through the same channel you used to contact us. None of these routes require you to close your account first. Eligibility for specific data rights depends on local law and the region from which you access the platform.
Open your signed-in account page to see your registered details and linked payment methods. For a full session or transaction log, submit a request via our support route and we will provide what we hold.
If your registered name or contact information is inaccurate, contact support with the correct details and your account reference. We verify and update the record after identity confirmation.
If you believe we hold information that should be removed or amended, send a written query through the support contact listed on this page. We will acknowledge it and respond within the scope our published process allows.
For questions about how a specific data point — such as a bKash deposit reference or a session log entry — is used, our support team can walk you through the relevant part of this policy.
If a section of this policy raises a question you cannot answer from the page itself, these are the routes we publish for account and policy contact. Use the channel that suits how you prefer to communicate — each one connects to the same support team.
The live chat widget is available from your signed-in account page. Start a session and mention your query relates to the privacy policy so the agent can route it correctly.
Send a written query to the support email address published in your account help section. Include your account reference and the specific data point or policy clause you are asking about.
The help centre linked from your account dashboard contains policy articles and a contact form. Use the contact form for formal data queries that require a written response and record.
Data handling at 777aya follows a few consistent practices that you can verify through your own account experience. We do not retain payment credentials beyond what is needed to reconcile your wallet; bKash deposit references and Bank Transfer records are kept for account and dispute resolution purposes, then managed in line with applicable retention rules. Your account password is stored in hashed form — we cannot read it, and neither can our support staff, which is why a reset rather than a recovery is the process we use. Cookies placed on your device fall into functional and analytical categories; you can adjust non-essential cookies from the settings link in your account. If we make a material change to this policy, we will notify you through your registered contact before the change takes effect. This page is the published version of that policy; any update replaces prior versions here.
bKash and Bank Transfer references are kept only as long as needed for wallet reconciliation and dispute handling. We do not hold full payment credentials, and retention periods follow applicable local and platform rules.
Passwords are hashed on storage. Unusual login patterns trigger an account flag visible to our support team. You can review active sessions from your account security tab and end any you do not recognise.
Functional cookies keep your session active. Analytical cookies help us understand lobby navigation. You can turn off non-essential cookies at any time through the cookie settings link inside your account dashboard.
When this policy changes in a material way, we send a notification to your registered contact method before the updated version goes live. The current version is always the one published on this page.
These are the questions that come up most often when account holders read through this policy. If yours is not here, the support routes in the section above will get you a direct answer.
No. We record only the transaction reference and amount when you use bKash or Bank Transfer. Your PIN and banking credentials stay between you and your payment provider. We never see or store them.
We hold your registration details, linked payment method references, session logs and any correspondence you have sent to support. You can request a summary of this through our published support contact routes.
Contact support through live chat or the support email in your account help section. Include your account reference and the correct information. We verify your identity first, then update the record on our side.
You can raise a formal data query through support. Whether full removal is possible depends on your local law and any outstanding account obligations. We will review and respond within the scope our published process allows.
We share limited data with payment processors and identity verification services where your account activity requires it. We do not sell personal data to third parties for marketing. Third-party links operate under their own separate policies.
If we make a material change, we notify you via your registered contact method before the update goes live. The version on this page is always current. Checking it periodically is good practice alongside watching for notifications.