Slots / App
884bd keeps this policy straightforward: we collect only what we need to run your account, process transactions through bKash, Rocket and Upay, and respond to your support requests. Access to this platform depends on your local law and eligible regions.
This policy describes the categories of information we collect when you register an account, log in, navigate the site, or carry out a transaction. The information we hold falls into three broad groups: account identifiers you provide when you register (name, contact details, login credentials); transaction records tied to payment methods such as bKash, Rocket and Upay; and technical signals from your browser or device that help us keep the session stable and secure. We do not sell your personal information to third parties. Where we share data with a service provider, it is limited to what that provider needs to fulfil a specific function — for example, routing a Rocket or Upay transaction — and they are contractually bound to use it only for that purpose. Retention periods vary by data type. Transaction records are kept as long as required for financial record-keeping under applicable rules. Session and device data is held for a shorter period. You can ask us to review what we hold about you at any time through the contact routes listed in this policy. How this policy applies to you depends on your local law and the eligible regions from which access is permitted.
This policy covers the data we collect and handle directly through the 884bd platform. It does not extend to third-party websites linked from our pages, nor does it govern how payment processors or network providers handle data on their own systems. Understanding what falls inside and outside this policy helps you know where to direct any question.
Any information you provide when opening or updating your account — login credentials, contact details, verification steps shown in the account area — falls fully within this policy. We control how that data is stored, who can access it, and how long it is kept.
Records of deposits and withdrawals processed through bKash, Rocket or Upay are within scope. We hold the transaction reference and status visible in your account history. The internal processing logs of the payment provider itself sit outside our direct control and are governed by their own terms.
Technical data collected while you browse — page paths, session duration, device type — is within scope and used only to maintain a stable experience. This data is not linked to your identity unless you are logged in, and it is not shared with advertisers.
Links to external pages, game-content providers and payment network sites operate under their own privacy frameworks. We are not responsible for how those services collect or use data. Check their individual policies before providing personal information on an external site.
You have several practical options under this policy, and none of them require legal formality to start. The simplest step is to log in and review what is visible in your account area: your registered contact details, transaction history for bKash, Rocket and Upay payments, and any communication preferences you have set. If something looks incorrect — a contact detail, a wallet reference, a name spelling — you can update it directly in your account settings without contacting us first. For information that is not editable from the account area, or if you want to understand exactly what records we hold about a specific session or transaction, you can raise a written request through our support contact. We will acknowledge the request and aim to respond with the relevant details. If you believe any data we hold is inaccurate or handled outside the terms of this policy, you can ask us to correct or remove it, and we will let you know the outcome. Eligibility for certain actions may depend on your local law and the region from which you access the platform.
Log into your account and open the transaction history section to see payment records linked to bKash, Rocket or Upay. Account details, contact information and communication preferences are all visible from the same area.
If a registered detail is wrong, update it directly through the account settings fields. For fields that cannot be self-edited, submit a correction request via support and we will process it within our standard review window.
Any question about how your data is used, how long it is kept, or who can access it can be directed to our support team. Reference your account when you write so we can pull the right records without delay.
You may ask us to remove personal information we hold about you. We will review the request against our retention obligations and confirm what can be removed and on what timeline. Some financial records may need to be kept under applicable rules.
If you have a specific privacy question, a correction to request, or want to understand how a particular piece of account data is handled, these are the contact paths published on this site. Use the route that suits the nature of your question — account-linked queries are handled faster when you include your registered contact detail in the message.
Open the live chat widget from any page while logged in to ask a privacy or account-data question. This is the quickest route for questions tied to a specific transaction or account record.
Submit a written request through the support section of your account. Use this route for correction requests, data review queries or anything that requires a documented response from our team.
For formal privacy requests — removal, access or a complaint about data handling — send a message to the support email address listed in the contact section of this site. Include your account reference so we can locate the relevant records.
The steps below reflect how 884bd handles the four areas most likely to affect your account privacy. Each area has a practical entry point so you are not left guessing where to look.
Account identifiers and transaction records linked to bKash, Rocket or Upay are held in secured storage with access restricted to authorised functions. Retention periods follow our internal schedule and, where relevant, applicable financial record-keeping requirements. You can ask for a summary of what we hold.
We use session cookies to keep you logged in and to track which page state you were on. Analytics cookies, where used, record only anonymised path data. You can manage cookie preferences through your browser settings; blocking session cookies will affect login and account functionality.
Login credentials are hashed and not stored in readable form. Account access from a new device may trigger a verification step shown on screen. If you notice activity you did not initiate, use the support contact routes immediately — do not wait for a scheduled check.
Correction and removal requests are handled through the support ticket route. We confirm receipt and provide an outcome within the review window. If a request cannot be fulfilled in full — for example, where a record must be kept for financial compliance — we will explain why in writing.
These questions cover what we get asked most often about data, account records and the steps available to you. If your question is not here, the support ticket route is the right place to raise it.
We collect the details you provide at registration — your name, contact information and login credentials. Once you begin transacting, records of payment activity through bKash, Rocket or Upay are added to your account history. Device and session data is collected separately and is not linked to your identity unless you are logged in.
No. Transaction records tied to your bKash, Rocket or Upay activity are visible only within your own account. No other account holder can view your payment history. Our support team can access these records only when you raise a query that requires us to look at a specific transaction.
Yes, you can submit a removal request through the support ticket route in your account. We review every request and confirm what can be removed. Some records — particularly those tied to financial transactions — may need to be kept under applicable rules, and we will explain those exceptions clearly in our response.
We do not sell your personal data. Where we work with a service provider — for example, to route a payment or maintain platform security — we share only the minimum data needed for that specific function. Providers are bound by contract to use that data only for the stated purpose and not to retain it beyond their service scope.
Log in and open your account settings. Most contact fields can be updated directly from there. If a particular field is locked — for example, after a verification step — submit a correction request through the support ticket section and include the detail you want changed. We process corrections as part of our standard support review.
This policy applies to accounts registered on this platform. Access to the platform itself depends on your local law and the eligible regions from which access is permitted. If you are accessing from a jurisdiction where the platform is not available, the availability of any privacy rights described here may also be affected by your local rules.