111bdtf Privacy Policy: How We Handle Your Information
At 111bdtf, we are direct about what data we collect, why we collect it, and how you can control it. This policy covers every part of your account experience — from the moment you register through every transaction record tied to your bKash, Nagad or Bank Transfer activity — and access to our platform depends on your local law and eligible region.
Account data protection
Transaction record access
bKash & Nagad context
Your correction rights
POLICY SCOPE DETAIL
What This Privacy Policy Covers at 111bdtf
This policy applies to all information collected when you open an account, navigate our lobby, or initiate a payment through bKash, Nagad, Rocket or Bank Transfer. We collect the details you provide at registration — your name, contact information and preferred payment method — along with session and device data generated during your visits. Transaction records associated with your wallet activity are stored in your account history and are accessible to you through the account dashboard. We do not sell your personal information to third parties. Data shared with payment processors — including bKash and Nagad — is limited to what those services require to complete a transaction you have authorised. We retain account data for as long as your account remains active and for the period required under applicable rules in the regions where we operate. If your account is closed, we follow a defined retention schedule before deletion. Eligibility to use 111bdtf depends on your local law and the regions we currently serve. Nothing in this policy creates a legal right to access where local law restricts it. For questions about what data we hold for your account specifically, contact us through the published support route listed on the support page.
bKash payment data
Nagad transaction logs
Bank Transfer records
Account registration fields
Session and device signals
INSIDE VS OUTSIDE
Where This Policy Applies and What It Does Not Cover
This policy draws a clear line between what 111bdtf controls and what sits outside our responsibility. Understanding that boundary helps you know exactly who to contact when a data question arises — whether it concerns your account, a payment, our site content, or a third-party link.
Account Access Data
Login records, session tokens and device identifiers generated when you access your 111bdtf account are covered by this policy. We control how these are stored, how long they are retained and who within our team can view them.
Payment Transactions
When you use bKash, Nagad, Rocket or Bank Transfer, the data you enter on our payment screens is covered here. Once a transaction leaves our system to reach the payment provider, that provider's own privacy terms govern the data in transit.
Site Content and Cookies
The cookies and analytics we use to understand how you navigate our lobby — which categories you visit, which pages load — are part of this policy. You can review cookie settings in your browser. We do not use tracking that follows you outside our domain.
Third-Party Services
Links to third-party sites, payment apps like bKash or Nagad's own platforms, and any external service you reach from our pages operate under their own policies. We do not control those policies and are not responsible for how those services handle your data.
YOUR PRACTICAL RIGHTS
Actions You Can Take Under This Policy
You have concrete steps available to manage your personal data — not just abstract rights. Your account dashboard shows the registration details we hold, including the contact information and preferred payment method you submitted. If anything looks incorrect, you can update it directly from the account settings page without contacting support first. For records you cannot edit yourself — such as historical transaction logs linked to your bKash or Nagad activity — you can raise a correction request through our published support route. We will review the record and respond through the same channel. If you want to know exactly what data we hold for your account, you can submit a data inquiry by contacting us via the support email listed on our contact page. We will acknowledge your inquiry and provide a summary of the data categories we store for your account. Closure requests are also handled through support; we will confirm the retention period that applies before deletion proceeds.
Review Your Records
Open the account dashboard to see the registration details and transaction history we hold. This is the fastest way to check what data is associated with your account without involving support.
Correct Account Details
Update your contact details and payment method preference directly in account settings. For fields locked after verification, submit a correction request through our support email and we will process it.
Raise a Data Inquiry
If you want a summary of every data category we store for your account, contact us through the published support email. We will respond with the relevant details for your account specifically, not a generic list.
Request Account Closure
Submit a closure request through support. We will confirm the retention schedule — how long your transaction records remain on file after closure — before we begin the deletion process.
REACH OUR TEAM
How to Contact Us About This Policy
If you have a question about this privacy policy, a data correction request or a concern about how your information is handled, use only the contact routes published on our site. We do not accept privacy requests through social media or unverified channels.
Support Email
Send your privacy inquiry or data correction request to the support email address listed on our Contact page. Include your registered account identifier so we can locate your record without delay.
Live Chat
The live chat widget on the site connects you to our support team during published operating hours. Use this route for immediate questions about your account data or to start a correction request in real time.
Account Help Centre
The Help Centre in your signed-in account area contains articles about data settings, cookie preferences and how to read your transaction history. Start here if your question relates to what is visible in your account.
HOW WE PROTECT DATA
Our Approach to Data Handling and Account Security
Every data handling practice described in this policy is applied consistently across your account — from the registration fields you fill in on day one to the transaction records generated each time you use bKash, Nagad or Bank Transfer. We do not make exceptions for specific payment methods or account types.
Cookies and Tracking
We use session cookies to keep your account active while you navigate the lobby and analytics cookies to understand which pages are visited most. We do not use cookies that track your activity across third-party sites. You can clear or block cookies in your browser settings at any time.
Account Security Measures
Access to your account data is controlled by the login credentials you set. We apply standard security practices to protect stored data. If you notice any unauthorised activity on your account, contact support immediately through the published email or live chat route.
Data Retention Schedule
We keep your account data for as long as the account is active and for any additional period required under applicable rules in the regions we serve. After account closure, transaction records are retained on a defined schedule before deletion — the exact period is confirmed when you submit a closure request.
Policy Update Process
When this policy changes, we post the updated version on this page with a revised effective date at the top. Continued use of your account after a posted update means you have seen the revised terms. We do not send personalised notifications for routine updates.
POLICY FAQ
Common Questions About Privacy at 111bdtf
These questions cover the data topics we hear about most — account records, payment data, cookies, correction requests and what happens when you close your account. If your question is not answered here, the support routes listed above are the right next step.
What personal data does 111bdtf collect when I register?
We collect the details you enter on the registration form — your name, contact information and the payment method you choose, such as bKash or Nagad. We also collect session and device data automatically when you access the site. We do not collect more than what is needed to operate your account.
Does 111bdtf share my data with bKash or Nagad when I make a payment?
When you initiate a payment through bKash, Nagad, Rocket or Bank Transfer, we share only the information those payment services require to process the transaction you authorised. We do not share your full account profile with payment processors — only the transaction-relevant fields.
How do I correct information in my account that looks wrong?
Open account settings to update your contact details or preferred payment method directly. For locked fields — such as the name or ID used at registration — contact us through the published support email with your account identifier and the correction you need. We will review and respond through the same channel.
Can I request a full list of the data 111bdtf holds for my account?
Yes. Send a data inquiry to the support email listed on our Contact page. Include your registered account identifier. We will provide a summary of the data categories we store for your account. We do not send generic responses — the summary will relate to your account specifically.
How long does 111bdtf keep my data after I close my account?
After you submit a closure request, we apply a retention schedule required under applicable rules in the regions we operate. The exact period is confirmed when we acknowledge your closure request. Transaction records linked to bKash or Bank Transfer activity are included in this retention period before deletion.
Does using 111bdtf on mobile change how my data is collected?
Accessing our site through a mobile browser generates the same categories of session and device data as desktop access. No additional data is collected because you are on a mobile device. Cookie settings can still be managed from your mobile browser the same way they are on desktop.