App / Live
bd009 collects and uses your personal information only to run your account, process transactions through Nagad, Upay, and Bank Transfer, and keep your session secure. This policy explains what we collect, how we use it, and what choices you have — and it applies to every account holder using bd009 from eligible regions, subject to your local law.
When you open an account at bd009, we collect the information needed to create and maintain that account — your contact details, login credentials, and the records tied to your payment activity. Transaction data from Nagad, Upay, and Bank Transfer deposits and withdrawals is stored in your account history and is accessible from the signed-in wallet section. We use this data to process your requests, respond to support queries, and meet obligations under applicable law. We do not sell your personal data to third parties for their own marketing purposes. Cookies and similar tracking tools are used on bd009 to keep your session active across pages and to understand how the site is used at an aggregate level — you can manage cookie preferences through your browser settings. Retention periods vary by data type: account records are kept as long as your account remains active and for a further period as required by applicable legal obligations. Where our service is accessed from Bangladesh, your rights and our obligations depend on local law and the eligible regions where bd009 operates. If any part of this policy conflicts with a local legal requirement that applies to you, the local requirement takes effect to the extent of that conflict.
Not every interaction with bd009 falls under the same set of rules. This section sets out which activities this policy directly governs and where separate terms apply.
Creating and using your bd009 account — login, profile details, password resets and session activity — falls fully within this policy. We control what data is collected at these steps and how it is retained.
Deposits and withdrawals made through Nagad, Upay, and Bank Transfer generate records stored in your account history. This policy covers how bd009 handles those records; the payment provider's own privacy terms also apply to their side of the transaction.
Pages and game content served on bd009 are covered by this policy for analytics and session data. Game content from our lobby studios is delivered through their platforms — those providers hold their own data practices for in-game events.
Links or services outside bd009 are not governed by this policy. If you follow a link away from our site or use a third-party wallet interface, their privacy terms apply from that point and we have no control over what they collect.
You have practical options for managing the personal data bd009 holds on your account. If you want to review the information stored against your profile — contact details, payment records, login history — open the account settings page and check the sections shown there. If any detail is incorrect, you can update most fields directly from your account dashboard; for information you cannot edit yourself, contact our support team and we will correct it. You can ask us to explain what data we hold and why we hold it, and you can request that we delete data we no longer need for legal or operational reasons. Requests of this kind are handled through our support channels. We aim to respond to data queries promptly, though the exact timeframe depends on the nature of the request and applicable legal obligations in your region. Your right to access, correct, or request deletion of your data may be limited by local law in Bangladesh and the eligible regions where bd009 operates — we will tell you if a restriction applies to your specific request.
Sign in and open the account history section to see transaction records, login events, and stored profile data. Payment entries from Nagad, Upay, and Bank Transfer appear as individual line items with timestamps.
Most profile fields can be updated directly in account settings. For fields that are locked — such as verified identity documents — raise a correction request through our support channel and we will guide you through the process.
If you want to know exactly what data we hold or why, send your query through the support options listed in the Contact section of this page. Include your registered account identifier so we can locate your records accurately.
You can ask us to remove data we no longer need to retain. We will confirm what can be deleted and what must be kept under legal obligations before acting on any removal request.
If you have a question about this privacy policy, want to exercise a data right, or need to report a concern, use the contact routes published on bd009. We do not list channels or hours we cannot verify here — check the Contact or Help section of the site for the current routes.
Raise data and privacy questions through the account support route shown in your signed-in dashboard. Include your registered details so the team can locate your records.
The Help section on bd009 covers common privacy and account questions. Check there first for documented answers before submitting a direct request.
For formal data access or deletion requests, submit a written query through the contact form published on the site. Describe the data involved and the action you are requesting.
We apply access controls and session management to limit who within bd009 can see your personal account data, and we log access to sensitive records. Your data is not shared beyond what is needed to operate your account and process your transactions.
Cookies on bd009 maintain your session state and collect aggregate usage data. You can adjust or clear cookies through your browser settings at any time. Disabling session cookies may affect login continuity across pages.
Your account is protected by your login credentials. We recommend keeping your password private and logging out from shared or public devices after each session. Unusual access events appear in your account login history.
Account and transaction records are retained for as long as your account is active and for any further period required by applicable law. When data is no longer needed and no legal hold applies, it is removed from active systems.
When this policy changes, the updated version is published on bd009 with a revised date. Continued use of your account after a change takes effect means you have seen the updated terms. Contact support if you have questions about any revision.
These are the questions we hear most often about how bd009 handles personal data. If yours is not here, reach out through the support route in your account.
We collect the details you enter during registration — name, contact information, and login credentials — along with the transaction records generated when you use Nagad, Upay, or Bank Transfer. Session and device data is also collected to keep your account secure.
Sign in to your bd009 account and open the wallet or history section. Nagad, Upay, and Bank Transfer entries appear as individual records with dates and amounts. These records are part of your account data covered by this policy.
We do not sell your data to third parties for their own marketing. We share information only where needed to process your transactions — for example, with payment providers like Nagad or Upay — or where required by applicable law.
Most profile fields can be updated directly in account settings. For locked fields such as verified identity documents, contact our support team through the channel shown in your account dashboard and we will guide you through the correction process.
Yes. You can submit a deletion request through the contact form on bd009. We will confirm what data can be removed and what must be retained under legal obligations before acting. Eligibility depends on your local law and applicable legal holds on your records.
Use the support route published in your signed-in account area or the contact form on bd009. Describe the data involved and what you believe went wrong. We will review and respond through the same channel. Availability of formal complaint routes depends on your eligible region and local law.