bdg35 Privacy Policy: How We Handle Your Information
bdg35 is clear about what data we collect when you open an account, make a deposit through Nagad, Upay or Bank Transfer, and use our platform — and we are equally clear about what you can do with that information. Access to this platform depends on your local law and eligible regions; this policy applies wherever that access is permitted.
Account data clarity
Transaction record access
Your right to review and correct
Published contact route
POLICY SCOPE NOTICE
What This Privacy Policy Covers at bdg35
When you create an account with bdg35, we collect the details you enter during registration — your name, contact information and the payment identifiers linked to your chosen funding method. If you deposit via Nagad or Upay, the transaction reference associated with that wallet action is recorded in your account history. If you use Bank Transfer, the bank reference and amount are logged the same way. We also collect standard technical data: device type, session timestamps and browser signals that help us keep your account accessible on mobile. We do not sell your personal data to third parties for their own marketing purposes. We share data only where required to process your payment, verify your account identity or meet an obligation under applicable law. Cookies and similar tracking tools are used on our site to remember your session preferences and maintain login continuity. You can adjust cookie settings through your browser at any time. This policy does not extend to third-party services you access through links on our site — those services operate under their own terms. Availability of this platform and the scope of data rights available to you depend on your local law and the eligible regions from which access is permitted.
Nagad
Transaction references from Nagad deposits are stored in your account history and used only for payment verification and dispute resolution.
Upay
Upay wallet identifiers linked to your deposits are retained for the period required to resolve any transaction query on your account.
Bank Transfer
Bank reference numbers and transfer amounts are logged against your account record and are accessible to you from your transaction history page.
INSIDE VS OUTSIDE
Where This Policy Applies and Where It Does Not
Not every piece of data or every service on the platform falls under the same rules. This section draws a clear line between what our policy directly governs and what sits outside it. Understanding this boundary helps you know where to direct a question and what to expect when you raise one.
Account access data
Login credentials, session records and account-level identity information you provide during registration are fully within the scope of this policy. You can request a review or correction of this data by contacting us through the support route published on the site.
Transaction records
Payment records generated when you fund your account — whether via Nagad, Upay or Bank Transfer — are covered by this policy. These records appear in your account history and are retained for the period required by applicable law.
Site content and game data
Game session data such as round outcomes and bet amounts is logged to maintain the integrity of your account balance. This data is within scope and can be referenced when you raise a query about a specific round or transaction.
Third-party services
External links on our site lead to services that run under their own privacy terms. Once you leave the bdg35 environment, this policy no longer applies. We cannot control how those services handle your data.
YOUR PRACTICAL RIGHTS
Actions You Can Take Under This Policy
Your data is not static. You have concrete steps available to you whenever you want to review, correct or question what we hold. Start by opening your account settings — the profile section shows the contact and identity details we have on record for your login. If something is wrong, you can update it directly or raise a correction request through our support route. Transaction records are visible from the history tab in your account; if a Nagad, Upay or Bank Transfer entry looks incorrect, note the reference and bring it to support. For any question about what data we hold, how long we keep it or how it was used, a written request sent through our published contact path will receive a response. We do not require you to justify a data query — asking is enough. Your right to access and correct your own account data applies regardless of where you deposited or what account activity you have had.
Review your record
Open account settings and check the profile section to see the identity and contact details we hold against your login.
Correct account details
Update your contact information directly in account settings, or submit a correction request through the support route if the field is locked.
Query a transaction
Find the relevant entry in your account history — note the reference number — then bring it to support with a clear description of the issue.
Request data information
Send a written request through our published contact path to ask what data we hold, how it is used or how long it is retained. No extra justification is required.
REACH OUR TEAM
How to Contact Us About This Policy
If you have a question about your data, a correction to submit or a policy point you want explained, these are the routes we publish for reaching us. Use the channel that works for your situation — account-specific queries are easiest to handle when you include your account reference.
Live Chat
Open the live chat widget from any page on the site. State that your query relates to a privacy or data matter and our team will route it to the right place.
Email Support
Send your data or privacy question to our support email address listed in the Contact section of the site. Include your account reference so we can locate your record without delay.
Account Help Centre
The Help section inside your signed-in account area contains published policy documents and a direct form for data-related requests. Check there first for common policy questions.
HOW WE HANDLE DATA
Our Approach to Data Security and Retention
Security and data handling at bdg35 are built around the account-to-wallet flow that defines how you use the platform. We apply standard encryption to data in transit, which covers the session between your device and our servers — this is especially relevant when you are on mobile and submitting a payment via Nagad or Bank Transfer. Data is retained only for as long as required to maintain your account, process outstanding transactions or meet any applicable legal obligation. Once that period ends, personal data is removed from active records according to our internal retention schedule. You can request information about how long your specific data is held by contacting support.
Session encryption
Data moving between your device and our platform is encrypted in transit. This applies to account login, payment submission and transaction history retrieval on both mobile and desktop.
Cookie management
We use session cookies to keep you logged in and preference cookies to remember display settings. You can clear or block these through your browser settings at any time without losing your account access.
Retention periods
Account identity data and transaction records are kept for the period required by applicable law and our own account-management obligations. After that window, data is removed from active systems.
Policy updates
When we update this policy, the revised version is published on this page. Continued use of your account after a policy update indicates you have read the revised terms, so check this page if you have been away for a while.
POLICY QUESTIONS ANSWERED
Common Questions About Your Privacy at bdg35
These are the questions we receive most often about how we collect, store and handle personal data. If your question is not here, contact us through the support routes listed on this page.
What personal data does bdg35 collect when I open an account?
We collect the name, contact details and identity information you submit during registration. If you fund your account via Nagad, Upay or Bank Transfer, the payment reference associated with that transaction is also recorded against your account.
Can I see the data bdg35 holds about me?
Yes. Open account settings to view the identity and contact details on record. Your transaction history — including every Nagad, Upay and Bank Transfer entry — is visible from the history tab inside your signed-in account.
How do I correct wrong information in my account?
Some fields are editable directly in account settings. If a field is locked or the correction involves identity details, submit a request through live chat or our support email with your account reference and the correct information clearly stated.
Does bdg35 share my data with third parties?
We share data only where necessary — to process a payment, verify your account identity or comply with an applicable legal obligation. We do not sell your personal data to third parties for marketing purposes.
How long does bdg35 keep my personal data?
Data is kept for as long as your account is active and for the period required by applicable law after it closes. Once that retention window passes, personal data is removed from active records. Contact support for specifics on your account's retention period.
What happens to my data if I stop using my account?
Your account data remains on record for the legally required retention period after your last activity. Once that period ends, it is removed. Send a written data query through our published contact route if you want details specific to your account.