Rujukan Laman

Malaysia legal terms in one place

At dfbocqi, this page sets out how access, data use, cookies, and record requests work for Malaysia, so you can see what we keep and why we keep…

Malaysia accessData useCookie settingsRecord requests
Explore the Lobby Read FAQ
dfbocqi Malaysia legal terms in one place
CONTACT PATHS

Where to send legal requests

Use the route inside your account so the right team can match your message with the right record.

In-account form Open the form from your profile area when you need a correction, a copy…
Email thread Write from the email linked to your account and state the exact change you…
Security follow-up For cases that need extra identity checks, we may ask for a fresh document…
RECORDS AND CHECKS

How we handle records and access

Session cookies keep you signed in and help us remember language choice, while security checks help us spot unusual access before changes are made.

Data handling

We keep the details needed to run the account, answer your request, and handle disputes. That may include login history, device markers, wallet actions, and support messages stored for the period our duties require.

Cookies

Cookies remember session state, language choice, and repeated security checks. Clearing them can log you out or reset a preference, but it does not erase the account records we keep.

Account security

Keep your password private and use a device you control. If we detect unusual access, we may pause changes until identity checks are complete, which helps protect the profile from unwanted edits.

Retention

We do not keep records longer than needed for dispute handling, fraud checks, or legal duties. When the retention period ends, the record is removed or anonymised under our internal schedule.

Who to contact

For access, correction, or deletion requests, use the contact route inside your account. Include the email linked to your profile and a clear description of what you want changed.

Request changes

If any stored detail is wrong, tell us the field, the correct version, and why it should change. We may ask for a fresh document before we update the record.

Questions on access and records

If you are checking how access, data handling, and request timing work, these answers keep to the parts that matter for Malaysia. We focus on local law, the records tied to your account, and the route you should use when you need a correction, a copy, or a status check. That way you know what happens before you send the message and what can happen after we receive it.

Access depends on local law and the checks tied to your account. If the current rule allows it, you can continue; if not, we do not make the account available until the rule changes.

We keep the records needed to run the account, verify changes, handle disputes, and meet retention duties. That can include login history, support messages, device markers, and wallet activity tied to your profile.

Send the field that needs changing, the corrected version, and any document that supports it through your account contact route. We may ask a follow-up question before we make the update.

Yes. Use the contact route in your account and say you want a copy of the records tied to your profile. We verify ownership first, then send the available file securely.

Cookies help us remember session state, language, and security checks. Clearing them may sign you out or reset a preference, but it does not erase the account records we keep.

The first reply comes from the support route shown in your account, then the right internal team handles the case. That keeps the request linked to your profile and avoids delays.

Related Pages

About Us Sugar Rush Register Cobra Queen