Rujukan Laman

Terms & Conditions for your Malaysia account

These Terms & Conditions set the rules for opening, using, and closing your qqnusa account, including sign-in, wallet actions, and access to each clause on this page.

Account useMalaysia lawVerificationSupport path

Explore the Lobby Read FAQ

What the terms cover

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

This page explains the clauses that govern account use, payment handling, content access, and changes to the wording that applies to you. The version that matters is the one tied to your account record and the region you use it from. If a rule changes by

1
location, local law decides whether the clause applies, and access is available only where local law permits. We may update these terms when the account flow, security checks, or verification steps need a clearer rule, and we may ask you to accept the new wording before
2
you continue. If your details are wrong or a wallet action needs extra checks, we can pause the affected action until the record is confirmed. For Malaysia accounts, deposits and withdrawals routed through Touch 'n Go, GrabPay, Boost dan FPX follow the same contract logic: the
3
payment rail must match the account, and any request can be held if the record does not match.

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

HELP ROUTES

Where to raise a term query

Use the channels below when you want the wording explained, a copy of the current version, or a correction to the record tied to your account.

Live chat Send the clause number, your registered email, and a short explanation of what you need. We use that to find the right wording fast and reply in the same thread.

Email Use email when you need a copy of the current wording or want to raise a correction request. Include your username, the date, and the account action so we can match the record.

Form Use the form for access questions, acceptance history, or any point tied to a payment route. Add the time, device, and any screenshot so the reply sits against the right clause.

DATA CARE

How we keep term records

We keep term acceptance logs, support history, and security records so we can show what you agreed to and when you asked us to change it.

Data handling

We keep account details, device data, and acceptance logs only for account handling, security, and clause checks. We do not use them for unrelated purposes, and access stays limited to staff who need the record.

Cookies

Cookies remember your login state, the language you last saw, and the version of the terms linked to your session. If you block them, some pages may ask you to sign in again.

Account security

Keep your password private, use a device you trust, and change the password if you think someone else knows it. We may ask for a fresh login or extra check before any account change.

Retention

We hold acceptance records, support logs, and verification files only as long as we need them for account handling, legal duties, or clause checks. After that, we remove or archive them under our retention rules.

Correction requests

If your name, email, or other account detail is wrong, send the correction through support from the same contact route on the account. We compare the request with the existing record before we amend anything.

Contact path

For access, correction, or a copy of the wording that applies to you, use the support route shown in your account. The reply path depends on local law and the options available for your region.

Common points on the terms

This section is here for the points people ask us about most: which wording applies, how location changes the rule, and how to request a correction or copy. We keep the answers tied to account records, local law, and the acceptance route you used, so you can check the clause that actually governs your account. If the answer depends on a payment action, device check, or update to the terms, the reply may include an extra verification step before anything changes.

The version that applies is the one linked to your account when you accepted it, plus any later update you agreed to. If a clause changes by location, local law and permitted access decide which wording is in force.

Yes, where local law permits and your account details match the region you opened it for. If a rule differs by place, the account will follow the version shown to you and any extra checks we need.

Send a request through support from your account area. We will match it to your profile and share the current wording that governs your use, so you can read the exact clause, not a summary.

Tell us the exact field that is wrong, such as name or email, and send the correct value through the account contact route. We may ask for a fresh check before we change the record.

Access can pause if the account cannot be verified, if a security step fails, or if you need to accept an updated clause. Once the issue clears, access resumes where local law allows.

Any wallet action, including deposits or withdrawals through Touch 'n Go, GrabPay, Boost dan FPX, follows the account record and the clause linked to it. A mismatch can hold the action until it is checked.

Use support and send the clause number, date, and account details involved. We will compare your note with the record and reply through the same route after we check what applies to you.

Terms & Conditions for your Malaysia account

Where to raise a term query

How we keep term records

Data handling

Cookies

Account security

Retention

Correction requests

Contact path

Common points on the terms

01 Which version of the terms applies to my account?

02 Can I use the account from Malaysia?

03 How can I get a copy of the current wording?

04 What if my details need correcting?

05 Why might access be paused?

06 How do payment actions fit the terms?

07 Who do I contact about a clause dispute?

Related Pages