Rujukan Laman

How sar288 Handles Your Privacy

Clear privacy choices, Malaysia payment context and account-data access sit in one sar288 policy, so you know what we collect before you open an account.

Malaysia data useCookie controlsAccount requestsPayment context
Explore Lobby Read FAQ
sar288 How sar288 Handles Your Privacy
CONTACT PATHS

Three Ways to Ask About Privacy

Privacy questions should reach the team that can actually read your account record and answer with context.

Live chat privacy request Open chat from your account and ask for the privacy queue.
Email data request Send a clear request from the email linked to your account.
Account security concern If you suspect account access that was not yours, contact us quickly.
ACCOUNT SAFETY

Six Data Controls You Can Use

We handle privacy through practical controls inside the account flow, not long wording alone. The policy connects each data type with a purpose, a retention reason and a contact path.

Data minimisation

We ask for the details needed to create your account, keep wallet records aligned and answer support cases. If a field is optional, we mark it clearly before you send it.

Cookie choices

Cookies help keep sessions active, remember language choices and detect unusual access patterns. Where settings are available, you can change browser controls, but some account and security cookies must remain for sign-in.

Login protection

We use device signals, session records and account verification to spot access that does not match your normal pattern. These checks support privacy by limiting unauthorised viewing or wallet changes.

Retention periods

We keep data only for account operation, legal record duties, dispute handling and security checks. After the reason ends, records are deleted, anonymised or kept in restricted form if required.

Payment data context

Touch 'n Go, GrabPay, Boost dan FPX references are used to match deposits, withdrawals and support enquiries. We do not ask you to send private payment passwords through chat.

Request handling

When you ask to access, correct or delete data where permitted, we verify your identity first. This prevents another person from using a privacy request to view or alter your account details.

Privacy Questions Before You Join

These answers explain how the Privacy Policy applies before and after you open an account. They focus on data collection, access requests, cookies, payment references, security checks and contact paths. If your request depends on Malaysian law or your account status, our support team will explain the next step after verifying you.

We collect details needed to set up and protect your account, such as name, contact details, login records, device signals and wallet references. Extra checks may apply before withdrawals or account changes.

Payment references help us match your wallet activity with the correct transaction and answer support questions. They are used for account records, verification, dispute checks and legal duties where applicable.

Yes, you can ask for access to your personal data. We verify your identity first, then explain what can be shared, the format available and any limits required by law.

Contact support from your account or linked email and state which detail needs correction. We may request proof before changing identity, contact or payment-linked records to avoid unauthorised edits.

Cookies and similar tools help keep your session active, remember settings and flag unusual access. Some are needed for account security, while browser controls may let you reduce other cookie use.

You can request deletion where local law and your account status allow it. Some records may need to remain for security, transaction evidence, dispute handling or legal record duties.

Use live chat or email from your account details and mention privacy in the request. We will verify you, route the case to the right team and respond with the next steps.

Related Pages

Kingdoms Rise Safari Wilds sar288 App Keno