Rujukan Laman

Legal terms for your account

This page explains how we handle account data, cookie use, retention periods, and change requests on won99.

Malaysia lawData useCookie settingsRecord retention

Local law and records in practice

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

We handle legal requests according to the place where your account is used and the law that applies there. If a local rule limits access, changes how we keep records, or affects how a request is handled, we follow that rule for the case in front

1
of us. Account records are kept for identity checks, dispute handling, security logs, and proof of changes you ask us to make. Cookie data stays tied to session state, language choice, and basic safety checks, not to a separate profile outside your account. When you ask
2
for a copy, correction, or removal where local law allows it, we use the same account thread to trace the request, confirm the file, and answer clearly. That same approach helps us keep the legal trail in order without mixing one request with another.

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

REQUEST ROUTES

How to send a request

To send a legal request, begin in your account area and state the exact detail you want updated.

RECORD CARE

How we handle legal records

Our handling stays narrow and practical. Access is limited to staff who need the record for login checks, request handling, dispute work, and account security.

Data handling

We collect the account, device, and support details needed to run login, protect sessions, and answer your request. The record stays tied to that purpose, and access remains limited to the people handling the case.

Cookie settings

Cookie settings store session state, language choice, and basic safety checks so the site remembers your screen while you move around. You can clear them in your browser, and the account still keeps its own request history.

Security checks

When you ask for a change, we confirm the request against the account record before acting. That extra step helps prevent someone else from changing your data or access path without permission, and it keeps the action traceable.

Retention

We keep records only for the period needed for account history, dispute handling, and legal duties in the region. After that point, we remove or anonymise what we no longer need and keep only what the law requires.

Change requests

To ask for a copy, correction, or deletion where local law allows it, send one clear request from your account area. Include the detail you want changed so we can trace the exact record and respond on the same thread.

Contact trail

Every legal request gets a reference in the same thread, which helps you follow status and helps us avoid missing a reply. If the matter needs more checks, we tell you what is still pending before we close it.

Questions about access and records

Here, the legal side stays plain: what we hold, why we hold it, and how you can ask for a change. If your case depends on local law, we apply the rule that fits the place where your account is handled. Use the same account thread for follow-up so the record stays clean, easy to trace, and tied to the right request. That also helps us keep replies in order when there are several actions on one file.

You can ask for a correction, a copy, a deletion where local law allows it, or a check on how your record is used. Send the exact detail so we can match the request to the right file and respond cleanly.

Send the request from your account area and keep the same thread for follow-up. That lets us link the request to your record, check the right file, and reply without asking you to start again from zero.

Cookie data helps the site remember session state, language choice, and basic safety checks. It does not replace your account record; it only helps the page stay in the right state while you move around.

Only staff who need the record to handle the request can see it. We keep access narrow so the thread stays private, and we do not pass it around to unrelated teams or side tasks.

If local law asks for a different handling step, we follow that rule for the account in question. That can affect access, retention, or the way we answer a change request, depending on the case.

We keep records for the period needed for account history, dispute handling, and legal duties in the region. After that, we remove or anonymise what no longer needs to stay linked to the account.

Reply in the same thread and include the request reference. That keeps the file easy to trace and helps us avoid duplicate checks or mixed replies on the same matter, especially when a case has several steps.

Legal terms for your account

How to send a request

How we handle legal records

Data handling

Cookie settings

Security checks

Retention

Change requests

Contact trail

Questions about access and records

01 What can I ask you to change?

02 How do I request my record?

03 Why do you keep cookie data?

04 Who can see my request?

05 What if local law differs?

06 How long do you keep records?

07 How do I follow up later?

Related Pages