Reference

Privacy Policy for Your ratu118 Account

Our Privacy Policy explains what account data we collect, why we use it, and how you can ask about it when you use ratu118.

Account dataWallet recordsCookie choicesContact path
Explore Our Lobby Read FAQ
ratu118 Privacy Policy for Your ratu118 Account
CONTACT ROUTE

Where To Ask About Your Privacy Policy

A direct support path helps when you need a copy, correction or explanation of account data. Start from the support contact shown in your signed-in account, and include the phone number linked to ratu118 plus the subject of your request. Do not send a wallet PIN or full password. We may ask for an account step or phone verification before discussing private records. The same route covers cookie questions, cashier references and access requests from Jakarta.

Team online

Account data request

Ask us to identify the account data connected with your phone number. We may confirm your identity through the account step or phone verification before releasing private details.

Wallet record question

Send the transaction reference and payment rail when asking about DANA, OVO, GoPay or QRIS data. We use those details to locate the correct cashier record without requesting your wallet PIN.

Cookie or access help

Tell us which device and browser you used if a cookie choice or sign-in record looks unfamiliar. Our support path can explain the record and the next account-security step.

HANDLING PRACTICE

How We Handle Account Data

We keep this policy practical: data is collected for a stated account, security, payment-matching or support reason, then accessed by the people or service processes that need it.

Account creation

When you open an account, we use the details you enter to create access and connect later requests to the correct account. Phone verification may be required before private account data is discussed.

Payment matching

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references help us match a cashier event. We retain the reference needed for account records without asking for your wallet password.

Device security

Sign-in time, browser type and device signals can be checked when access appears unusual. If you use a mobile browser to reach the lobby, those security records may be linked to your account session.

Cookie controls

Cookies can remember a session and support account access, while browser controls let you remove or restrict them. Removing cookies may require you to complete phone verification again at the next sign-in.

Record retention

We keep each category only as long as needed for its stated purpose, account security, dispute handling or a legal request. Ask support about a particular record instead of sending sensitive credentials.

Change request

If your name, phone details or account data needs correction, contact us through the signed-in support path. We check the request against your account before changing a record or explaining why it remains.

Privacy Policy Answers For ratu118

These Privacy Policy answers cover the searches we hear most often before account access: what we collect, how wallet references are used, what cookies do, and how to request a change. Keep your phone number and transaction reference ready when contacting support. For access or eligibility questions, the applicable position depends on local law.

It covers account details, phone verification, device and sign-in records, cookies, support messages, and payment references from DANA, OVO, GoPay, QRIS, bank transfer or virtual account. It also explains why we use each category and how you can contact us.

Yes. We use a DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference to match a cashier event with your account. The reference supports reconciliation and support replies; we do not need your wallet PIN for that process.

Use the support contact shown after you sign in and state that you want a copy of your account data. Include your linked phone number, but never send your password or wallet PIN. We may complete phone verification before responding.

You can request a correction through the signed-in support path. Tell us which field is wrong and provide the account detail needed to locate it. We may confirm your identity first, then update the record or explain the reason it remains.

Cookies can keep a mobile browser session connected to your account and help identify an unfamiliar sign-in. You can remove or restrict them through browser settings. After removal, the next access may require another sign-in or phone verification step.

The period varies by record type and the reason it is needed, including account security, payment matching, dispute handling or a legal request. Contact support with a specific record question, and we will explain the applicable retention position.

Yes. Use the contact path displayed on the site and ask about the Privacy Policy before completing account creation. Do not include a password or wallet PIN. Account access and eligibility depend on local law, so those questions may need a separate answer.

Related Pages

ratu118 Indonesia About Us Access guide FAQ Badminton Asia Championship Bet