App / Sports
h31bdt is straightforward about what data we collect when you use our platform, why we collect it, and how you can review or correct it at any time. Access to our services depends on your local law and eligible regions — this policy explains your rights wherever that access applies.
When you create an account on h31bdt, we collect the details you submit directly — your name, contact address, and the payment method identifiers you connect to your wallet, such as a Nagad mobile number, an Upay account reference, or a Bank Transfer detail. We also collect session data generated automatically when you browse the platform: device type, browser version, IP address and interaction logs. We use this information to operate your account, process transactions you initiate, resolve support queries, and keep the platform secure. We do not sell your personal data to third parties. We do not share it with advertisers. Data shared with payment processors — Nagad, Upay, Bank Transfer — is limited strictly to what those processors need to complete a transaction you have authorised. We keep account records for as long as your account remains active and for a period after closure as required by applicable financial and regulatory obligations in supported regions. If you have questions about what data we hold, the support routes listed in this policy are the right starting point. Access to this platform depends on your local law and the eligible regions we serve.
This policy covers data processed directly by h31bdt when you use our platform. It does not extend to external websites we may link to, payment networks operating under their own terms, or third-party services you connect independently. Understanding the boundary between what we control and what we do not is practical account knowledge.
All data collected when you log in, update profile details or change your account settings falls within this policy. We process this data to keep your account functional and to verify your identity when you request changes.
When you initiate a deposit or withdrawal through Nagad, Upay or Bank Transfer, we pass only the data needed to complete that transaction to the relevant processor. The processor's own privacy terms govern how they handle that data on their side.
Interaction data generated as you browse the lobby, open game categories or view account notices is collected by us and used solely for platform operation, security monitoring and improving navigation paths — not for advertising profiling.
Links to external sites, embedded tools not operated by us, and any service you connect outside the h31bdt platform are outside this policy's scope. We have no visibility into or control over data collected by those external services.
Your account gives you direct access to several data-related actions without needing to contact support first. From the account settings page you can review the profile information we hold, update a contact detail, and see which payment methods — Nagad, Upay, Bank Transfer — are currently linked to your wallet. If something looks wrong, the correction path is to update the field directly and save; for fields you cannot edit yourself, a support request is the right route. Where you want to know exactly what data we hold beyond your visible profile, you can raise a data enquiry through the support channels listed in this policy. We will acknowledge the request and respond with what we can share consistent with our security and legal obligations. Requests to close an account and delete associated data are handled through the same support route; we will confirm what is removed and what must be retained under applicable financial rules. Eligibility for all these actions depends on your local law and the region your account falls under.
Open the account settings page to see your current profile data, linked payment methods and transaction history. This is the fastest way to check what we hold without raising a formal request.
Editable fields can be updated directly in settings. For restricted fields — such as registered mobile number or verified identity details — contact support with the correction and the account reference.
If you want a full picture of the data associated with your account, send a data enquiry through the live chat or email route. We respond with what we can disclose under our security and legal obligations.
A closure and data-deletion request is handled by the support team. We will confirm what is removed immediately and what must be kept for the retention period required by applicable financial rules.
If this policy raises a question you cannot resolve by reviewing your account settings, we have published contact routes you can use. Each route is staffed and monitored; response times vary by channel and by queue volume at the time you write in. We do not publish support hours we cannot stand behind, so check the contact page for current availability.
Open the chat widget from any page while signed in. Use this route for account-specific data questions, correction requests or to ask what information is linked to your wallet. A team member will take the request forward.
Send a detailed written request to the support email published on the contact page. Include your account reference and the specific data question or correction you need. This route is suited for formal data enquiries and closure requests.
Many data actions — reviewing your profile, updating contact details, checking linked Nagad or Upay references — are available directly in account settings without needing to contact us. Start there before raising a support request.
Knowing how your data is stored and who can access it is a reasonable question to ask any platform you use for real transactions. We apply access controls internally so that account data is visible only to teams with an operational need — support staff handling a query you raised, compliance teams acting on a regulatory obligation. We do not grant general internal access to payment identifiers such as Nagad or Upay references; those are handled through encrypted channels within the transaction flow only.
We use session cookies to keep you signed in and functional cookies to remember your language and display preferences. Analytical cookies help us understand navigation patterns at an aggregate level. You can manage cookie preferences through your browser settings; removing functional cookies may affect how your account behaves.
Password changes and account recovery steps are handled through the authenticated account page. We do not request your password by email or chat. If you receive an unsolicited message asking for credentials, treat it as suspicious and notify us through the published support route immediately.
We keep active account data for as long as your account is open. Following closure, certain transaction and identity records are retained for the period required by applicable financial regulations in supported regions. After that period, data is deleted or anonymised. The exact retention window depends on your jurisdiction.
When we update this policy, the revised version is published on this page with a new effective date. Continuing to use h31bdt after a policy update means you have seen the revised terms. If a change affects how we use data in a material way, we will place a notice in your account area.
The questions below cover what we hear most often about data, account records and how to act on your rights under this policy. If your question is not here, the support routes listed above are the right next step.
We collect the registration details you submit — name, contact information and any payment method references you link, such as a Nagad number or Bank Transfer detail. We also collect device and session data automatically when you use the platform. We use this data to operate your account and process transactions you initiate.
Payment identifiers like your Nagad or Upay reference are passed only to the relevant payment processor and only to complete a transaction you have authorised. We do not share them with advertisers or unrelated third parties. The processor handles that data under their own privacy terms once the transaction leaves our system.
Editable fields are available directly in your account settings page — update the field and save. If the detail is restricted and cannot be changed through settings, contact the support team via live chat or email, providing your account reference and the correction you need. We handle those requests through the support queue.
Yes. Send a data enquiry through the email support route published on the contact page. Include your account reference so the team can locate your records. We will respond with what we can share in line with our security obligations and the applicable rules for your region.
On closure, your active profile and preferences are removed from live systems. Certain transaction and identity records are retained for the period required by financial regulations in your eligible region. After that retention window, retained data is deleted or anonymised. The support team can confirm the specific window that applies to your account.
We use session cookies to keep you signed in, functional cookies for display preferences, and aggregate analytical cookies to understand navigation. You can manage or remove cookies through your browser settings. Removing functional cookies may change how your account displays or behaves on return visits, but will not affect your stored account data.