Slots / Mobile
484bd is straightforward about how your account data is handled. This policy tells you exactly what we collect when you register, deposit via bKash or Bank Transfer, and use our platform — and how you can review or question any of it. Access to our services depends on your local law and eligible regions.
When you open an account with 484bd, we collect the details you submit during registration — your name, contact information and any payment identifiers connected to the method you use, whether that is bKash, Upay or Bank Transfer. We collect this to process your transactions, verify your account and keep your session secure across devices. We do not sell your personal data to third parties for marketing. Where we share data — for example, with payment processors who handle your bKash or Bank Transfer transactions — it is only to complete the service you requested. We store account and transaction records for as long as your account is active and for a further period as required by applicable rules. You can request access to the data we hold on you at any time through the support contact on this page. Our use of cookies is limited to session management and basic analytics that help us keep the platform running correctly. We do not use cookies to build advertising profiles. This policy applies to activity on 484bd and is subject to the laws of the jurisdiction governing your use of the platform, which depends on your local law and eligible region.
This policy applies to the data 484bd directly collects and processes. It does not cover third-party services you reach from our platform, and it does not extend to payment processors beyond what is needed to complete your transaction. The four areas below define the boundary clearly so you know exactly where our obligations sit.
Data collected when you register, log in or update your account details on 484bd falls fully inside this policy. This includes your email, contact number and any verification steps shown in your account settings.
Payment data connected to bKash, Upay and Bank Transfer transactions is covered here — but only the identifiers we receive to confirm a deposit or withdrawal. The payment processor's own handling of your wallet credentials sits under their separate policy.
Session cookies, page navigation data and device type that we collect to keep the site working correctly are within scope. We use this at an aggregate level to fix errors and improve how the platform loads on mobile.
Links to external services, game studio interfaces and any third-party payment landing pages operate under their own privacy terms. 484bd does not control or carry responsibility for data handling outside our own platform boundary.
You have real choices over the data connected to your 484bd account. The actions below are available to you directly — either through your account area or by contacting our support team. We aim to respond to all data requests without unnecessary delay, though the timeframe may depend on the nature of the request and applicable rules in your region. If your account includes transaction records from bKash or Bank Transfer deposits, those records are visible inside your account history. You do not need to raise a formal request just to review your own transaction log — it is already there. For anything that requires a correction, deletion or a more detailed query about what we hold, the support routes on this page are the right place to start. Eligibility to exercise certain rights depends on your local law and the region from which you access the platform.
Open your account history to see transaction records connected to bKash, Upay or Bank Transfer activity. The log shows deposit and withdrawal entries without requiring a separate data request.
If your registered name, contact number or email needs updating, go to your account settings. Fields that affect payment processing — such as your bKash-linked number — may require identity confirmation before a change is saved.
For questions about what we hold, why we hold it or how long it is retained, contact support through the published route on this page. State clearly that your query is about personal data and we will direct it to the right team.
To request deletion or restriction of your data, submit the request through our support contact. We will confirm whether the request can be fulfilled under the applicable rules for your region and account status.
If you have a question about this privacy policy — including how your bKash wallet identifiers are stored, what account data we retain or how to submit a correction — use the contact routes below. These are the channels published on 484bd. We do not publish response time commitments here because they depend on the type of request and current volume, but all privacy-related queries are handled by the team responsible for this policy.
Open the chat widget on 484bd to raise a privacy question in real time. Available through the support section of the site; suitable for quick account data queries.
Send a detailed written query to the support email address listed in the Help section of your account. Email is the recommended route for formal data access or correction requests.
The Help section inside your signed-in account area contains published guidance on data requests and links to the correct contact form for privacy-related submissions.
Our approach to data handling is built around keeping your account secure and your transaction records accurate. We do not build advertising profiles, we do not share your wallet details beyond what your chosen payment route requires, and we keep cookie use to the minimum needed for session management. The four areas below cover the specifics.
Your account credentials are stored using standard encryption practices. Access to your account data is restricted internally to teams that need it to process your transactions or respond to your support queries. We do not expose account details through any public-facing channel.
We use session cookies to keep you logged in and functional analytics cookies to identify platform errors. We do not place third-party advertising cookies. You can manage cookie preferences through your browser settings, though disabling session cookies will affect how the platform functions.
We retain account and transaction records — including bKash and Bank Transfer history — for the period your account is active and for a further period required by applicable rules. When retention is no longer needed, records are deleted or anonymised according to our internal schedule.
When this policy is updated, the revised version is published at 484bd/privacy-policy/ with the effective date noted. Continuing to use the platform after an update is posted means you have had the opportunity to review the changes. Contact support if any update raises a question for your account.
The questions below cover what we get asked most about how 484bd handles your data. If your question is not here, the support routes in the section above are the right next step.
We collect the details you enter during registration — name, email address and contact number — along with any payment identifiers linked to the method you choose, such as your bKash mobile number or bank account reference. We do not collect data beyond what your account and transaction activity requires.
We pass payment identifiers to the processor handling your chosen transaction route — bKash, Upay or Bank Transfer — only to complete that transaction. We do not sell or share your payment details for any other purpose. The processor's own privacy terms govern how they handle your wallet credentials on their side.
Your full transaction history — including bKash deposits and withdrawals — is visible in your signed-in account area under transaction history. You do not need to raise a separate request to view this log. If you see an entry you do not recognise, contact support directly through the published channel.
You can submit a deletion request through the support email listed in your account Help section. Whether we can fulfil it in full depends on your account status and applicable rules for your region. We will confirm the outcome in writing once the request has been reviewed.
No. Our cookie use is limited to session management and basic analytics that help us keep the platform running correctly for your device and browser. We do not place advertising or cross-site tracking cookies. Manage your preferences through your browser settings if needed.
Raise the issue directly with our support team via live chat or the email address in your account Help section. State that your query relates to personal data and the team responsible for this policy will handle it. Access to remedies may depend on your local law and the region from which you use the platform.