Reference

Privacy Policy for Your Indonesia Account

The rajacolok Privacy Policy explains what we collect, why we use it and how you can ask us to change or remove eligible details.

Clear data purposesWallet record contextAccount access stepsRequest path included
rajacolok Privacy Policy for Your Indonesia Account
ACCOUNT HELP PATH

Get Privacy Help From Your Account

A clear contact route helps when a data question is tied to a login or payment record. Sign in, open the account support path and describe the specific item you want us to check; if you cannot sign in, use the contact route shown on the rajacolok site. Include your registered phone number only through that secure route, never in a public message. We use the details you provide to locate the request and respond about your Privacy Policy rights.

Team online

Account access

If phone verification prevents access, tell us which account step stopped and the device you used. We can direct a privacy request through the available account support route without asking you to post personal details in an open chat.

Payment receipt

For a DANA, OVO, GoPay or QRIS record, share the reference shown in your account rather than wallet credentials. We use that reference to locate the transaction entry and explain what data our Privacy Policy covers.

Data request

Ask for access, correction or deletion of eligible account details through the signed-in contact path. We may verify ownership with your registered phone number before changing records, protecting your account from an outside request.

DATA CONTROL ROOM

Cookies, Security And Data Retention

We keep this Privacy Policy practical by linking each data type to an account task.

Phone verification

Before account access, we use the phone verification step to confirm that the person requesting entry matches the account record. This reduces mistaken disclosure when a mobile device is shared or a session is opened from a new browser.

Session cookies

Cookies can remember a signed-in session, language choice or security state on your browser. You can manage browser cookie settings, but disabling required cookies may interrupt the Privacy Policy request path or make you sign in again.

Payment records

Our records may contain a payment method, amount status, reference and time for DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. We do not treat that reference as permission to view unrelated wallet content.

Account security

Login events, device details and security signals can be checked when access looks unusual. These records help us protect your account and investigate a privacy concern, while we limit use to account, security and service purposes.

Retention period

We keep personal data only as long as it supports the purpose described in this policy, account administration, dispute handling or a legal requirement. When a record is no longer needed, our handling follows the applicable deletion or anonymisation process.

Changes and contact

You can request a copy, correction or eligible deletion by using the signed-in account contact path. We may ask for phone verification or another ownership check, then explain the result and any reason a record must remain.

Questions About rajacolok Privacy Policy

These Privacy Policy answers address the searches we hear most often from Indonesian account holders. They explain the practical steps for checking personal data, understanding wallet references and managing browser access. If your situation is not covered, sign in and send a specific request through the account support route. Access or eligibility depends on local law.

It covers data you submit for an account, phone verification details, device and session signals, cookies, support messages and payment references. It explains how we use, retain, secure and disclose those details for account access, security, payment status and policy requests.

Our Privacy Policy concerns the payment reference and status needed for an account transaction, such as DANA or QRIS. It does not give us general access to your wallet balance or unrelated wallet activity. Your wallet provider has separate privacy terms.

Sign in and use the account support path to request access to eligible personal data. State the account phone number and the records you want checked, such as login history or a GoPay reference. We verify ownership before releasing account details.

You can ask us to correct inaccurate account details through the same contact route. Explain what is wrong and provide the updated value. We may repeat phone verification before making a change, and we will explain if a transaction record must remain unchanged.

A mobile browser can store session and security cookies so your sign-in state works across account pages. Browser settings let you clear or restrict cookies. If required cookies are blocked, you may need to verify your phone again or lose access to a request form.

We keep payment references for as long as needed for the stated account purpose, security checks, dispute handling or applicable legal duties. This can include DANA, OVO, bank transfer and virtual account records. We remove or anonymise data when retention is no longer needed.

You may request deletion of eligible personal data through the account contact path. We first verify ownership and check whether a record is still needed for security, account administration or legal duties. If some data must remain, we explain the reason and limit its use.