Mobile / App
kkfd3 collects only the data needed to operate your account, process wallet transactions through Nagad or Upay, and keep your session secure across devices. Access to this platform and the applicability of this policy depend on your local law and eligible regions.
When you open an account on kkfd3, we collect the information you provide during registration — your name, contact details and chosen login method. We also record transactional context: when a wallet like Nagad or Upay is used to fund or withdraw from your account, we hold the reference data needed to match that transaction to your account record. We do not store your full wallet PIN or password. Device data — browser type, operating system version and session timestamps — is logged to support continuity when you switch between a mobile browser and a desktop view. This data is not sold to third parties. We share it only where a legal obligation requires disclosure, or where a contracted service provider processes it strictly on our behalf under confidentiality terms. Retention periods apply: active account data is held while your account remains open; transactional records may be kept for a further period as required by applicable rules. The exact retention window depends on jurisdiction-specific requirements, and availability of this platform is itself subject to your local law and eligible regions. If you have questions about what data we hold, the support contact paths in this policy are the right starting point.
This policy covers data processed directly by kkfd3 in connection with your account. It does not extend to third-party services you reach through links on this site, or to payment processors whose own terms govern how they handle wallet credentials.
Login events, session tokens and device identifiers tied to your kkfd3 account fall inside this policy. We control how that data is stored, accessed and deleted on our systems.
When you use Nagad or Upay, reference data connecting the transfer to your account is covered here. The payment provider's own policy governs what they record on their side.
Browsing behaviour on kkfd3 pages — which game lobbies you visit, how long a session lasts — is covered by this policy and by our cookie notice, which you can review in your account settings area.
External links, game studios like PG Soft or Microgaming, and any payment gateway you exit to operate under their own privacy terms. We cannot control what data they collect once you leave our environment.
You have several practical options when it comes to your data on kkfd3. First, you can request a summary of the personal information we hold against your account — submit this through the support contact route listed in this policy and we will respond as our process allows. Second, if any detail in your account record is incorrect — your contact number, email address or registered name — you can update most fields directly inside your account profile page; for fields that require verification, contact support with the correction and relevant identity confirmation. Third, if you believe your data has been handled in a way that does not match this policy, raise it with us before escalating externally; we aim to resolve data queries through direct contact. Finally, in regions where local law grants it, you may request deletion of your account data, subject to any retention obligations that apply. Availability of any of these rights depends on your local law and eligible regions.
Submit a data access request through the support channel listed below. We will confirm what personal data is held on your account and provide it in a readable format within the timeframe our process allows.
Most contact details are editable inside your profile page after login. Fields that require identity verification — such as your registered name — must be corrected via support with appropriate confirmation documents.
If something in this policy is unclear, or you think your data has been used outside its stated purpose, contact us first. We treat data queries as a priority and prefer to resolve them directly before any formal escalation.
Where local law allows, you may ask for your account data to be removed. We will process this subject to any mandatory retention periods that apply in your jurisdiction.
For any privacy-related question — data access, correction requests or concerns about how your information is handled — use the contact routes published on this site. We do not accept privacy requests through social channels not listed here.
Send your data or privacy query to the support email address shown in the Contact section of this site. Include your registered account email so we can locate your record.
The live chat widget on kkfd3 is available for account and policy questions. Start a session, confirm your account identity and describe your data request so the agent can log it correctly.
The Help Centre linked in your account dashboard covers common data and privacy questions. Check there first — if your question is not answered, escalate via email or chat.
Our approach to your data is shaped by what your account actually needs to function. We do not collect data beyond what registration, wallet activity and session management require.
We use cookies to maintain your login session and remember device preferences. A cookie notice is shown on your first visit; you can review cookie settings in your account. Disabling non-essential cookies does not block account access but may affect how the lobby displays.
Your account password is stored in hashed form — we cannot read it directly. If you suspect unauthorised access, use the password-reset link on the login page immediately and then contact support to flag the incident for review.
Active account data is held while your account is open. After closure, certain transactional records — including Nagad or Upay wallet references — may be retained as required by applicable rules in your jurisdiction. We do not keep data longer than necessary.
To update, correct or request removal of your data, use the email or chat support routes listed on this site. Confirm your account identity in your first message so we can locate your record and action your request correctly.
These are the questions we receive most often about how kkfd3 handles account data, cookies, wallet records and your rights as a registered user.
We collect the name, contact details and login credentials you enter during registration. We also record device and session data to support continuity across your mobile and desktop sessions. We do not collect more than what your account needs to operate.
We store the transaction reference data that connects a Nagad or Upay transfer to your account record. We do not store your wallet PIN or full account credentials. The payment provider's own privacy policy governs how they handle the data on their side.
Yes. Submit a data access request through the support email or live chat shown on this site. Include your registered email address so we can identify your record. We will respond with a summary of the personal data held against your account.
Active account data is held while your account is open. After closure, certain records — particularly those related to wallet transactions — may be retained for a further period as required by the rules applicable in your jurisdiction. We remove data once retention obligations are met.
We do not sell your data. We share it only where a legal obligation requires disclosure or where a contracted service provider processes it on our behalf under strict confidentiality terms. Third-party sites you link to from kkfd3 operate under their own policies.
Most contact details can be updated directly on your account profile page after login. For fields that need identity verification — such as your registered name — contact support with the correction and relevant confirmation. We will update the record once verified.