Reference

ful500 Terms & Conditions, Made Clear

ful500 Terms & Conditions explain how you open an account, use the casino and sportsbook lobby, and manage DANA, OVO, GoPay or QRIS transactions.

Account accessWallet rulesPrivacy termsLocal law
ful500 ful500 Terms & Conditions, Made Clear
TERMS SUPPORT

Where to Ask About Account Rules

A clear support route matters when a Terms & Conditions clause affects your account or wallet status.

Account access If phone verification or a login rule blocks access, use the support link beside the account area. Tell us the device path you used, such as mobile browser or desktop browser, and quote the relevant Terms & Conditions section so we can assess the issue against your account record.
Wallet questions For a DANA, OVO, GoPay or QRIS question, open the support route beside the cashier area and include the displayed wallet status. For bank transfer or virtual account matters, add the reference shown on your account rather than sending unrelated personal details.
Policy changes To ask about a clause change, correction or account restriction, send the request through account support after signing in. We will identify the applicable Terms & Conditions version, explain the recorded action, and tell you which account step is needed next.
DATA PRACTICES

How We Apply These Terms

Our policy handling is tied to the records needed to operate an account: verification details, wallet references, device signals and support messages.

Account records

We retain account and phone-verification details needed to apply these Terms & Conditions. When you ask about access, we compare the request with the account record rather than treating a screenshot alone as proof. Keep your registered details current so a policy request can be matched accurately.

Wallet references

A DANA, OVO, GoPay or QRIS reference helps us trace the payment instruction linked to your account. Bank transfer and virtual account references serve the same purpose. We use the reference to check status and apply the transaction clause without requesting a wallet password.

Cookies and devices

Cookies and device signals may support login continuity, fraud checks and account security. Your mobile browser can carry the same policy session toward the lobby, while a new device may trigger another verification step under the Terms & Conditions.

Security duties

You must protect your login details and tell us through account support if you suspect unauthorised access. We may pause an account check while confirming identity, device activity or a wallet reference, then explain the relevant rule before access is restored or changed.

Retention requests

We keep policy and transaction records for the period needed to resolve disputes, meet legal duties and administer the account. If you ask why a record remains, include your account detail and the clause involved; we will explain the retention basis available for that request.

Changes and corrections

You can ask us to correct inaccurate account data or clarify a Terms & Conditions change through the signed-in support route. State the exact field or clause, attach only necessary evidence, and we will direct the request to the team responsible for that record.

Terms & Conditions Questions Answered

These Terms & Conditions answers focus on the points that affect an Indonesian account before you complete verification or use a wallet route. We cover access, account data, payment records, device checks and policy changes so you know which clause to read and which support path to use when a question remains.

You can open the Terms & Conditions from the policy link on the account area before completing the account step. Read the current version before using DANA, OVO, GoPay, QRIS, bank transfer or virtual account instructions, because those clauses govern the related transaction record.

They apply to accounts using the ful500 service where local law permits. Your location, account details and the relevant Indonesian rules can affect access or eligibility. If a mandatory local rule differs from a clause, that mandatory rule applies to the required extent.

Phone verification links the account to the contact detail you provide and helps us assess login, wallet and policy requests. A new device or an account change may require another check. Complete the requested step before asking support to change account access.

The terms cover the payment instruction, displayed wallet status and transaction reference connected to your account. If a status does not match, use account support with the rail name and reference. We do not need your wallet password to investigate the recorded instruction.

Yes. Send a correction request through the signed-in support path and identify the exact account field that is wrong. Include only necessary evidence. We will check the request against the applicable Terms & Conditions and explain whether an additional verification step is required.

A mobile browser and desktop browser may show the same account policy path, but a new device can trigger security or phone verification. Do not share login details. If access changes after switching devices, quote the device path when contacting account support.

Use the account support route to ask which version applies and when a clause changed. Mention the section title, account detail or wallet reference involved. We will explain the recorded change and any account action required, with access remaining subject to local law.