App / Mobile
520d is clear about what data we collect when you use this platform and how it stays with us. Access to this service depends on your local law and eligible regions — read through these points so you know exactly where you stand.
When you open an account on this platform, we collect the details you provide during registration — your name, contact information and the payment method you choose to link, such as bKash or Bank Transfer. We use this to process your transactions, maintain your account wallet and respond to any support request you raise through our published channels. We do not sell your personal data to third parties. Data shared with payment processors — including bKash and Bank Transfer providers — is limited to what those providers need to complete your transaction; we do not pass additional profile data beyond what the transfer requires. Cookies and session data help us keep the platform running smoothly on your mobile browser; you can adjust cookie preferences through your browser settings at any time. We retain account records for as long as your account remains active and for the period required under applicable rules in eligible regions. If you close your account, we follow standard retention windows before removing identifiable records. Because access to this service depends on local law and your eligible region, the specific rules that apply to your data may vary. If you have a question about how your information is handled, the support routes listed on this page are where to start.
When you use bKash to fund your account wallet, we pass only the transfer reference and amount to the payment processor. No additional profile detail travels with that request.
Bank Transfer deposits are logged against your account wallet. The bank reference number and amount are retained for the duration required by applicable rules in your eligible region.
Device identifiers and session tokens keep your mobile login active. You can clear these by logging out or adjusting your browser cookie settings — no app install required.
Messages you send through our support routes are stored with your account file. We keep them to resolve follow-up questions and to maintain an accurate record of what was agreed.
Not every interaction with 520d falls under the same rules. This section draws the line clearly so you know which activities this policy covers and which are handled by separate frameworks or third-party terms. Access and eligibility remain subject to your local law and the eligible regions for this service.
Everything that happens inside your signed-in account — wallet balance, transaction history, contact details, session activity — is covered by this policy. We hold those records and you can request to review them.
When a payment moves through bKash or Bank Transfer, the segment of the journey inside those providers' own systems is governed by their own privacy terms — not ours. We cover only the record we hold on our side.
Browsing the lobby, filtering game categories and reading published terms does not create a personal data record beyond your session cookie. No purchase or profile data is logged from unauthenticated browsing.
Any external link — a payment provider page, a studio site — is outside our policy boundary. Once you leave this domain, the privacy rules of that destination apply. We do not control or take responsibility for those policies.
You have practical options when it comes to the data we hold. The first step for most requests is your signed-in account area — transaction records, linked payment methods and contact details are visible there directly. If you spot an error in your registered name, phone number or email address, you can update those fields from the account settings page. For anything that requires our involvement — a data question we cannot resolve through self-service, a request to understand what records we hold, or a concern about how your information was used — our support routes handle it. Send the request with your account reference so we can locate your file without asking you to repeat yourself. We aim to acknowledge data-related queries within a reasonable window and to keep you informed if the matter requires more time. Your right to ask questions about your data does not depend on whether your account is currently active, though the scope of what we can share may be shaped by applicable rules in eligible regions.
Log into your account and open the transaction history and profile sections. Most account data is visible there without needing to contact support.
Name, phone and email fields can be edited from the account settings page. If a field is locked, raise it through support with your account reference number.
Use the support routes on this page to send a written request. Include your account reference so we can locate your file and respond without unnecessary back-and-forth.
A closure request goes through support. We follow the retention window required under applicable rules before removing identifiable records from active systems.
If the account area does not answer your question, these are the published routes to reach us. Use your account reference in every message so we can pull your file without delay. Availability depends on your eligible region and local access conditions.
Open the chat widget from the footer of any page while signed in. State that your message is a privacy or data request and include your account reference in the first message.
Write to our support address published in the help section of your signed-in account area. Mark the subject line as a data request for faster routing to the right team.
The help section inside your signed-in account lists current contact options and any status notices. Check there first — some requests can be resolved through self-service without opening a ticket.
These are the four areas where our data practices matter most to your account experience. Each one reflects what we actually do — not a template statement. If you want more detail on any of these, the support routes above are the right place to ask.
We use cookies to keep your mobile session active and to remember your lobby preferences. You can clear or block them through your browser. Blocking session cookies will require you to log in again each visit.
Access to your account data requires your login credentials. We do not share account credentials or wallet details with any party other than the payment processor handling your active transaction.
We hold account records for as long as your account is active and for the period required under applicable rules in eligible regions. Closed accounts move to a reduced-retention state before identifiable data is removed.
Use the support routes on this page to request a correction, ask what data we hold, or query how a specific record was used. Include your account reference so we can respond without asking for repeat details.
These are the questions we hear most often about how this policy works. If yours is not here, reach out through the support routes listed above.
We collect the details you provide at registration — name, contact information and your chosen payment method, such as bKash or Bank Transfer. Session and device data is collected automatically to keep your account login active on mobile.
We do not sell your data. Payment processors like bKash and Bank Transfer receive only the minimum needed to complete your transaction. No additional profile detail travels with those requests. Third-party links leave our policy boundary entirely.
Log into your account and check the transaction history and profile sections — most records are visible there directly. For anything not shown in the account area, raise a written request through our support routes with your account reference.
Contact information and some profile fields can be edited from account settings. If a field is locked or the change requires verification, contact support with your account reference and the correction you need. We will confirm once it is updated.
Once you request closure, we move your account to a reduced-retention state. Identifiable records are removed after the period required under applicable rules in your eligible region. You can ask support for more detail on that window.
Access to this service and the specific rules covering your data depend on your local law and eligible region. The policy sets out our baseline practice; local rules may add to or adjust certain rights. Check with support if you have a region-specific question.