Reference

Terms & Conditions For miyajp Access

miyajp Terms & Conditions set the rules for opening an account, using DANA, OVO, GoPay or QRIS, and reaching the casino and sports areas.

Account stepsWallet rulesPolicy accessLocal-law wording
miyajp Terms & Conditions For miyajp Access
HELP WITH TERMS

Get Answers Before You Accept

A clear question deserves a clear route, especially when a policy affects your account or wallet action. We ask you to include the account detail or payment reference connected with your question, without sending a password or security code. Our support path can clarify wording, access conditions and the status of a DANA, OVO, GoPay or QRIS instruction. Use the contact route displayed within your account so the request reaches the right policy context.

Team online

Terms questions

Ask us to explain a clause before you accept it. Include the section heading and the account email or phone detail linked to your miyajp account, so we can answer the exact Terms & Conditions question rather than guessing from a general description.

Wallet disputes

If a DANA, OVO, GoPay or QRIS status does not match your record, send the payment reference through the account support route. We can check the displayed instruction and explain which Terms & Conditions section governs that wallet action.

Access concerns

When an account step or phone verification prevents access, contact us from the support route shown near your account area. Tell us the device path you used and the message displayed; we will point you to the relevant policy wording.

ACCOUNT SAFEGUARDS

What We Handle Under These Terms

The policy also tells you how we handle the practical details behind an account. We use the details needed to operate access, verify a phone step, assess a payment record and respond…

Data handling

We use account details for the purposes described in these Terms & Conditions, such as access checks, phone verification, payment status matching and support replies. We do not need your password or one-time security code in a support request.

Cookie settings

Cookies may keep a required session active or remember a setting while you move through the account path. Your browser controls can remove them, although doing so may require you to repeat a login or verification step.

Account security

Keep your login details private and use only your own verified phone path. If an unfamiliar sign-in or account change appears, stop the action and contact support through the route connected to your account.

Payment records

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference helps us match a wallet action with the correct account record. Retain the receipt until the displayed status and your account history agree.

Retention requests

If you want to ask how long a particular account or payment record is kept, name the record and the policy section in your request. We will explain the applicable retention wording and any account step involved.

Change requests

To request a correction to account details or ask about a policy change, contact us through the in-account support route. We may need phone verification before changing information that affects access or payment matching.

Terms & Conditions Questions Answered

These Terms & Conditions questions focus on the account decisions you are most likely to make before opening access. We explain the acceptance step, local eligibility, wallet records, data requests and the support route in direct language. If your situation is different, quote the relevant clause when you contact us so we can keep the answer tied to the current policy.

They cover account creation, phone verification, access, wallet instructions, security, data handling, cookies, policy changes and support requests. They also explain how local eligibility is treated. Read the current text before accepting it, particularly if you intend to use DANA, OVO, GoPay or QRIS.

They apply when you open an account, sign in, accept the policy or use an account action described in it. A payment reference, phone verification step or access request can therefore be subject to the clause connected with that action.

Yes. Access and eligibility depends on local law, so the availability of an account action may differ by location. If you are in Indonesia and are unsure whether a step applies to you, contact support through the route shown in your account.

You can request a correction through the in-account support route. Name the detail that appears wrong and identify the account step it affects. We may ask you to complete phone verification before changing data used for access or payment matching.

DANA and QRIS actions are matched to the account and payment reference shown during the relevant cashier step. Keep your receipt until the status agrees with your account history. If it does not, send the reference through support for a policy-based check.

Do not continue with the account action if the wording is unclear or unacceptable. Contact us through the support path displayed in your account, quote the section heading and ask whether a different access route is available where local law permits.

Use the account support route and name the clause or date displayed with the policy. We can explain what changed, which account action it affects and whether you need to accept the current text before continuing with access or wallet steps.