Reference

rgo365 Legal and account access

rgo365 Legal sets out how we handle your account, payment records and access to our Indonesia service.

Account termsData handlingLocal accessContact steps
rgo365 rgo365 Legal and account access
CONTACT ROUTES

Three ways to raise a Legal question

A clear contact path helps when your question concerns access, a payment record or a policy request.

Account support Use the support path from your signed-in account for questions about phone verification, access status or a policy notice. Include your linked phone number and the exact message shown on your mobile browser so we can match the request to the right account record.
Payment records For DANA, OVO, GoPay or QRIS questions, attach the payment reference rather than your wallet password or PIN. Our team can compare the reference with the account ledger and explain whether the record is pending, matched or requires another account step.
Policy requests If you want a correction, access clarification or copy of a policy record, state the request in plain English through the account contact path. We may ask for phone verification before discussing account-specific details or changing information linked to your account.
DATA PRACTICE

How we handle your Legal records

We treat Legal questions as account matters, not as general lobby enquiries. Our process links access decisions to the account record, keeps payment references separate from wallet credentials and uses the contact…

Account details

We use the details you provide during account opening to create and maintain your account record. Phone verification helps us confirm that an access request is connected to the number on file before we discuss account-specific Legal or payment details.

Payment references

A DANA, OVO, GoPay or QRIS reference can be used to trace a payment status, while bank transfer and virtual account records help us reconcile the matching account entry. We do not need your wallet PIN to investigate a receipt.

Cookies

Cookies and similar browser storage can keep a session active and remember basic access settings. You can clear them through your browser controls, but doing so may sign you out and require phone verification again before account access.

Account security

Keep your phone, password and wallet credentials private. We will not ask you to disclose a wallet PIN in the support path. If you suspect that someone accessed your account, contact us with the linked phone number and stop using the affected session.

Record retention

We retain account and transaction records for the period needed to operate the service, resolve disputes and meet applicable legal duties. A retention request does not automatically remove records that we must keep under a local rule.

Change requests

To request a correction or ask how a record is used, contact us through the signed-in account route where available. Describe the field or transaction, add its date and complete any phone verification needed to protect your account.

Answers about rgo365 Legal

These Legal answers cover the account questions most often raised before access. They explain the practical route for checking eligibility, correcting records, protecting wallet details and asking about a policy decision. Read the current Legal notice as well, because local requirements can affect whether access is available.

rgo365 Legal covers account opening, phone verification, access conditions, payment records, cookies, security, retention and requests to correct account details. Eligibility depends on local law, so you should check the current notice before opening an account or using any listed casino or sports content.

Access from Indonesia is available where local law permits. We may require a clear account path and phone verification before access. If your screen shows a restriction, contact account support with the linked phone number and the exact message rather than trying to bypass the restriction.

Phone verification connects an access request to the account holder and helps us discuss private account or payment details safely. It may also be needed for a correction request. Never send your password, wallet PIN or full security credentials through the support path.

We use the DANA or QRIS payment reference, date and account details to match a transaction and explain its status. We do not need your wallet PIN. For a payment question, send the receipt reference through account support so the record can be checked without exposing private credentials.

Use the signed-in account contact route and identify the account field or transaction you want corrected. Add the relevant date and linked phone number. We may ask for phone verification before changing information or disclosing details, and some records may need to remain under applicable law.

Our mobile browser path may use cookies or browser storage to keep a session active and remember basic access settings. Clearing them can sign you out and trigger phone verification again. Your browser controls let you manage these settings, subject to the access needed for account security.

Use the account support path and describe the restriction exactly as it appears. Include your linked phone number and the date you noticed it. We can explain the account record or applicable Legal wording where local law permits, but we cannot bypass a restriction required by local law.