Reference

How fk33 Handles Your Account and Payment Data

This page sets out what account, device and transaction data fk33 collects when you register, deposit through bKash, Nagad or Rocket, or open tables like Football Derby Live and Crash Betboost.

Account DataWallet RecordsDevice LogsCookie ControlsSupport Access
fk33 How fk33 Handles Your Account and Payment Data
REACH OUR TEAM

Contact Paths for Privacy Questions

Questions about your data don't need to wait for a formal letter. We've built three ways to reach us directly from your account, each tied to the same support record so nothing gets lost between channels or repeated back to you twice.

Live Chat Support Open live chat from your account dashboard to ask what personal data fk33 holds against your profile, or to request a correction to your registered mobile number or wallet details.
Email Requests Send a written request if you want a copy of your account data or you'd like us to remove browsing logs tied to a closed wallet; we'll confirm receipt and outline next steps.
In-App Help Desk Use the help desk inside the fk33 mobile view to flag a privacy concern directly from the same screen where you manage your bKash, Nagad or Rocket deposits.
HOW WE PROTECT DATA

Data Handling Behind Every fk33 Account

Protecting your account isn't a single setting — it's a handful of practices working together. From how we lock down wallet references to how long we hold onto a login record, here's what actually happens behind your fk33 account once you're signed in.

Encrypted Wallet Records

Every bKash, Nagad and Rocket transaction reference is stored behind encrypted account layers on our servers, kept separate from your everyday browsing history across the lobby.

Cookie Controls

Cookies track your session and game preferences, like whether you favour Crash Betboost or Slot Starfire, so pages load faster; you can clear them from your browser settings anytime.

Retention Windows

We keep transaction and login records only as long as needed for account verification and dispute resolution, then archive or remove them under the policy in force for your region.

Account Security Checks

Two-step verification and OTP confirmation on login limit access to your account, and we review flagged devices before allowing a fresh bKash, Nagad or Rocket withdrawal request.

Common Questions About Your Data on fk33

Here are the questions we hear most often about how fk33 handles your account and payment information, answered directly without the legal boilerplate.

We collect your mobile number, the device and browser you sign in from, and wallet references from bKash, Nagad or Rocket used to fund your account, along with transaction history for verification.

No. Your wallet PIN stays inside the bKash, Nagad or Rocket app and is never sent to or stored on fk33 servers; we only see the transaction reference confirming a deposit.

Yes, contact support through live chat or email and we'll tell you what account, device and payment records are linked to your profile, subject to identity confirmation.

Transaction and login data is kept only as long as needed for account verification and dispute handling, then archived or removed according to the rules for your region.

We share only what's necessary with bKash, Nagad and Rocket to process a deposit or confirm a withdrawal; we don't pass your details to unrelated third parties.

Data handling follows your local law and eligible region, so specific rights and processes can vary depending on where you're accessing the account from.
Reference

Privacy Policy

Service availability depends on eligible regions and local law. Users should check local rules before opening an account.

Access may be available only where local law permits.