Live / Sports
gdoo111 collects only the account and transaction data needed to keep your session running and your wallet records accurate. This policy explains what we hold, why we hold it, and the steps you can take to review or update it — access and eligibility depend on your local law and the eligible regions we serve.
When you register or log in, we collect the details you submit directly: your name, contact information, and the account credentials you set. When you make a deposit or withdrawal through bKash, Nagad, or Rocket, we record the transaction reference and amount against your account wallet — we do not store your mobile banking PIN or full wallet credentials. We also collect device and browser signals automatically: your IP address, session timestamps, and the pages you visit within our platform. These signals help us detect unusual activity on your account and keep your session consistent across mobile and desktop. Cookies are used to maintain your logged-in state and to understand which lobby sections you open most often; you can adjust cookie preferences through your browser settings. We retain active account records for as long as your account remains open. If your account is closed, we hold only the records required by applicable data retention obligations, and then delete the rest. This policy applies to the gdoo111 platform only; third-party payment processors like bKash and Nagad operate under their own privacy terms.
Transaction references tied to your bKash deposits are logged against your wallet record. We do not access your bKash account directly or retain your mobile number beyond account verification.
Nagad transfer references appear in your transaction history inside your account. The record shows amount and timestamp; Nagad's own privacy policy governs what they store on their side.
Rocket payment confirmations are stored as transaction entries in your account wallet. Review them any time under the transaction history tab in your account area.
Bank Transfer records include the reference number and credited amount. These entries remain visible in your account history for the duration your account is active.
Not everything you encounter while using gdoo111 falls under this policy. We cover what happens on our own platform — your account session, wallet activity, and the data you submit to us directly. Third-party services connected to your session, including payment processors and game content studios, maintain their own data practices. Understanding the boundary helps you know where to direct a question.
Login credentials, session tokens and account preferences you set on gdoo111 are fully within scope. We control how that data is stored, who can see it and how long it is kept.
Transaction references for bKash, Nagad, Rocket and Bank Transfer deposits recorded inside your gdoo111 wallet are covered. The payment processor's own systems are outside our policy scope.
The pages, game lobbies, promotional notices and support articles you read on gdoo111 are covered by this policy in terms of how we log your interaction data with that content.
Game content studios, external analytics tools and payment networks operate under their own privacy terms. This policy does not extend to those services; check their published documents directly.
You have concrete choices about the data we hold on your account. Reviewing your own records is the quickest starting point — open your account area and check the transaction history tab to see every deposit and withdrawal reference we have logged for you. If any detail looks wrong, you can submit a correction request through our support contact; we will check the record against the original submission and update it where an error is confirmed. Deleting your account removes your active profile and personal details from our live systems; records required under applicable data obligations are held only for as long as those obligations require, then removed. You can also ask us to clarify what specific data category we hold and why. We aim to respond to straightforward data questions within a reasonable period, though response times depend on the complexity of the request and the volume we are handling at that time. All requests should go through the published support route so we can verify your identity before releasing or changing any record.
Log in and open the transaction history tab to see every wallet entry we hold against your account. No support contact is needed for this — it is visible to you directly.
If your name, contact information or any other submitted detail is wrong, raise a correction request via our support contact. We verify against the original submission before making any change.
Not sure why a specific data point is held or how long it stays? Send the question through our support route with your account reference and we will explain the applicable retention rule.
Closing your account removes your active profile data. Submit the request through support; we will confirm what is removed immediately and what is held under applicable retention obligations.
All data and privacy questions should come through the published contact routes below. Have your account reference ready when you write — it lets us pull the correct record without delay and verify that the request is coming from the registered account holder. We handle data questions separately from general account support so they reach the right review step.
Send data requests, correction submissions and policy questions to our support email address listed on the Contact page of gdoo111. Include your account reference in the subject line.
The live chat widget on gdoo111 connects you to our support team directly. Use it for straightforward privacy clarifications or to get directed to the right submission route for a formal request.
The Help section inside your logged-in account area lists the current support routes and provides the submission form for data-related requests. Check there first for the most current contact details.
Security and data discipline are built into how we run account sessions. We use encrypted connections for all login and wallet activity so your credentials and transaction references are not exposed in transit. Cookie settings are adjustable in your browser at any time; disabling non-essential cookies does not prevent you from logging in or completing a deposit through bKash, Nagad or Rocket. Account security depends on the password and verification method you set at registration — keep those details private and contact support immediately if you suspect unauthorised access.
All account login and wallet transactions on gdoo111 run over encrypted connections. This covers your credentials, session data and every bKash, Nagad, Rocket or Bank Transfer reference we record.
We use session cookies to maintain your logged-in state and preference cookies for lobby layout. You can manage or block non-essential cookies through your browser settings without losing account access.
Active account data is kept while your account is open. Once an account is closed, we remove personal details as soon as applicable retention obligations allow. We do not keep data longer than necessary.
To update stored details or query a retention decision, use the support contact routes on gdoo111. We verify your identity from your account reference before acting on any data change request.
These are the questions we hear most often about how gdoo111 handles account and transaction data. If your question is not here, reach out through the support routes listed on gdoo111.
At registration we collect your name, contact details and the credentials you set. We do not ask for more than is needed to open and verify your account. Device and session data is collected automatically when you log in to keep your session consistent.
No. We record the transaction reference and amount from your bKash or Nagad deposit against your wallet history, but we never store your mobile banking PIN or full wallet credentials. Those remain entirely within your payment provider's systems.
Log in and open the transaction history tab to see your wallet records directly. For a broader view of what personal data we hold, send a request through the support contact on gdoo111 with your account reference included.
Yes. Submit an account closure and data deletion request via our support contact. We remove your active profile data promptly; records kept under applicable data retention obligations are held only for the required period, then deleted.
We share data only where necessary to process your transactions — for example, passing a transaction reference to bKash, Nagad or Rocket to confirm a deposit. We do not sell personal data. Game content studios receive no personal account data from us.
Use the email support address or live chat on gdoo111. Include your account reference so we can verify your identity and pull the relevant record. The Help section inside your logged-in account area also lists the current submission routes for data questions.