Sports / Slots
520bd is clear about what data we collect from you, why we hold it, and how you can review or correct it. Access to our platform depends on your local law and eligible regions — this policy covers what applies once you are using our services.
When you create an account with us, we collect the information you submit during registration — your name, contact details and any identity verification documents required to process your account. When you make a deposit or withdrawal using Nagad, Upay or Bank Transfer, we record the transaction reference, amount and wallet identifier linked to that activity. This is so we can match payments to your account correctly and respond to any dispute you raise. We also collect technical data from your device and browser session — IP address, device type and session timestamps. This helps us detect unusual activity on your account and maintain session integrity. We do not sell your personal data to third parties. We share it only where it is required to process a transaction, verify your identity, or respond to a lawful request that applies to your eligible region. Retention periods depend on regulatory requirements applicable to the region where your account operates. Where data is no longer needed for those purposes, we remove it from active records in line with our internal retention schedule.
Each Nagad deposit or withdrawal linked to your account is recorded with its reference number and wallet identifier so payment queries can be resolved accurately.
Upay transaction data is held against your account history. You can view your transaction log in the account wallet section after signing in.
Bank Transfer entries are matched to your account using the reference you provide. We hold these records for as long as your account remains active or as required by applicable rules.
Browser, device type and session timestamps are logged to protect your account from unauthorised access. This data is not shared with advertisers or marketing networks.
This policy governs data collected directly by 520bd through our website and account system. It does not extend to third-party services you access via external links, and it does not override the terms of any payment provider such as Nagad or your bank. The four areas below set out what is inside and outside the scope of this document so you know exactly where our obligations begin and end.
Data collected when you register, log in or update your account details — including email, contact number and wallet identifiers — falls fully within this policy. We are responsible for how that data is stored and who can access it.
Payment records processed through Nagad, Upay or Bank Transfer via our platform are covered here. The privacy practices of those payment providers are governed by their own separate policies, which we do not control.
Usage data tied to which pages you open, how long you stay and which game categories you browse is collected by our analytics layer. This data is used internally to improve navigation and is not tied to your identity externally.
Game studios supplying content to our lobby — such as Pragmatic Play or Microgaming — operate under their own data terms for game-engine telemetry. Those terms are outside the scope of this policy; we cover only what our platform collects directly.
You have practical options for managing how your data is held. Sign in to your account and open the profile section to review the personal details we hold on file — name, contact number, wallet identifiers and linked payment methods. If any detail is incorrect, you can update it directly through the account settings fields shown there. For information that cannot be changed through self-service — such as historic transaction references or identity documents already submitted — you can contact our support team and ask for a review. We will confirm what we hold and explain the process for correction or removal where applicable. If you want to understand specifically how long a record is retained, that question belongs in a written support request so we can give you a documented answer. Any request relating to data you believe was collected without your knowledge should also be sent through the support route; we treat those as priority queries and acknowledge them in writing.
Sign in and open the account profile page to see the personal and payment data we hold. Transaction records are listed in the wallet section by date and reference.
Contact number, email and wallet identifiers can be updated through account settings. For document-level corrections, submit a request via our support channel.
If you are unsure what we hold or why, send a written query through the support route. We will confirm the categories of data linked to your account and the reason each is held.
For deletion requests or concerns about how data was collected, contact support directly. We acknowledge data-related requests in writing and explain any steps needed from your side.
If you have a question about this policy, want to request access to your data, or need to raise a concern, use the contact routes below. We only list channels that are visibly published on the site — we do not promise specific response windows, but every message sent through these routes is logged and assigned for review.
Open the chat widget from any page while signed in. State that your query is about your account data or this privacy policy so it is routed to the right team.
Send your data or privacy query to the support email address shown on our contact page. Include your registered account email so we can locate your record.
The help section inside your signed-in account lists published guidance on data access and correction steps. Start there for self-service answers before opening a support ticket.
We keep your account data behind access controls that limit which internal functions can read or write your personal record. Cookies are used on our site for session management and basic analytics — not for third-party advertising profiles. You can manage cookie preferences through your browser settings at any time. Data linked to closed accounts is retained only for as long as required by applicable rules in your eligible region, after which it is removed from active systems. If the retention obligation changes, this policy will be updated and the revised version will be posted here.
Session cookies keep you signed in while you browse. Analytics cookies help us understand page navigation. Neither type is shared with advertising networks. Manage them through your browser settings.
Access to your personal record inside our systems is restricted by role. We do not expose wallet identifiers — Nagad, Upay or Bank Transfer references — to any part of our system that does not require them for payment processing.
We hold your data for as long as your account is active and as required by rules applicable to your eligible region. Once that obligation ends, the record is removed from active storage.
When this policy changes, the updated version is posted at this URL with a revised date. Continued use of your account after an update means you have seen the revised terms.
The questions below cover what we hear most from account holders about data, access and their rights under this policy. If your question is not answered here, use the support contact routes listed on this page.
We collect the name, contact number and email you enter during registration, plus identity documents if your account tier requires verification. Payment wallet identifiers — such as your Nagad or Upay number — are recorded when you make a transaction.
Yes. Sign in, open the account profile section, and the personal details and transaction records linked to your account are displayed there. For document-level records, submit a written request through our support channel and we will confirm what is held.
Contact number, email and payment wallet details can be updated directly in account settings. For submitted identity documents or historic records that cannot be self-edited, contact our support team with a written correction request and your registered email address.
Game studios receive only the session data needed to run their game engine — no name, wallet number or full account record is passed to them. Studios operate under their own data terms for game-engine telemetry, which is outside the scope of this policy.
Retention after account closure depends on the rules applicable to your eligible region. We hold records only for as long as those obligations require, then remove them from active systems. Send a support request if you want a specific answer for your account.
Each transaction reference is stored against your account for dispute resolution and payment matching. These records are kept for the period required by applicable regional rules and are not shared outside the payment processing purpose they were collected for.
Send a written query through our support email or live chat, mark it as a data concern, and include your registered account email. We treat these as priority queries, acknowledge them in writing, and explain what data we hold and the basis for holding it.