Rujukan Laman

Privacy Policy for Your Malaysia Account

Our Privacy Policy maps the account data needed to open your soju88 wallet, keep access secure, and record payment context for Touch 'n Go, GrabPay, Boost dan FPX.

Malaysia data useCookie choicesTouch 'n Go contextAccount access requests
soju88 Privacy Policy for Your Malaysia Account
CONTACT PATHS

Privacy Help Channels You Can Use

You can contact us about this Privacy Policy before opening an account, after joining, or when you want a change made to stored data. To keep your request safe, we may ask for account details, recent wallet context, or device clues before we act. We will not ask for your payment app password, bank password, or one-time code.

Team online

Chat privacy team

Use live chat when you need a quick privacy answer about account data, cookie settings, or a recent access alert. Our team may ask for your username and a short description before checking internal records.

Email data request

Send an email when you need a copy, correction, or deletion request recorded in writing. Include the email tied to your account, the request type, and any payment reference needed to locate the record.

Wallet record check

If your privacy question involves Touch 'n Go, GrabPay, Boost dan FPX records, share the method name, date, and reference number. We use those details only to match the wallet event to your account.

ACCOUNT SAFEGUARDS

Data Care Across Account Activity

Our privacy work sits inside the account flow, not outside it. When you log in, browse games such as Control Squeeze or Dragon Hatch, or move funds through…

Data collection

We collect account details, contact data, device signals, session records, and wallet references that help us run your account.

Cookie choices

Cookies help remember your session, language choice, and basic site preferences.

Login protection

We may check device type, IP range, failed login attempts, and session changes to spot unusual access.

Payment privacy

For Touch 'n Go, GrabPay, Boost dan FPX, we store payment context such as method, amount status, reference, and time.

Retention period

We keep records while they are needed for account operation, disputes, audit checks, security work, or legal duties.

Change requests

You can ask us to correct account data, update contact details, or review stored records tied to your account.

Privacy Questions Before You Join

These answers explain the privacy points we get asked about most often before you open an account or manage an existing one. They focus on data use, access rights, cookies, payment context, and how to reach us. If your situation is specific, contact us with account details we can verify.

We collect details needed to create and protect your account, such as contact data, login records, device signals, and wallet references. We use them for access checks, support replies, security work, and legal record duties.

Yes, you can ask us for a copy of data tied to your account. We may verify your identity first, then prepare the record we can share under applicable law and account security rules.

Cookies help keep your session active, remember preferences, and measure basic site performance. You can control many cookies through your browser, though account login and wallet checks may need certain session cookies to work.

No. We may store transaction context such as method name, status, time, and reference, but we do not store your Touch 'n Go, GrabPay, Boost, FPX, bank, or payment app password.

We keep account and wallet records while they are needed for service operation, dispute checks, security work, audit needs, or legal duties. After that, we delete them or make them anonymous where practical.

Access is limited to team roles that need the data for account service, wallet checks, security review, or privacy response. Staff access is handled through internal controls and is not open to every team member.

Contact us by chat or email with the account detail that needs correction. We may ask for proof of account ownership before updating stored data, so your request cannot be used by another person.