Reference

Open Terms & Conditions Before Access

kijang777 Terms & Conditions set the account steps, payment rules and access boundaries you should understand before entering the lobby.

Account rulesWallet conditionsPolicy accessSupport route
kijang777 Open Terms & Conditions Before Access
POLICY HELP DESK

Contact Us About A Terms Question

A clear support path helps when a clause affects your account, wallet status or access request. We ask you to contact us from the account support route so we can connect your question with the correct registration or payment record. Include the relevant account detail and a short description of the clause you are asking about; never send a password or one-time verification code. Our support process is designed to clarify the Terms & Conditions rather than change a rule informally.

Team online

Account support route

Open the support path connected to your account when you need clarification about phone verification, duplicate details, login access or a policy clause. We can refer the request to the correct account record without asking you to disclose your password or one-time code.

Wallet status check

For DANA, OVO, GoPay or QRIS questions, include the payment reference and the wording that concerns you. We use the receipt or status detail to identify the relevant Terms & Conditions step, while bank transfer and virtual account questions follow the same account-linked process.

Policy change request

If a clause appears unclear or your personal details need correction, send the request through account support with the exact section and requested change. We review the wording against your account record and explain the available route under the current Terms & Conditions.

ACCOUNT SAFEGUARDS

Browse How We Handle Policy Details

Terms & Conditions only work when the related account records are handled carefully. We use the details needed to create, verify and maintain your account, while payment references help us match a…

Registration records

The account details you submit are used to apply the registration clauses, connect phone verification with account access and identify the correct account when you contact us. Keep your details current so a policy request is not delayed by a mismatch.

Payment references

A receipt, reference number or wallet status can be used to match a payment event with your account conditions. This applies to DANA, OVO, GoPay, QRIS, bank transfer and virtual account steps without requiring you to share private login credentials.

Cookie settings

Cookies may preserve sign-in continuity, remember a policy page setting or help us identify a session connected with your account. Your browser controls whether cookies remain active, and changing them may affect how the Terms & Conditions page opens.

Login protection

You are responsible for keeping your password and verification details private under the account clauses. If you notice unfamiliar access, stop using the session and contact support through the account path so we can check the account record.

Record retention

We retain account, support and payment references for the period needed to apply the Terms & Conditions, resolve a request or meet a legal requirement. Ask support which retention rule relates to your specific record and request.

Correction requests

You can ask us to correct inaccurate registration details or clarify how a policy record is being used. Send the request through account support with the affected field and account reference; we will explain the next step without requesting your password.

Find Answers About Account Conditions

These Terms & Conditions questions focus on the account decisions you are most likely to check before opening access or contacting support. We keep each answer tied to a practical step, including phone verification, local payment records, policy changes and requests about personal data. If your situation is not covered, use the account support path with the relevant section name.

They explain account registration, phone verification, login protection, permitted access, payment references, policy changes, data handling and support requests. They also state that access or eligibility depends on local law, so you should check whether the service is permitted where you are located.

Yes, our account conditions require phone verification before access is completed. Use a number you control and keep the verification details private. If the step stalls, contact support through the account route rather than creating another account or sharing a code.

The payment clauses can apply to DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity. The payment reference should match your account details, because we use that connection when checking status, identifying a request or explaining a payment-related condition.

You can request correction of inaccurate registration details through account support. Name the affected field and include the account reference, but do not send your password or one-time code. We assess the request against the current Terms & Conditions and explain the available next step.

We publish revised Terms & Conditions on this policy page and state the effective date where a change requires one. Review the wording before continuing account access. If a clause is unclear, contact support with the section title so we can address that specific question.

Cookies may help maintain sign-in continuity, remember a page setting or connect a session with your account. Your browser controls cookie storage, and changing those settings can affect page behaviour. Contact support if you need clarification about a cookie-related policy point.

Access is available only where local law permits. Check the rules that apply in your location before opening or using an account. For a site-specific question, contact us through account support and mention the access clause you want clarified.