Rujukan Laman

asianbookie5 Privacy Policy for Your Malaysia Account

This page explains what we collect, why we use it, and how you can ask for access or changes before you open your account.

Plain wordingLocal law appliesAccess and changesMalaysia focus
asianbookie5 asianbookie5 Privacy Policy for Your Malaysia Account
CONTACT CHANNELS

How You Reach Our Team

If you want to ask about stored details, contact preferences, or a record copy, use the channel that fits your request best.

Account chat Open the chat inside your account for quick questions about access, correction, or a…
Support form Use the form when you want a written trail for a privacy request, especially…
Privacy mailbox Email suits longer requests or attachments, and it gives you a clear copy of…
HANDLING STANDARDS

How We Handle Your Records

We keep this policy practical. Cookie settings, account changes, and support messages are stored only as long as they help us run your account, handle a dispute, or meet legal duties where…

Data handling

We collect only what is needed to manage your account record, process support requests, and keep a clear history of changes. Unneeded fields are not kept in active use once the request is closed.

Cookie settings

Cookies remember language, session state, and consent choices so the page behaves the same when you return. You can clear them in your browser, and the site will load with a fresh session.

Account security

We use login checks, session timeouts, and change alerts to reduce unwanted access. When we see a risky sign-in, we may ask for another check before we accept a sensitive request.

Retention

Records stay only for the time needed to support the account, settle a dispute, or meet legal duties where local law permits. After that, we remove or archive them according to our schedule.

Access and correction

You can ask us to show the record we hold, correct a mistake, or explain why a field is needed. We may request a matching detail so we do not disclose the wrong account.

Contact trail

Messages sent through chat, form, or email stay linked to your request so the right team can follow the thread. That record helps us answer clearly and keep the change history traceable.

Questions About This Policy

These answers cover the practical parts of our policy: what we keep, why we keep it, how long it stays, and how you can ask for access or changes. If your request depends on local law, we follow the rule that applies where the request is made. Use the contact paths above when you need a record of the conversation.

We keep the details you enter, the device signals needed for session stability, and the message history tied to support. That mix helps us match requests, fix errors, and answer questions about your account record.

Cookies remember language, session state, and consent choices. They also help the site recognise a fresh page load after you return, so your preferences do not disappear between visits.

Records stay only as long as needed to run your account, handle a question, or meet legal duties where local law permits. After that, they are removed or archived under our retention schedule.

Yes. Send the request through chat, the form, or email, and we will check the record against enough matching details before we change it. That keeps the update attached to the right account.

When you pay through Touch 'n Go or FPX, we keep the reference so we can match it to your account, answer questions, and resolve mismatches without asking you to resend the same record.

Use the chat in your account for quick questions, the form for a written trail, or email for longer requests and attachments. We reply through the same path so you can keep track.

Access depends on local law and is available where local law permits. If a request can be handled, we will follow the rule that applies and explain any limit that affects the record.