3666dat Privacy Policy: How We Handle Your Account Data
At 3666dat, we are clear about what personal data we collect from your account, how we use it, and who can access it. This policy applies to every account holder in Bangladesh and eligible regions — your right to know what we hold starts here.
Account data protected
bKash & Upay transaction records
No third-party data sale
Your access rights explained
POLICY POSTURE
What Data We Collect and Why We Hold It
When you open an account with 3666dat, we collect the information needed to verify your identity, process your payments and keep your account secure. This includes your name, contact details, and the payment method you register — whether that is bKash, Upay, or Bank Transfer. Each time you make a deposit or withdrawal through bKash or Upay, a transaction record is created and stored against your account. We keep these records to resolve disputes, respond to account queries and comply with the obligations that apply to us in the regions where we operate. We also collect technical data such as your device type, browser session and IP address when you access the platform. This data helps us detect unusual login attempts and keep your account from being accessed without your knowledge. We do not sell your personal data to third parties. Where we share data with a service partner — for example, a payment processor handling your bKash or Bank Transfer transaction — we do so only under a data-handling agreement that limits how that partner may use your information. Your account data is retained for as long as your account remains active and for a further period required by applicable law. Availability of this service depends on your local law and eligible region.
bKash transaction records
Upay payment history
Bank Transfer logs
Account login records
Device session data
POLICY SCOPE
Where This Policy Applies and What It Covers
This policy covers data collected through the 3666dat platform directly. It does not extend to third-party sites or services you reach by following a link away from our platform. Below is a plain breakdown of what falls inside and outside this policy's scope, so you know exactly where our obligations begin and end.
Account Access
All data collected when you register, log in or update your account details on the 3666dat platform falls within this policy. This includes the email address, phone number and payment method you provide during account setup.
Payment Transactions
Deposit and withdrawal records processed through bKash, Upay and Bank Transfer are covered by this policy. The payment processor handling the transaction operates under its own terms, which we cannot control once data leaves our platform.
Site Content and Cookies
We use cookies and session data to keep you logged in and to remember your display settings. This data is covered by this policy. You can manage cookie preferences through your browser settings at any time.
Third-Party Services
External links, payment gateways outside our direct control and any third-party platform you navigate to independently are not covered by this policy. We encourage you to read the privacy terms of any external service before sharing your information there.
YOUR RIGHTS
Practical Steps You Can Take Under This Policy
You have concrete actions available to you regarding the data 3666dat holds on your account. These are not abstract rights buried in legal text — they are steps you can take through your account or by contacting support directly. If you want to review the personal details we hold, log into your account and open the account settings section; the profile fields there show the current information stored against your account. Transaction records linked to your bKash or Upay deposits are visible in the transaction history tab. If any stored detail is incorrect — for example, your registered phone number or Bank Transfer account name — you can submit a correction request through the support channel. We aim to process corrections promptly, though the time required depends on what verification is needed. You may also ask us what data we hold and why, and request that data no longer needed for legal or account purposes be removed. These requests are reviewed individually and subject to the obligations that apply in your eligible region.
Review Your Records
Log into your account and navigate to account settings to see the personal details and payment methods currently stored. Transaction records for bKash and Upay deposits appear in the transaction history tab.
Correct Account Details
If a stored detail is wrong — name, phone number or registered Bank Transfer account — raise a correction request through our support channel. Verification steps shown in your account apply before any change is confirmed.
Ask What We Hold
You may contact us to ask what personal data we hold and the reason we hold it. We will respond through the same channel you use to contact us, subject to identity verification matching your account.
Request Data Removal
Where data is no longer required for legal or account purposes, you may request its removal. Requests are assessed individually; some records must be retained under applicable law regardless of a removal request.
REACH OUR TEAM
How to Contact Us About This Policy
If you have a question about this privacy policy, want to exercise a data right or need to report a concern about how your information is handled, you can reach the 3666dat support team through the channels below. We aim to respond to data-related queries with the same priority as account support queries.
Live Chat
Open the live chat from your account dashboard to speak with the support team about a data query or correction request. Available when you are logged in.
Email Support
Send a detailed message about your privacy concern or data request to our support email address. Include your registered account email or bKash number so we can locate your record.
Account Help Centre
The Help Centre inside your account lists the steps for common data requests — including how to update a Bank Transfer detail or download a transaction record — without needing to contact the team directly.
HOW WE PROTECT DATA
Data Handling, Cookies, Security and Retention at 3666dat
We have built the account and payment infrastructure around a few clear data-handling principles. Data collected at login or during a bKash deposit is stored on servers with access controls that limit which systems and staff can reach it. We do not retain payment credentials such as bKash PINs or Bank Transfer passwords — those are handled entirely by the payment processor, not stored on our side. Cookies set during your session are used for session management and platform performance; they are not used to track you across unrelated websites. Your account data is retained for as long as your account is active, plus the retention period required by applicable law in your eligible region. If you close your account, we will retain only what is legally required and remove the rest in line with our internal data schedule.
Access Controls
Account data is stored behind access controls that restrict which internal systems and staff can retrieve it. Payment credentials from bKash, Upay and Bank Transfer transactions are handled by the payment processor, not stored in your account profile.
Cookie Use
Session cookies keep you logged in while you navigate your account. We do not use cookies to track your activity on other websites. You can clear or block cookies through your browser settings; doing so may affect how your account session behaves.
Data Retention
We hold your account data for the duration your account is active and for the additional period required under applicable law. When you close your account, data no longer required for legal purposes is removed on a scheduled basis.
Policy Updates
When this policy changes, the updated version is posted here with a revision date. Continued use of your account after a change is posted means you have had the opportunity to review the updated terms.
POLICY QUESTIONS
Frequently Asked Questions About This Privacy Policy
These are the questions we hear most often from account holders in Bangladesh about how their data is handled, what we store and how to act on their rights under this policy.
What personal data does 3666dat collect when I open an account?
We collect the details you enter during registration — your name, email address, phone number and the payment method you add, such as bKash or Bank Transfer. We also collect technical session data like your device type and IP address each time you log in.
Does 3666dat store my bKash PIN or Bank Transfer password?
No. Payment credentials like your bKash PIN or Bank Transfer login are handled entirely by the payment processor. We receive a confirmation of the transaction result, not your credential. Your PIN and passwords are never stored in your 3666dat account.
Can I see all the data 3666dat holds on my account?
Yes. Log into your account and open account settings to view your stored profile details. Your bKash, Upay and Bank Transfer transaction history is visible in the transaction history tab. For a full data summary, contact support with a written request.
How do I correct a mistake in my information?
Raise a correction request through live chat or email support. Include the field you need corrected and the correct value. We will ask you to complete the verification steps shown in your account before any change is applied, to confirm you are the account holder.
Does 3666dat share my data with third parties?
We share data only with service partners directly needed to operate your account — for example, a payment processor handling your Upay or Bank Transfer transaction. Sharing happens under a data-handling agreement. We do not sell personal data to marketing companies or unrelated third parties.
What happens to my data if I close my account?
When you close your account, we remove personal data that is no longer required. Some records — particularly transaction logs linked to bKash or Bank Transfer activity — must be retained for the period required by applicable law in your eligible region, then removed on schedule.