Reference

raja123 Privacy Policy For Your Account

The raja123 Privacy Policy explains what we collect, why we use it, and how you can manage your account data before opening an account.

Clear data purposesWallet details explainedPhone verification contextIndonesia access rules
raja123 raja123 Privacy Policy For Your Account
CONTACT DATA HELP

Get A Clear Privacy Support Path

Privacy questions should have a direct route, so we separate data requests from ordinary lobby questions. Contact our support channel from the account area and include the phone number linked to your profile, the request you want handled, and any relevant payment reference. We use those details to locate the correct record without asking for a wallet password. You can also ask why a verification check, cookie setting or retention period applies to your account.

Team online

Account data request

Send a request through the account support channel using your registered phone number. We check the account step before discussing personal records, then explain which data can be accessed, corrected or removed under the rules that apply where you are located.

Wallet reference check

If a DANA, OVO, GoPay or QRIS reference appears incorrectly, provide the payment date and account reference rather than your wallet password. We compare the record with the cashier entry and tell you what can be corrected in the account history.

Cookie settings

For cookie questions, tell us whether you are using a mobile browser or desktop browser and which setting concerns you. We can explain the cookie purpose, how it affects login continuity, and which choices remain available without changing your account details.

HANDLING YOUR DATA

How Our Privacy Policy Works Daily

Our privacy process follows the same account path you use: registration, phone verification, login, wallet matching and support.

Account collection

When you open an account, we collect the details needed to create your profile and complete phone verification. We use those details to recognise your login, connect support requests to the right record and apply access rules where local law permits.

Payment matching

A DANA, OVO, GoPay or QRIS reference helps us match a cashier event with your account. Bank transfer and virtual account records serve the same purpose. We review the reference and status, not the private password or security code of your wallet.

Cookies and devices

Our browser cookies can retain a session marker and selected settings on your phone or desktop. Device details may help us spot an unfamiliar login. Clearing cookies can require another login, but it does not erase account records by itself.

Account security

Login records, phone verification and device signals help us examine access that does not match your usual account path. If a security question arises, contact support from the registered account route and avoid sending passwords, wallet PINs or one-time codes.

Retention period

We keep personal and transaction records for as long as needed for account operation, security checks, dispute handling or legal duties. When a purpose ends, we remove or anonymise the record where practical, subject to any continuing requirement that applies.

Changes and requests

You can ask us to correct inaccurate profile details, explain a data use or assess a removal request through support. Include your registered phone number and a precise request. We verify ownership first and reply with the available next step.

Privacy Policy Answers For raja123

These Privacy Policy answers focus on the questions you may ask before creating or using a raja123 account in Indonesia. They cover account records, payment references, browser cookies, data requests and local access conditions. If your situation is not listed, contact support through the account route with the registered phone number.

The raja123 Privacy Policy covers account details, phone verification, login and device records, cookies, support messages, payment references and retention. It explains why we use each category, how we protect account access, and how you can ask about correction, removal or other available data rights.

Phone verification helps us connect the person completing the account step with the correct profile and gives support a way to check ownership. We use the verified number for account security and service contact, not as permission to request your DANA, OVO or GoPay password.

Yes. The Privacy Policy covers QRIS references, DANA, OVO and GoPay status details, plus bank transfer and virtual account records used to match a payment with your account. We may retain the reference and outcome for account support, security checks or legal duties.

Contact support through the account channel and state which profile detail or record you want checked. Include your registered phone number, but never send a password or wallet PIN. We verify account ownership first, then explain whether correction, removal or another request path is available.

We keep data while it serves account operation, payment matching, security review, dispute handling or a legal duty. After that purpose ends, we remove or anonymise it where practical. Some transaction records may remain longer when a rule or unresolved account matter requires continued storage.

Yes. Your mobile browser settings let you clear or restrict cookies, including session markers used to keep login steps connected. Clearing them may require another sign-in and can reset preferences. We still retain account records separately when they are needed for security or legal purposes.

Yes. Account eligibility and access depend on local law. Where local law permits, you can read this Privacy Policy before phone verification and contact support about your records. We assess requests against the rules that apply to your location and explain any limits in our reply.