App / Slots
This page sets out exactly how 678k collects, uses and protects the information attached to your account — including the data connected to your Nagad or Upay wallet activity. Access to our platform and the scope of this policy both depend on your local law and the eligible regions where you operate.
678k collects information when you create an account, log in from your mobile, and interact with the cashier — whether you are using Nagad, Upay or another configured payment route. The information we hold includes your registered contact details, transaction references, device session data and any communication you send through our support channel. We do not sell your personal data to third parties, and we do not share transaction-level wallet data outside the scope of processing your account activity. Cookies and session tokens are used to keep your login stable across pages; you can review cookie behaviour through your device browser settings at any time. Where you have provided contact details for account verification, those details are held only for as long as your account remains active or as required under applicable local rules. This policy applies to the 678k platform as accessed through 678k. Any third-party service you reach from our pages — including external wallet interfaces for Nagad or Upay — operates under its own separate privacy terms, not ours. If you are unsure whether this policy applies in your region, check your local law and the eligible regions stated at account registration.
Transaction references tied to your Nagad deposits are held within your account record for processing and account history purposes only.
When you use Upay as a payment route, the reference data generated is kept inside your account ledger and is not passed to unrelated third parties.
Login session tokens help us keep your account stable while you move between pages on mobile. These are cleared when your session ends or when you log out.
Your registered phone number or email is used for account verification and support contact only — never shared for marketing by unrelated parties.
Not every interaction on or around 678k falls under this policy. Understanding the boundary helps you know where to direct questions and what to expect from each part of your account experience. The four areas below clarify what sits inside this policy, what sits outside it, and how to tell the difference when something is unclear.
Data collected when you log in — device type, session timestamp, account ID — falls fully inside this policy. We hold it, we are responsible for it, and you can ask us about it directly.
The transaction reference 678k receives when you complete a Nagad or Upay payment is inside our policy scope. The data held by the wallet provider itself is governed by that provider's own terms, not ours.
Game session data recorded inside your account — which titles you opened, session length — is covered here. Game content delivered by studios such as Habanero or PG Soft is subject to their own data arrangements at the infrastructure level.
Any link from 678k that takes you outside our platform leads to a service we do not control. This policy stops at our own domain. Check the privacy terms of any external service separately.
You have real, actionable options when it comes to the information we hold against your account. These are not abstract entitlements — each one has a direct path you can follow from your account dashboard or through our support channel. Reviewing your account record is the starting point: log in and open the account section to see the contact details, wallet entries and session history we hold. If any detail is wrong — a phone number, a registered name, a linked contact — you can request a correction by reaching support directly. For questions about what data we hold or how long we keep it, our support team can give you a specific answer tied to your account, not a generic one. If you want to request that we remove your data, you can raise that through the same support path; we will confirm what can be actioned under applicable local rules.
Log in and open the account section to see which details we hold — contact info, payment references and session history are all visible or available on request.
If your registered phone number or contact detail is incorrect, raise a correction request through our support channel and we will verify and update it.
Send a specific question about retention, data use or wallet references to support. We will respond with an answer tied to your actual account, not a form letter.
You may request removal of your account data through support. We will confirm what is actionable under applicable local law and the eligible region rules that apply to your account.
If something in this policy is unclear, or if you want to act on any of the rights described above, our support channel is the right place to start. State your account reference and the specific question — we will route it to the right person rather than giving you a generic reply.
Open a support request from inside your account dashboard. Include your registered contact detail and describe the privacy question or correction you need.
If you cannot log in, you can reach us by email using the address shown on the Contact page. Include the account email or phone number you registered with.
We acknowledge privacy-related requests and follow up with a specific answer. If a request requires more time — for example, a data removal under local rules — we will let you know the next step.
678k applies access controls to limit who inside our operation can view account-level data. Session tokens are short-lived and tied to your active login — they do not persist after you close the session. Retention of your personal data continues only while your account is active or while there is a legitimate reason under applicable local rules to keep it. Once that reason ends, data is removed from active records. Cookie settings on your device browser let you manage how session data is stored on your end; removing cookies will end your active session and require a fresh login next time you open 678k.
Internal access to account-level personal data is restricted. Not everyone in our operation can view your records — access is limited to the functions that require it for your account to work.
Session cookies keep your login stable across pages during an active visit. They expire when you log out or close the session. You can manage cookie storage through your device browser settings.
We hold your data while your account is active. When an account closes or a retention reason ends under local rules, personal data is removed from active records on a set schedule.
To update, query or request removal of your data, contact support with your account reference. We confirm the outcome in writing and note any steps that depend on local law.
The questions below cover what we get asked most about this policy — from how wallet data is handled to what you can do if you want your information updated or removed. If your question is not here, support can answer it directly.
We store the transaction reference generated when your Nagad or Upay payment is processed through your account. This is held inside your account ledger for account history purposes. The wallet provider holds its own data under its own separate privacy terms, which are outside our policy.
Access to your personal data inside 678k is restricted to the functions that need it to operate your account — such as account verification and support. We do not give general internal access to account-level personal records, and we do not sell or share your data with unrelated third parties.
Log in and open the account section to check your current contact details. If something needs correcting — a phone number or email — raise the request through our support channel with your account reference. Support will verify and update it after confirming your identity.
We keep your data while your account is active. When an account is closed or a retention reason ends under applicable local rules, personal data is removed from active records. You can ask support for the specific retention position that applies to your account and region.
Game session references recorded inside your 678k account are covered by this policy. At the infrastructure level, studios such as Habanero and PG Soft operate under their own data arrangements. We record that you opened a session and its duration; detailed game-engine data is held at the studio level, not inside your 678k account record.
This policy applies to your use of 678k. Access to the platform and the scope of data processing both depend on your local law and the eligible regions stated at account registration. If you are unsure whether this policy covers your situation, check your local law before using the platform.