Reference

rkgg Privacy Policy for Your Account Data

Your account details, phone verification, wallet status and device signals are covered in the rkgg Privacy Policy, so you can understand what we collect before opening an account.

Account dataWallet activityDevice accessCookie choices
rkgg rkgg Privacy Policy for Your Account Data
PRIVACY HELP

Where to Ask About Privacy Policy

A clear support path matters when your account data or wallet record needs attention. Start inside your signed-in account and use the support route near the cashier area, including the account identifier and the privacy question you want answered. We use those details to locate the correct record without asking you to send a wallet PIN or full payment credential.

Team online

Access questions

If phone verification blocks account access, tell us which step stopped and the device path you used, such as a mobile browser or desktop browser. We can direct the privacy request to the relevant account record.

Wallet records

For DANA, OVO, GoPay or QRIS records, include the payment reference and date rather than a PIN. This lets us check the account link while limiting the sensitive details shared in your request.

Data changes

To ask for a correction, access copy or deletion assessment, use the account support path and describe the requested change. We may verify account ownership before acting so another person cannot alter your data.

CONTROL YOUR DATA

Privacy Controls Behind Your rkgg Account

We keep this policy practical by connecting each privacy choice to an account action you recognise.

Account details

We use the account details you submit to create and maintain access. Before discussing a record, we may ask for an account identifier and phone verification step so the request is tied to the right person.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references help us trace an account request. We focus on transaction identifiers and status data, not wallet PINs or full secret credentials.

Device signals

Mobile browser, desktop browser, operating system and sign-in events may be recorded to recognise unusual access. These signals support account protection and are not a substitute for your phone verification.

Cookies

Cookies can keep a signed-in path working and help us understand which privacy notice was shown. You can restrict optional cookies in browser settings, although some account functions may then need another sign-in.

Retention periods

We retain records only for the period needed for account operation, payment matching, dispute handling or applicable obligations. A deletion request may be limited where a record still serves one of those purposes.

Request route

Send privacy questions, access requests or correction requests through the support path inside your account. We will ask for enough detail to confirm ownership and can explain the outcome of the request.

Privacy Policy Questions Indonesian Accounts Ask

These Privacy Policy answers cover the account steps and local wallet records you are most likely to ask about before joining. If your situation is not listed, use the account support path with a short description and the relevant payment reference, device path or phone verification step.

It covers account details, phone verification, wallet references, device signals, sign-in events and cookies used on rkgg pages. It also explains retention, privacy requests and the conditions affecting access where local law permits.

Yes. The Privacy Policy covers references and status details connected with DANA, QRIS, OVO, GoPay, bank transfer and virtual account requests. We do not ask you to provide a wallet PIN.

Phone verification helps connect an account request to the correct person before account access. It also supports privacy checks when you ask us to access, correct or remove account data.

You can request access to the personal data linked with your account through the signed-in support path. Include your account identifier, and we may verify ownership before providing a response.

Send a correction request through account support and identify the field or payment reference that appears wrong. For DANA, OVO, GoPay or QRIS records, include the date and reference, not secret wallet details.

You may send a deletion request through the account support path. We assess it under the Privacy Policy, because some account, payment or dispute records may need to remain for operational or legal reasons.

Cookies can support sign-in continuity and remember the privacy notice shown on your mobile browser. You can restrict optional cookies in browser settings, but required account functions may ask you to sign in again.