Rujukan Laman

Privacy Policy for Your fofo22 Account

Your account, device, cookie, game-session and Touch 'n Go, GrabPay, Boost dan FPX payment records are covered by this Privacy Policy before you open an account with fofo22.

Account dataCookie controlsPayment recordsRequest access
fofo22 Privacy Policy for Your fofo22 Account
REQUEST CHANNELS

Contact Paths for Privacy Requests

Privacy requests are handled through account-safe channels so we can confirm that the request is really from you. Please avoid posting identity files, bank screenshots, or payment receipts in open social replies.

Live chat privacy queue Start chat from your account menu and choose privacy help. We may ask for a masked phone number, recent payment method, or account email so the agent can confirm ownership before changing data.
Email data desk Send privacy requests to the address shown inside your account area. Include your username, preferred reply channel, and the exact request, but leave out full bank numbers unless our team asks through a secure form.
Payment record checks For Touch 'n Go, GrabPay, Boost dan FPX questions, share the transaction time and reference code. We use those fields to trace records without collecting screenshots that show unrelated wallet activity.
DATA PRACTICES

Account Data Around Salon Prive BJ

We treat privacy as part of account safety, not a separate form hidden away from the lobby.

Account data we collect

When you open an account, we collect your login name, contact details, region setting, device signals, and session timestamps. These fields help us protect access, send service messages, and answer privacy requests tied to your account.

Game session records

For tables such as Salon Prive BJ, Football Studio, or Crash X, session records may include time, game ID, wager status, and device marker. We use them for account history, dispute checks, and fraud detection.

Payment data use

Your Touch 'n Go, GrabPay, Boost dan FPX references help us reconcile deposits and withdrawals. We keep only the fields needed for matching, support replies, risk checks, and record duties that apply.

Cookie choices

Cookies help keep you signed in, remember language choices, and spot unusual session activity. You can manage browser cookies, but some account functions may need session cookies to keep your access safe.

Retention periods

We keep account and payment records for as long as needed for service, dispute handling, security checks, and legal duties. When a record is no longer needed, we remove it or mask identifying fields.

Change requests

You can ask us to update contact details, access stored account data, or erase eligible records. We verify your identity first, then explain the action taken or why a record must remain.

Your Privacy Policy Questions Answered

These questions focus on how the Privacy Policy works when you hold or create an account with us. The answers explain what data we collect, why payment references matter, how cookies work, and what you can ask us to change. If your situation involves a legal restriction, our reply will follow the law that applies to the account region.

We collect the details needed to create and protect your account, such as login name, contact channel, region setting, device signals, and session activity. We also record support requests you send to us.

Payment references from Touch 'n Go, GrabPay, Boost dan FPX help us match deposits, withdrawals, and account checks. They also help support confirm a transaction without asking for extra wallet screenshots.

No. Our cookies focus on session access, language choice, account safety, and basic site performance. You can manage cookies in your browser, though some account pages may not work without session cookies.

Yes, you can ask for access to your account data through the contact paths listed here. We confirm ownership before sharing records, then provide what the law allows for your account region.

Sign in and contact support from your account area. Tell us which contact field is wrong and provide the new detail. We may send a verification step before changing email or phone records.

You can request erasure where local law permits and where the record is no longer needed for account, payment, security, or legal reasons. If we must keep a record, we will explain why.

Only team roles that need to handle the request can access it. We limit access to support, account safety, and payment checking roles, and we keep the request with your account record.