Reference

raja7000 Privacy Policy for Indonesia Accounts

The raja7000 Privacy Policy explains how we collect, use and protect the details connected with your account, including phone verification and wallet records for DANA, OVO, GoPay and…

Clear data purposesWallet record controlsAccount contact pathCookie choices
raja7000 raja7000 Privacy Policy for Indonesia Accounts
CONTACT ROUTES

Get Privacy Help Near Your Account

A clear contact route matters when you want to ask what data we hold or correct an account detail. Use the support path connected to your raja7000 account and include the phone number or wallet reference involved, without sending a password or full payment credentials. We can then locate the relevant record, explain its purpose and tell you which verification step is needed for a change request.

Team online

Account support path

Open the account support route when a phone number, sign-in record or profile detail needs checking. We use the account reference you provide to connect your request with the correct record, then ask for an appropriate verification step before making a change.

Wallet status request

For a DANA, OVO, GoPay or QRIS record, share the transaction reference and date rather than your wallet password. We use those details to check the payment record, explain what data is stored and keep unrelated account information out of the request.

Policy clarification

Ask us about a Privacy Policy section when the wording is unclear or you need to request a copy of your account data. Include your registered phone number so we can confirm ownership before discussing personal details through the support route.

DATA PRACTICES

What We Keep And How We Protect It

We handle policy requests around identifiable account data, wallet references and device sessions as separate records with different purposes.

Account details

We collect details such as your registered phone number and account identifiers to create, locate and maintain your account record. The phone verification step confirms that a requested change is connected to you before we discuss or update personal details.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account records may show a reference, amount status and processing time. We use these fields to match a payment event, investigate a receipt question and avoid requesting your complete wallet credentials.

Device sessions

When you sign in from a phone or desktop browser, we may record device type, operating system, browser details and session timing. These signals help us investigate an unusual login and explain why an account access check was requested.

Cookies

Cookies can keep a session active, remember a language or display choice and help us understand whether a page request belongs to the same browser session. You can manage cookie settings in your browser, though some account functions may then need another sign-in.

Retention checks

We keep personal records for the period needed to operate the account, resolve payment questions, address disputes or meet a legal requirement. When a purpose ends, we assess whether the record can be removed, separated from identifiers or retained for a narrower reason.

Change requests

To request correction, access or removal of eligible personal data, contact support from the account route and identify the record concerned. We may verify your registered phone number before responding, and local legal requirements can affect what we are able to change.

Privacy Policy Answers For Your Account

These Privacy Policy answers address the searches we hear most often from Indonesian account holders. They cover the data connected with a phone-verified account, wallet references, browser sessions and requests sent through support. Read the relevant answer before sharing a payment receipt or asking us to update your details.

The raja7000 Privacy Policy covers account details, phone verification, device sessions, cookies and payment references linked to DANA, OVO, GoPay, QRIS, bank transfer or a virtual account. It explains why we use each type of record and how you can ask about access or correction.

Yes. The Privacy Policy explains that DANA and QRIS records can include a payment reference, status and processing time used to match an account event. Send the reference and date through support, not your wallet password or full payment credentials.

Phone verification connects an account request with the person who controls the registered number. We may use it before discussing personal details, changing an account field or responding to a Privacy Policy request. Where access is discussed, eligibility depends on local law.

The Privacy Policy covers practical session signals such as device type, operating system, browser details and sign-in time. We use them to investigate unusual account activity and explain an access check. This can apply whether you use a mobile browser or desktop browser.

You can send a correction request through the account support route and identify the detail that appears wrong. Include your registered phone number for verification, but do not include a password. We will explain the next step and whether local law affects the request.

We retain records for the operational, payment-dispute or legal purpose that requires them. A payment reference from GoPay or a bank transfer may therefore remain while a question is open. We review whether continued storage is needed when that purpose ends.

Use the support path connected with your account and state whether you want access, correction, removal or a policy explanation. Add your registered phone number and the relevant record reference. We verify account ownership before discussing personal data or applying an eligible change.