Casino / Slots
This policy explains exactly what account data bdtk30 collects when you use the lobby, make a Nagad transfer or contact support — and what choices you have over that data. Access to the platform depends on your local law and eligible regions; this policy applies wherever the service is available to you.
When you open an account, bdtk30 collects the details you enter during registration — name, contact information and the payment method you connect, such as Nagad or Bank Transfer. We use this to process your wallet activity, route support queries and maintain your account record. We do not sell your personal details to third parties, and we do not share them with external marketing partners outside of what is disclosed here. Session data and device identifiers are recorded automatically when you load the lobby or browse game categories; this helps us keep the account stable across sessions on your mobile. Cookies used for login state and session continuity are described in the cookie section below. Data related to your Nagad or Bank Transfer transactions is retained for the period required by applicable financial compliance rules — the exact retention window depends on your jurisdiction. If you are accessing the platform from Bangladesh, your eligibility and the data rules that apply to you are governed by local law and the eligible-region terms shown during registration. We keep this policy current; the version shown on this page is the one in effect.
When you transact via Nagad, we record the reference, amount and timestamp in your account wallet history. This record is visible to you after login and is retained for the period required under applicable rules.
Bank Transfer deposits are logged against your account. We hold the reference data needed to match and confirm each transfer; these records are not shared outside the platform except where law requires.
Messages you send through our support channel are stored and linked to your account. We use them to resolve your query and to maintain a contact history you can reference in future interactions.
Your mobile device type, session tokens and browser identifiers are logged automatically. This data keeps your login stable and lets us detect unusual access patterns that might affect your account security.
This policy governs data collected directly by bdtk30 through your account, lobby sessions and support contact. It does not extend to third-party services linked from the platform, nor to payment processors that operate under their own privacy frameworks. Understanding the boundary helps you know where to direct a question — to us, or to the relevant third party.
All data collected at sign-up, login and during account management falls within this policy. This includes the email, contact number and payment method details you enter directly into your bdtk30 account fields.
Nagad and Bank Transfer activity processed through our platform is covered here. However, the internal processing rules of Nagad or your bank sit outside this policy — check their own terms for those details.
Game session data — which titles you open, how long a session runs, stake history — is recorded under this policy and visible in your account history where the game or provider exposes it.
Links to external sites, app stores or payment gateways are not covered by this policy. If you leave the bdtk30 environment, the privacy rules of that destination apply, not ours.
You have concrete options for managing the data bdtk30 holds about you. After login, your account dashboard shows your registered details, wallet history and session records — this is the first place to check if you want to review what we hold. If something is incorrect, you can update contact details directly in the account settings section; for fields that cannot be changed self-service, raise a request through our support channel and we will action it. You can also ask us what specific data we hold on your account, or request that we explain how a particular record was created. Requests related to data correction or record queries are handled through the support contact paths listed on this page. We aim to respond to data-related requests within the window required by applicable local rules — the specific timeline depends on your jurisdiction and the nature of the request.
Log in and open your account dashboard. Transaction history, registered contact details and session records are visible there without needing to contact support first.
Update your name or contact number in account settings. For fields locked to the registration process — such as linked Nagad number — contact support with your account reference and the correction needed.
If you want to know what specific data we hold or why a record exists, contact us through the support channel. Include your account reference so we can pull the correct record and respond accurately.
For deletion or portability requests where local law applies, contact us directly. We will confirm what is possible under the rules that govern your region and respond within the required window.
For any question about this policy, a data correction or a request about your account record, reach us through one of the channels below. Include your account reference in the first message so we can locate your record without back-and-forth.
Open the support widget inside your account after login. Describe your data question and include your account reference. The team will pull your record and respond within the session.
Send your data or policy query to our listed support address. Use your registered contact number or account ID in the subject line so the request is matched to the right record quickly.
Minor corrections — contact number, display name — can be handled directly in your account settings without contacting support. Check there first before raising a ticket.
Our approach to data handling covers four areas: what we store, how long we store it, who can access it and how you can request changes. Account credentials are stored with access controls in place. Session cookies are used to keep your login state stable across page loads on mobile — they expire when you log out or after an inactivity period. Retention periods for transaction data, including Nagad and Bank Transfer records, follow the minimum required by applicable rules in your region. You can request a review of what we hold at any time through the support channel.
We use session cookies to maintain your login state in the lobby. These are not used for cross-site advertising. You can clear them through your mobile browser settings at any time, though this will end your current session.
Your account is protected by login credentials you set. We do not share your password or access tokens with any third party. If you suspect unauthorised access, contact support immediately and we will review the login history on your account.
We keep your account data for the period required under the applicable rules for your region. After that window, records are removed unless a legal hold applies. Data-deletion requests are handled through the support channel.
When this policy changes in a material way, we post the updated version here and note the revision. Continuing to use your account after a change is published means you have reviewed the updated terms that apply in your eligible region.
These are the questions we receive most often about how bdtk30 handles account data, cookies and data requests. If your question is not covered here, contact support with your account reference.
We collect the name, contact number and payment details you enter at registration — for example, your Nagad number or Bank Transfer details. We also record device and session data automatically when you load the lobby. All of this is described in the details section above.
Yes. Log in and open your account dashboard — transaction history, registered details and session records are visible there. For a broader data request, contact our support team with your account reference and we will confirm what we hold.
Open account settings after login and update the field directly. For details that cannot be self-edited — such as a linked Nagad number — raise a request through live chat or email support. Include your account reference so we can match the correction to your record.
We do not sell your data. We do not share it with external marketing partners. Data may be passed to payment processors like Nagad or your bank only to the extent needed to complete a transaction, and those processors operate under their own privacy terms.
Retention periods for Nagad transfers, Bank Transfer records and account activity follow the minimum required under the rules applicable to your region. The exact window depends on local law. You can ask about your specific record through the support channel.
Some records — particularly transaction data related to Nagad or Bank Transfer activity — must be held for the period required by applicable financial rules even after account closure. We remove other data after the required retention window expires. Contact support to understand what applies to your account.
Access to the platform and the data rules that apply depend on your local law and eligible region. If you are in Bangladesh, your eligibility and any applicable data rights are governed by local rules as described during registration. Check the terms shown in your account for the version relevant to your region.