Reference

How 588fd Handles Your Personal Information

This Privacy Policy sets out exactly what data 588fd collects when you open an account, make a deposit via bKash, Nagad or Rocket, and use the platform — and how we keep that data secure.

Account data protectionbKash, Nagad, Rocket payment privacyCookie and session controlYour right to access or delete data
588fd How 588fd Handles Your Personal Information
REACH OUR PRIVACY TEAM

Contact Us About Your Privacy Rights

If you want to access, correct or remove the personal data we hold on your account — including payment records linked to bKash, Nagad or Rocket — reach out through any of the channels below. We aim to respond to all data-related requests within a reasonable period. The channel you use does not affect how your request is handled.

Live Chat Start a live chat session from your account dashboard. Describe your data request clearly and our support team will log and escalate it to the right person.
Email Support Send your data request to our support email address listed in your account settings. Include your registered mobile number so we can verify your identity quickly.
Account Help Centre Open the Help section inside your account, select Privacy and Data, and submit a request form directly. Responses are tracked against your account record.
DATA HANDLING PRACTICES

How We Protect and Manage Your Information

We use SSL encryption across the platform so data moving between your device and 588fd — including wallet details from bKash, Nagad or Rocket — cannot be read in transit. Account security relies on OTP verification at login, which means a code sent to your registered mobile number confirms it is really you. We do not share your data with advertisers. Below are four specific ways we handle data responsibly.

Payment Data Isolation

bKash, Nagad and Rocket transaction references are stored separately from your gameplay history. Payment processors only receive the minimum details needed to complete or reverse a transfer.

Cookie Controls

We use session cookies to keep you logged in and analytics cookies to see how pages load on mobile. You can adjust cookie preferences from the settings panel inside your account.

Account Security Layer

Every login triggers an OTP to your registered number. If you notice a login you did not make, contact support immediately and we will freeze account access while we investigate.

Data Retention and Deletion

We hold your account data while your account is open. After account closure, data is retained only for the period required by applicable rules, then permanently removed from active systems.

Frequently Asked Privacy Questions

Below are the questions we hear most often about data, account privacy and how your payment details are handled on 588fd. If your question is not here, use the contact options in the support section above.

We collect your name, registered mobile number and the wallet identifier you link for bKash, Nagad or Rocket. We also log your device type, IP address and session activity for security verification.

No. We never store your mobile wallet PIN or full banking credentials. Payment references are recorded to match deposits and withdrawals to your account, but authentication stays within your wallet app.

Yes. Submit a data access request through live chat, email or the in-account Help Centre. We will verify your identity using your registered number and send your data within a reasonable timeframe.

Contact support via any channel listed on this page, state you want your data removed, and we will process the request. Some data may be retained for a period as required by applicable rules before full deletion.

We do not sell or share your data with advertisers. Data is shared with payment processors like bKash, Nagad and Rocket only to complete your transaction, and limited to what each processor needs.

Yes. The data rights available to you and the rules that apply to how we handle your information depend on your local law and the eligible region from which you access 588fd.
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.