Reference

Your Privacy, Explained Plainly

We collect only what's needed to run your account — login details, device data and payment references from bKash, Nagad or Rocket — and we don't sell it to third parties.

Data minimisationPayment reference privacyCookie controlsAccount-level security
Wicket 72 Your Privacy, Explained Plainly
PRIVACY SUPPORT PATHS

Questions About Your Data? Ask Us

If something in this policy isn't clear, or you want a copy of the data we hold on your account, our support team handles those requests directly. Reach out through live chat inside your account dashboard for a quicker reply, or send a written request if you need a formal data-access confirmation. We verify your identity before releasing any account details, the same way we verify a withdrawal — so have your registered mobile number and account email ready when you contact us.

Live Chat Open live chat from your account dashboard on mobile or desktop to ask about data storage, cookie settings or how your bKash, Nagad or Rocket references are used.
Email Request Send a written request for a copy of your account data or to ask us to correct a detail — we confirm your identity against your registered mobile number first.
Account Settings Manage cookie preferences and review what device and login data is tied to your profile directly from the account settings page, no support ticket needed.
HOW WE PROTECT DATA

Data Handling, Cookies And Retention

Keeping your account data tied only to you starts with how we verify logins and store payment references. We use device fingerprinting and OTP checks so a login from a new phone triggers extra verification, not just a password prompt. Cookies remember your session and lobby preferences — they don't track you across other sites. Transaction records tied to bKash, Nagad or Rocket are kept only as long as support or regional legal obligations require, and you can ask us to check what's stored on your profile at any point.

Login Verification

Every login is checked against your registered device and mobile number; a new device triggers an OTP step before your account or wallet history becomes visible.

Cookie Use

Cookies keep you logged in between app and browser sessions and remember lobby preferences like your last-opened game; they aren't sold or shared for outside advertising.

Data Retention

We hold account and transaction records only as long as needed for support queries, dispute checks or obligations under your local regulation, then the record is retired.

Your Access Rights

You can request a copy of your stored data, ask for a correction, or close your account record entirely by contacting support with your registered details.

Frequently Asked About Your Data

Here are the questions we hear most often about how Wicket 72 handles account data, cookies and payment references. If your question isn't covered here, our support channels above can walk through the specifics with you directly, based on your registered account.

We collect your registration details, device data and transaction references linked to bKash, Nagad or Rocket deposits. We don't collect your wallet PIN or full card credentials at any point.

No. Payment references stay inside our verification system and aren't passed to outside marketing partners. We only share data where required by law in your region or to confirm a transaction.

We retain records only for as long as needed for account support, dispute checks or legal obligations that apply where you're located. After that period, the record is retired from active use.

Yes. Contact our support team with your registered mobile number and we'll check, correct or close your account record, subject to any retention rules under your local law.

Yes, cookies keep your session active between login attempts and remember lobby preferences like your last game or table. They don't track your activity across other unrelated websites.

Yes. Your account is tied to one verified profile, so switching between the app on your phone and a desktop browser doesn't create separate, unsynced data records.
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.