Casino / Live
668tk collects and uses your personal data only for account operation, transaction processing and support. This policy explains what we collect, why we collect it and how you can review or correct your records — access and eligibility depend on your local law and eligible region.
When you open an account with 668tk, we collect the details you submit during registration: your name, contact address, login credentials and any identity verification documents we are required to hold. When you fund your account using Nagad, Upay or Bank Transfer, we record the transaction reference, amount and wallet identifier linked to that payment — we do not store full payment credentials ourselves. We also collect device and session data automatically: browser type, IP address, pages visited and time on site. This helps us detect unusual login attempts and keep your account secure. We do not sell your personal data to third parties for their own marketing purposes. Data is shared only with payment processors handling your Nagad, Upay or Bank Transfer instruction, identity verification partners where required, and regulatory bodies where disclosure is legally compelled. Retention periods follow applicable data-handling obligations; you can ask us what period applies to your account type by writing to our support route. Your use of this site is subject to local law and eligibility in your region.
This policy covers your personal data handled directly by 668tk across account access, deposits, withdrawals and support interactions. It does not extend to third-party sites linked from our pages, payment provider privacy practices, or studio content platforms operated independently. Understand what falls inside and outside its scope before proceeding.
All personal data you submit when creating or updating your 668tk account — name, contact detail, password and identity document — falls inside this policy. We process this data to operate your account and verify your identity as required.
Payment references generated when you use Nagad, Upay or Bank Transfer are logged under this policy for fraud prevention and account reconciliation. We do not hold full wallet credentials; the payment provider handles those under their own terms.
Browsing behaviour on 668tk pages — game lobbies, deposit pages, support pages — is captured via session cookies. This helps us improve navigation and detect access issues. Cookie preferences can be adjusted in your browser settings.
Links to external payment gateways, studio platforms or verification partners take you outside 668tk. Their data practices are governed by their own policies. We encourage you to read those separately before submitting data to any third-party service.
You have several practical actions available to you regarding the personal data we hold. First, you can request a summary of the data linked to your account — this includes registration details, transaction records tied to your Nagad, Upay or Bank Transfer history, and any identity documents we hold. Second, if you notice an error in your account details, you can correct most fields directly from the account settings page; for fields locked after verification, contact support and we will process the correction. Third, if you want to raise a question about how a specific data point is being used, write to our support route with your account reference and the specific concern. We will respond through the same channel. Finally, if you wish to request deletion of data we are not legally required to retain, submit that request via email support with your account ID. Eligibility for deletion requests depends on your account status, outstanding transaction obligations and applicable local data-handling law in your region.
Request a summary of the personal data tied to your account — registration fields, transaction references and any verification documents we hold — by contacting support with your account ID.
Most contact and profile fields can be updated directly in account settings. Verified identity fields require a support request. Include your account reference so we can locate and update the correct record.
If a specific use of your data is unclear, write to support with your account reference and a description of the concern. We will respond via the same channel you used to contact us.
Where we are not legally required to retain data, you may request deletion by email. Your account status and any outstanding obligations affect whether a deletion request can be fulfilled immediately or must be deferred.
If you have a question about how your data is used, want to request a record summary or need to raise a correction, these are the contact routes available. Use the channel that matches your query type — account-specific queries move faster when you include your account ID in the first message. Availability of each channel depends on published site hours.
Send your data query, correction request or deletion request to our email support address shown on the site. Include your account ID and a clear description of your request so we can locate the correct records quickly.
For general privacy questions — what data we collect, how cookies work, where transaction references are stored — the live chat route on the site is the fastest path. Have your account ID ready if the question relates to your specific records.
The Help Centre section of the site contains published answers to common data and account questions. Check there first for cookie settings, account data summaries and how to locate your Nagad or Bank Transfer transaction reference in your account history.
Our approach to data handling is built around the minimum necessary for account operation and payment processing. We do not retain data longer than applicable obligations require, and we do not share it with unrelated commercial parties. If you want to know the specific retention period for your account type, ask via the email support route with your account reference.
We use session cookies to keep your login active and to understand how pages are navigated. You can block or clear cookies in your browser settings; doing so may affect how your account session behaves. We do not use cookies to track you across unrelated third-party sites.
Login credentials are stored using standard hashing; we do not hold plain-text passwords. If you suspect your account has been accessed without your permission, change your password immediately from account settings and contact support through the live chat or email route.
Transaction records — including Nagad, Upay and Bank Transfer references — are retained for the period required by applicable financial and data-handling obligations. When that period ends, records are deleted or anonymised. Your account registration data follows a separate retention schedule tied to account status.
When we make a material change to this policy, we post a notice on the site and update the effective date at the top of the policy page. Continued use of your account after a posted update means you have read the revised terms. Check this page periodically to stay current.
These are the questions we receive most often about data collection, account records and your rights under this policy. Each answer refers specifically to how 668tk operates — not general legal commentary. Access and eligibility depend on local law and your eligible region.
We collect the registration details you submit — name, contact address and login credentials — plus any identity verification documents required at that stage. Device and session data is also captured automatically when you browse the site. We collect only what is needed to operate your account.
We log the transaction reference and wallet identifier associated with each Nagad, Upay or Bank Transfer instruction for reconciliation and fraud prevention. We do not store full wallet credentials. Those are handled directly by the payment processor under their own data terms.
Contact us via email support with your account ID and a request for a data summary. We will identify the records held against your account — registration data, transaction references and any verification documents — and share a summary through the same channel.
Most profile and contact fields can be edited directly in your account settings page. Fields that were locked during identity verification require a support request. Write to us with your account reference, identify the field and provide the correct information for us to update.
Transaction records are retained for the period required by applicable financial and data-handling obligations. When that period expires, records are deleted or anonymised. If you want to know the specific period for your account type, ask via the email support route with your account ID included.
Send your concern to email support with your account reference and a clear description of the data point in question. For general cookie and session queries, live chat is available on the site. The Help Centre also covers common data questions without needing to contact support directly.