Mobile / App
ak 333 collects only the information needed to run your account, process wallet transactions through Nagad, Upay and Bank Transfer, and keep your session secure. What we collect, how we store it and what choices you have are set out clearly below. Access to our platform depends on your local law and eligible regions.
When you open an account with ak 333, we collect the details you enter during registration — your name, contact address and the credentials you choose. When you carry out a wallet transaction using Nagad, Upay or Bank Transfer, our system logs the reference data needed to match your deposit or withdrawal to your account record. We do not store full payment credentials on our servers; the transaction reference is the only payment-linked identifier we retain. Beyond account and transaction data, we collect standard session information — device type, browser, pages visited and session duration. This helps us identify errors, improve navigation and serve the lobby in a way that works on your device. We do not sell this data to third parties for marketing purposes. We retain account records for as long as your account remains active and for a period after closure as required by applicable rules in your jurisdiction. If you have a question about what we hold, the support route listed in this policy is the right starting point. Availability of our platform, including how data rules apply to you, depends on local law and the eligible regions we serve.
This policy covers the data ak 333 collects directly through our platform — your account, your wallet activity and your in-session behaviour on our site. It does not extend to third-party services you reach from our pages. The four areas below define what falls inside and outside the scope of this document.
Any data you enter when creating or updating your account — including login details and contact information — falls within this policy. We control how that data is stored and who can access it internally.
Transaction references linked to Nagad, Upay or Bank Transfer deposits and withdrawals are within scope. We do not store full payment credentials; only the reference data needed to match a transaction to your account.
Session logs, device identifiers and page-navigation data collected while you browse the lobby are within scope. We use this to maintain site performance and diagnose any access issues you report.
Links or integrations leading away from our domain — including payment processors and game studio environments — operate under their own privacy terms. We are not responsible for data practices outside our platform boundary.
You have specific, actionable choices about the data we hold on your account. If you want to review what information is stored, the first step is to check your signed-in account area, where your profile details and transaction history are visible directly. If something looks wrong — a name spelling, a contact address or a linked wallet reference — you can update it through the account settings fields shown there. For anything that cannot be changed through the account interface, raise it with our support team using the contact route in this policy. We will confirm receipt and work through the correction with you. If you decide to close your account, let us know through the same channel. We retain records for the period required under applicable rules in your jurisdiction, then remove personal identifiers from our active systems. Your rights under this policy depend on local law and the eligible regions we serve.
Open the account page after signing in to see the profile details and transaction history we hold. No separate request is needed to view what is already visible there.
Use the account settings fields to update a name, contact address or other profile entry. Changes take effect as soon as you save them in the interface.
If a record looks wrong and cannot be fixed through the account interface, contact our support team. Describe the specific entry and we will work through it with you.
Send a closure request through the published support route. We will confirm the request, process it and let you know the retention period that applies in your region.
If you have a question about this policy, a concern about your account data, or a correction to request, the routes below are the right channels to use. We only list contact methods that are visibly published on this site. We do not guarantee response times, but we will acknowledge your message and follow up through the same channel you used.
Open the live chat icon visible on our site pages. Describe your privacy question clearly and include your account reference so we can locate the right record.
Send a written query to the support email address published in our contact section. Use the subject line 'Privacy Query' and include your registered contact detail so we can verify your account.
The account help section of this site lists additional self-service steps for reviewing or updating your profile. Check there first for common data and settings questions before contacting the team.
We apply several layers of handling to keep your information accurate and your session activity private. Cookies, retention periods, access controls and correction requests each follow a defined process described in the items below. If any of these practices change, we update this page and the change is visible here.
We use session cookies to keep you signed in and to record page-navigation data for performance purposes. You can adjust cookie settings through your browser; turning off session cookies may affect how some lobby pages load on your device.
Access to your account record is protected by the credentials you set at registration. We do not ask for your password by email or chat. If you suspect unauthorised access, update your password immediately through the account settings page.
We keep your account data for as long as your account is active. After closure, we retain what is required under applicable rules for your jurisdiction, then remove personal identifiers from our active systems. The exact period depends on local law.
When this policy changes, the updated version is published on this page with a revised date at the top. Continued use of the platform after an update is posted means you have seen the revised terms. Check this page periodically if you want to stay current.
The questions below are ones we see most often from people reading this policy. If yours is not here, reach us through the support routes listed above.
We collect the name, contact address and login credentials you enter during registration. When you use Nagad, Upay or Bank Transfer, we also log the transaction reference needed to match it to your account. We do not store full payment credentials on our servers.
Yes. Sign in and open your account page to view your profile details and transaction history directly. For records not visible there, send a request through live chat or email support and we will identify what we hold and share it with you.
Go to account settings while signed in and update the relevant field. Most profile entries can be corrected there without contacting us. If the field is locked or the change does not save, raise it with our support team and describe the specific entry that needs updating.
We do not sell your data for marketing. We share only what is necessary to process a wallet transaction — such as a reference passed to Nagad or Bank Transfer — or what is required by applicable rules in your jurisdiction. Game studios supply game content only and do not receive your account data.
After account closure, we keep records for the period required under applicable rules in your jurisdiction. Once that period ends, personal identifiers are removed from our active systems. Contact our support team to start the closure process and ask about the retention period that applies to you.
We use session cookies to keep you signed in and to track page performance. You can disable cookies in your browser settings, but some lobby pages and account features may not load correctly without session cookies active. Functional cookies are required for the signed-in account area to work.