Rujukan Laman

Your Privacy Policy For Malaysia Accounts

This Privacy Policy explains how we collect, use, store and protect data linked to your ep369 account, including identity checks, wallet activity, device signals and support messages.

Clear data choicesSecure account recordsMalaysia privacy contact
ep369 Your Privacy Policy For Malaysia Accounts
PRIVACY HELP

Get Clear Help With Privacy Requests

Questions about this Privacy Policy can be sent through the signed-in account support channel or the privacy contact route shown on ep369.

Account channel Use the signed-in account channel to ask how your account data is used, request a copy, or check the status of a correction. Keeping the request inside your account helps us match it to the correct record.
Privacy requests For deletion, restriction or objection requests, contact the privacy route shown on the site and state the action you want. We will explain any legal or operational reason a record must remain, plus the time period that applies.
Security concern If you suspect account data has been exposed, use support promptly and describe the date, device and message involved. Do not include passwords or one-time codes; we use the details to assess the incident and tell you which protective step comes next.
SECURITY PRACTICE

How ep369 Handles Your Account Data

Our handling process separates account identity, transaction references, device data and support content so each category is used for a clear purpose.

Collection purposes

We collect account details you provide, verification results, wallet references, device signals and support messages. Each category is linked to a stated purpose, such as account safety, transaction matching, security checks or responding to you.

Cookie choices

Cookies and similar storage help keep sessions active, remember selected settings and measure page performance. Your browser may allow you to remove or block them, although some account functions may then need to be repeated.

Sign-in protection

We protect account access with sign-in controls, session checks and monitoring for unusual activity. Never share a password or one-time code; if a sign-in looks unfamiliar, contact support so we can assess the event and secure the account.

Retention periods

Transaction references, verification records and support conversations are retained for different periods. We remove, anonymise or restrict records when the relevant purpose ends, unless a legal duty, security need or open dispute requires continued storage.

Your data access

You may ask for a copy of personal data, correction of inaccurate details, deletion where allowed, or a reason for processing. We may verify your identity first to prevent another person receiving your account data.

Policy versioning

When this policy changes, we will publish the revised wording and effective date on this page. Material changes may also be signposted through an account message, so you can consider the new handling before continuing.

Answers For Your Privacy Requests

These answers address the requests we receive most often about account privacy. The exact response can depend on the data involved, the verification needed and Malaysian legal requirements. If your question is not covered, contact us through the privacy route and tell us which account record or processing activity concerns you. We will keep the reply focused on your rights, the records concerned and the next available step.

We collect details you submit, verification results, wallet and payment references, device or session signals, and messages you send to support. We use them for account access, transaction matching, security checks and responding to your requests.

Verification helps connect the correct person to an account, reduce unauthorised access and meet applicable legal duties. The required checks depend on your account activity and local law; access or eligibility depends on local law and is available where local law permits.

We receive or store transaction references and status details needed to match deposits or withdrawals, not your provider password or one-time code. The relevant payment provider handles its account data under its terms, while we use these records for your ep369 account.

Yes. Contact us through the privacy route, identify the account record involved and state whether you want access or correction. We may request identity checks before releasing a copy or changing details, and we will explain the next step.

You can request deletion where applicable. Some records may need to remain for legal duties, security checks, transaction disputes or account administration. We will tell you what can be removed, what must remain and how long the restriction applies.

Cookies can keep your session active, remember settings and help us understand page performance. You can manage them through your browser or available site controls. Blocking some cookies may require you to sign in again or repeat a preference.

Use the signed-in support channel or the privacy contact route shown on ep369. Include your account email or identifier, request type and relevant dates, but never send a password, one-time code or full payment credential.