Live / Mobile
528bd handles your information with a clear purpose: to run your wallet, process transactions through Upay and Bank Transfer, and keep your session secure. This policy explains exactly what data we collect, how we use it, and what choices you have — with access depending on your local law and eligible regions.
When you open an account on 528bd, we collect the details you submit during registration: your name, email address, contact number and the payment method you choose to fund your wallet. Where you use Upay or Bank Transfer, we record transaction references tied to your account — not your full payment credentials. We do not store card numbers or mobile banking PINs on our servers. We also collect session data automatically: your device type, browser, IP address and pages visited. This helps us keep the lobby working correctly on mobile and desktop. We do not sell this data to third parties for their own marketing. Data we hold is used to: verify your account identity, process deposits and withdrawals through your chosen payment rail, send account-related messages (not promotional mail unless you opt in), and detect unusual session activity. Retention periods follow the requirements of applicable law in the regions where 528bd operates. If you have questions about how long specific data is held, contact our support team through the published route. Access to this platform depends on your local law and eligible regions.
Transaction references linked to your Upay transfers are logged against your account ID only — we do not store the wallet credentials you enter on the Upay interface.
Bank Transfer deposit references are retained for reconciliation. Your full bank account number is not stored by 528bd after a transfer is confirmed.
If bKash or Nagad is made available in your region, the same reference-only logging applies — credentials stay within the respective payment provider's environment.
This policy covers the data 528bd collects and controls directly. It does not extend to third-party services that operate their own privacy terms — such as payment providers or game studios whose environments you enter when you tap through to a payment gateway or a studio-hosted game screen. Understanding the boundary helps you know where to direct any data question.
Covered. Registration details, login history, session tokens and account wallet records are all within the scope of this policy and subject to your access rights.
Covered for reference data 528bd holds. The payment provider's own interface — Upay portal, Bank Transfer page — is governed by that provider's separate privacy terms, not ours.
Covered. Cookies and analytics data collected on 528bd pages fall under this policy. You can manage browser-level cookie settings; see the cookie section in our full published policy.
Not covered here. Game studios such as PG Soft and Pragmatic Play operate their own data environments when a game loads. Check each provider's terms for how they handle session data inside their game engine.
Your account is the primary place to review and adjust what data 528bd holds for you. After logging in, the account settings section shows your registered contact details, linked payment method references and communication preferences. You can update your email address or phone number directly from that screen — changes take effect on your next login session. If you believe a record is inaccurate, raise it through the support route listed on the Contact page. Our team can check the data against your account history and correct it where the record is wrong. For a broader data query — such as asking what categories of information we hold — submit your question in writing through the same published support channel. We will respond within the period required under applicable law for the eligible region. You do not need to close your account to ask a data question, but if you choose to close it, account closure instructions are available in your settings.
Log in and open the account settings page. Your registered details, transaction references and communication preferences are displayed there for you to read.
Update your contact number or email directly in account settings. For corrections to transaction records or identity data, contact support with the specific details you want checked.
Send your question through the published support channel. Describe the data category you are asking about and include your registered account email so we can locate your record.
Account closure removes your active session and flags your record for the retention process set by applicable law. Follow the closure steps in your account settings or ask support to initiate it.
If any part of this privacy policy raises a question you cannot answer by reading your account settings, use one of the contact routes published on the 528bd site. Privacy questions are handled through the same support channels as account queries — there is no separate privacy-only inbox. When you write in, include your registered email address and a clear description of the data question so we can locate the right record and respond accurately.
Open the chat widget on the 528bd site to speak with a support agent about your account data or privacy question. Use your registered account to identify yourself at the start of the chat.
Send a written privacy query to the email address listed on the Contact page. Written requests give us a clear record of what you asked and let us reply with documented answers.
The Help section on the site covers common account and data topics. Check there first for answers about cookie settings, account records and communication preferences before opening a direct query.
Security measures on 528bd are applied at the account and session level. Your login credentials are stored in hashed form — we do not hold your password in plain text. Session tokens expire after a period of inactivity, which means an unattended browser tab does not stay authenticated indefinitely. These are standard account-security practices, not marketing claims, and you can verify the session behaviour yourself by leaving your account idle.
We use functional cookies to keep your session active and analytics cookies to understand how pages perform. You can manage cookie preferences through your browser settings; disabling analytics cookies does not affect your ability to log in.
We keep account and transaction records for the period required by applicable law in the eligible regions where 528bd operates. Once the retention period passes, records are deleted or anonymised according to the same legal requirements.
For data requests, corrections or policy clarifications, use the published support routes — live chat or the email address on the Contact page. There is no separate data-protection address; all privacy queries go through the standard support channel.
We update this policy when our data practices change or when applicable law requires it. The current version is always the one published at 528bd/privacy-policy/. Continued use of your account after an update means you have read the revised terms.
These are the questions we get asked most often about how 528bd handles your data and what rights you have as an account holder.
We collect your name, email address, contact number and the payment reference details linked to your chosen method — such as Upay or Bank Transfer. We also collect session data like device type, browser and IP address automatically when you access the site.
No. When you use a mobile wallet like bKash or Nagad, the credential entry happens within that provider's own interface. We record only the transaction reference that comes back to your 528bd account — not your wallet PIN or login details.
Log in to your account and open the account settings page. Your registered details and payment references are shown there. For a broader data summary, send a written request through live chat or the support email address listed on the Contact page.
Yes. For corrections to contact details, update them directly in account settings. For corrections to transaction records or a deletion request, contact support in writing. We will act within the period required by applicable law for your eligible region.
Only partially. This policy covers data 528bd collects on its own platform. When a game from a studio such as PG Soft or Pragmatic Play loads, that studio's own data environment applies. Check each provider's published terms for how they handle in-game session data.
The current version is always published at 528bd/privacy-policy/. We do not send a notification for every minor update, so we recommend checking back if you have a specific question. Continuing to use your account after an update confirms you have read the revised policy.