Reference

Privacy Policy for Your ratu338 Account

Our Privacy Policy explains how we handle the details you provide when opening a ratu338 account, checking wallet status, or contacting support.

Account dataWallet recordsDevice accessPrivacy requests
ratu338 Privacy Policy for Your ratu338 Account
PRIVACY CONTACTS

Where To Send A Privacy Request

A direct request helps us locate the right account record without asking you to repeat the same details. Contact us through the support route shown on ratu338 and state whether you need access, correction, deletion, or an explanation of a wallet record. Include the phone number linked to your account and a short description of the issue, but do not send a password or one-time code. We may ask for account checks before discussing personal data. This protects your account while keeping a clear path for questions about the Privacy Policy.

Team online

Account access

If you cannot reach your account after phone verification, contact support through the route displayed on ratu338. We use your account identifier and recent device details to check whether the request concerns a login record, a security block, or an incorrect profile entry.

Wallet records

For a DANA, OVO, GoPay, QRIS, bank transfer or virtual account question, send the payment reference and approximate time through support. We compare that reference with the account record, while asking you to hide passwords, access codes and unrelated financial details.

Privacy changes

To request correction, access or removal of personal data, identify the account and describe the requested action. We confirm ownership before making a change, explain any record we must retain, and reply through the contact path associated with your account.

DATA HANDLING

How We Apply The Privacy Policy

Your account data should have a clear purpose, so we connect each handling step to account access, payment checks, security or support.

Account details

We use your phone details and verification status to create and protect the account path. Before changing those details, we may compare the request with existing account records. This reduces the chance that another person redirects access or receives account-related replies.

Device signals

Browser type, device markers, language settings and session times can help us detect an unusual login. We use these signals for security and troubleshooting rather than asking for your password. Clearing browser data may require you to complete account verification again.

Cookies

Small browser files can keep a session active, remember basic page settings and help us understand whether an account page loads correctly. You can manage cookies in your browser, but disabling them may affect login continuity or require another verification step.

Payment matching

Payment references from DANA, OVO, GoPay, QRIS, bank transfer and virtual account routes help us match a transaction with your account. We use the reference and status needed for that check, not a request for your wallet password or private access code.

Retention choices

We keep account, security, support and payment records only for the period needed for account operation, dispute handling, fraud checks or a legal duty. When a retention reason ends, we remove, anonymise or restrict the record where local law permits.

Request ownership

A privacy request must come from the account holder or an authorised representative. We may ask for phone verification and a matching account detail before responding. We do not ask you to place a password, one-time code or full wallet credential in a message.

Privacy Policy Answers For Indonesia

These Privacy Policy answers address the account and payment questions we hear most often from people considering ratu338 in Indonesia. They explain the practical path for checking data, correcting a phone detail, understanding device records and asking about DANA, OVO, GoPay or QRIS references. If your situation involves local eligibility, access depends on local law. For an account-specific answer, use the support route and include only the details needed to locate your record.

The Privacy Policy covers details such as your phone information, verification status, login history, device signals, session activity and support messages. We use them to provide account access, check security, match payment references and answer requests. We do not need your password or one-time code to investigate a normal question.

We use a payment reference to match a DANA, OVO, GoPay or QRIS transaction with the correct account and status. The same approach can apply to bank transfer or virtual account records. Send only the reference and relevant timing through support, with private wallet credentials removed.

Yes, you can send an access request through the support route shown on ratu338. Identify the account with its linked phone details and describe the records you want checked. We verify ownership first, then explain what can be provided and whether any record must remain restricted.

Ask support to correct the phone detail linked to your account and explain why the existing entry is wrong. We compare your request with account records and may require phone verification before making a change. A correction can affect login access, so we explain the next account step.

Yes. Mobile browser type, device markers, language settings and session times may be recorded for security and troubleshooting. A desktop browser can create a separate session record. These signals help us assess unusual access; they do not replace your account verification or require your password.

We retain payment references, support messages and security records for the period needed to operate the account, handle disputes, check misuse or meet a legal duty. When that reason ends, we remove, anonymise or restrict the record where local law permits.

You can ask us to delete or restrict personal data through the stated support route. We first confirm account ownership and assess the request against operational and legal duties. Some payment, security or dispute records may need to remain for a defined purpose before removal is possible.