Rujukan Laman

Privacy Policy For Your zas36 Account

This Privacy Policy explains what zas36 collects when you open an account, use the lobby or contact support, and why each detail is needed.

Clear data purposesCookie choicesMalaysia account access

Explore Lobby Read FAQ

How We Use Your Personal Data

zas36 Service availability depends on jurisdiction. It is the user's responsibility to check local law before access.

When you create or use an account, we may handle your name, contact details, login credentials, verification records, device identifiers, approximate location, session activity and account messages. We use these details to open and secure your account, detect unusual access, process requests, answer support enquiries and

1
meet applicable legal duties. Payment references from Touch 'n Go, GrabPay, Boost dan FPX may be used to match a deposit or withdrawal request, but payment credentials remain with the relevant provider. Cookies and similar tools help keep sessions active, remember selected settings and measure page
2
performance. We limit access to staff and service partners who need it for these purposes. The policy applies to Malaysia access where local law permits, including access from Kuching. We may update this page when our handling practices change, with the revised date shown on the
3
page.

Service availability depends on jurisdiction. It is the user's responsibility to check local law before access.

POLICY CONTACT

Three Ways To Ask About Privacy

Questions about your personal data should be easy to raise. Our support routes are available for account access concerns, cookie requests, correction requests and questions about…

DATA CONTROLS

Six Parts Of Our Privacy Practice

Privacy work covers more than the registration form. We consider the records created during sign-in, browsing, payment matching, support conversations and security checks.

Data we collect

We collect details you submit for an account or support request, plus technical records such as device type, browser, IP address and session times. We use them to provide access, investigate faults and protect the account.

Cookie handling

Session cookies help keep you signed in and preserve selected settings. Measurement tools may record page visits in grouped form. You can manage cookies through your browser, although some account functions may then behave differently.

Account security

Login events, device signals and verification records help us identify unusual activity. We may pause a sensitive request while checking ownership. Never send a password, one-time code or payment PIN through a support message.

Retention periods

We keep records only for as long as needed for the stated purpose, account safety, dispute handling or a legal duty. When a record is no longer needed, we delete it, anonymise it or restrict access.

Third-party access

Service providers may process limited data for hosting, security, messaging, analytics or payment matching. They receive only what their task requires and must handle it under contractual and applicable legal controls.

Changes and requests

You can ask what personal data we hold, request a correction or raise a deletion question through support. We assess each request against identity checks, account safety and any retention duty that still applies.

Answers About Your Personal Data

The questions below cover the requests we receive most often about the Privacy Policy. They explain the practical steps for checking, changing or limiting the use of personal data connected with your zas36 account. The answer may depend on the record involved, your identity confirmation and the laws that apply to your location.

We may collect your contact and login details, verification records, device and browser signals, approximate location, cookie activity, payment references and messages you send to support. The exact records depend on how you use the account.

Account details let us create access, protect sign-in, match requests to the correct account, answer support enquiries and process account activity. We use each category for a stated purpose and limit access to people who need it.

Yes. Contact the privacy route shown on the page and describe your request. We may confirm your identity before responding, then explain the relevant records, their purpose and any reason a part cannot be disclosed.

Send the correction request through account support or the privacy email, including the affected field and the correct value. We may ask for confirmation before changing identity or verification details linked to account security.

You may ask us to delete personal data connected with your account. We assess the request against security, dispute handling and legal retention duties. Some records may be removed, anonymised or retained for a defined reason.

Touch 'n Go, GrabPay, Boost dan FPX handle their own payment credentials. We may receive transaction references, status and related account details to match a request, investigate a discrepancy and maintain an accurate activity record.

You can adjust browser cookie controls or contact support when a site preference needs help. Removing session cookies may affect sign-in or saved settings. We will explain which cookie category your request concerns and what change is available.

Privacy Policy For Your zas36 Account

Three Ways To Ask About Privacy

Six Parts Of Our Privacy Practice

Data we collect

Cookie handling

Account security

Retention periods

Third-party access

Changes and requests

Answers About Your Personal Data

01 What personal data does zas36 collect?

02 Why do you need my account details?

03 Can I ask what data you hold about me?

04 How can I correct inaccurate data?

05 Can I request deletion of my data?

06 How are payment details handled?

07 How do I change cookie preferences?

Related Pages