Reference

Terms & Conditions For Your Account

rina 4d Terms & Conditions explain how you open, use and protect your account before entering the lobby.

Account eligibilityWallet verificationLocal law appliesPolicy accessSupport route
rina 4d Terms & Conditions For Your Account
POLICY HELP

Get Help With A Terms Question

A clear contact path helps when a clause affects your account, wallet status or access request.

Account contact form Use the support form inside your account when you need a clause explained or…
Cashier status path A wallet question should include the payment rail and reference shown on your screen.
Access clarification If your account cannot reach the lobby, contact us from the same registered account…
ACCOUNT SAFEGUARDS

How We Apply These Conditions

Our policy handling follows the details attached to your account rather than informal messages or screenshots alone.

Account data

We use the account details you submit to manage access, verification and support requests under these Terms & Conditions. If a phone number or other detail is wrong, send a change request from the account route so we can match it to the existing record.

Cookies

Cookies and similar device records help keep your account path connected between login, policy pages and the lobby. You can ask support what cookie-related setting applies to your session, while changing browser settings may require another phone verification.

Login security

Keep your password private and use only your own device path when opening the account area. We may ask for phone verification before access, particularly after a browser change or an account detail update described by these Terms & Conditions.

Payment records

For DANA, OVO, GoPay, QRIS, bank transfer and virtual account requests, we retain the reference needed to match a receipt with your account. Never send a full password or wallet PIN; the payment name and visible reference are enough for an initial check.

Retention requests

If you want to ask how long a policy, account or payment record is kept, use the support form and identify the record type. We will explain the available handling route, including whether a legal or transaction reason requires the record to remain available.

Policy changes

When a clause changes, we place the revised wording on this policy page and may show a notice during account access. Check the date or message attached to your session before continuing, then contact us if the change affects your account or wallet request.

Terms & Conditions Questions Answered

These Terms & Conditions answers focus on the account decisions you are most likely to make before access. We explain the local-law wording, verification step, payment references, device behaviour and contact route without turning the policy into a general lobby description. If your situation is not covered, use the support form from your registered account and quote the relevant clause.

They cover account opening, phone verification, login security, wallet references, policy access, data handling and requests for account changes. They also explain that availability depends on local law. Read the wording before continuing, especially when a DANA, OVO, GoPay, QRIS or bank transfer step appears.

Yes. Account eligibility and access depend on local law. Where local law permits, the account path may proceed after the required checks. If the system pauses access, contact us from your registered account so we can explain whether the issue relates to verification, location rules or another policy condition.

Phone verification connects the account to a contact detail you control and helps us handle login or policy requests safely. We may request it before access, after a device change or when account details are edited. Do not send your password or wallet PIN to support.

Use the payment rail and reference displayed for your account, and make sure the account details match the transaction. For DANA and QRIS, we use the visible reference to check status. A mismatch can delay confirmation while we ask for clarification through the registered support route.

Yes, send the request through the account contact form and identify the detail that needs changing. We may ask for phone verification or another account check before applying it. This protects the record and prevents a change from being attached to the wrong account.

The same Terms & Conditions apply on both device paths, but a browser or device change may trigger phone verification again. Keep your login details private and use the registered account route if access stalls. We can then identify whether the issue is security-related or policy-related.

Open the support form from your registered account and quote the clause or section title you mean. Add your account phone number and, if relevant, the payment rail such as GoPay, OVO or virtual account. We will use those details to direct the question without requesting your password.