Reference

raja buaya Privacy Policy For Your Account

Our Privacy Policy explains how raja buaya collects, uses, stores and protects the details connected with your account, wallet activity and device access.

Account dataWallet recordsDevice accessPolicy requests
raja buaya raja buaya Privacy Policy For Your Account
CONTACT ROUTES

Account Path For Privacy Requests

A clear contact route helps when you need a copy, correction or deletion request connected with your account. Start from the account support path and include the phone number linked to your profile, plus the relevant wallet receipt or device detail. We use those details to locate the correct record without asking you to send a full password or security code.

Team online

Account support

Use the account support path for a Privacy Policy question, data copy request or correction request. Include your linked phone number so we can identify the right account.

Wallet status

For a DANA, OVO, GoPay or QRIS record, share the transaction reference and date through the support path. We check the payment record without requesting your wallet PIN.

Security concern

If an account access event looks unfamiliar, contact support through your account path promptly. We can review the device session, phone verification status and related security record.

SIX DATA CONTROLS

Six Controls For Your Account Data

We apply this Privacy Policy through specific handling steps rather than broad promises. Account records stay connected to the phone verification step, wallet records stay linked to a payment reference, and device…

Data collected

We may handle your account details, verified phone number, support messages, wallet references and device session data. We collect what is needed to connect access, security and payment records.

Cookie choices

Cookies can retain a session and remember selected access settings on your browser. You can adjust browser cookie controls, although some account access steps may then need to be repeated.

Account security

Phone verification supports account access, while device session records help us examine unfamiliar sign-ins. Never send your password, wallet PIN or one-time security code through support.

Retention period

We retain account, payment and security records only for the period needed for the stated purpose, account support and legal duties. Retention can differ when a payment query remains open.

Who to contact

Our account support route handles Privacy Policy questions, access requests and concerns about a DANA, OVO, GoPay, QRIS or bank transfer record linked to you.

Request a change

You can ask us to correct an inaccurate account detail or explain a stored record. Include the relevant account step, device path or payment reference so we can assess the request.

Privacy Policy Answers For Indonesia Accounts

These Privacy Policy answers address the searches we hear most often before an account is opened or a wallet record is checked. We keep each answer tied to an actual account step, from phone verification and browser cookies to payment references and requests made through account support. Where access or eligibility is discussed, it depends on local law.

The raja buaya Privacy Policy covers account details, phone verification, support messages, wallet references, cookie choices and device session records created when you access your account.

We use the phone number linked to your account for phone verification, access checks and support identification. It helps us locate your account without asking for your password or wallet PIN.

Yes. The Privacy Policy covers payment references connected with DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity when those records are used for reconciliation or support.

We may handle browser and device session details connected with account access, including security events. These records help us examine an unfamiliar sign-in or a repeated phone verification step.

Use the account support path and ask for a data copy. Include your linked phone number and the relevant account step so we can identify your record and verify the request.

Yes. Send a correction request through account support with the inaccurate detail and the correct value. We may ask for an account or payment reference before changing the record.

We assess removal requests against active account support, payment reconciliation and legal duties. Records no longer needed for those purposes can be removed or handled in a restricted form.