Reference

Open raja5k Privacy Policy With Clarity

raja5k Privacy Policy explains how we collect, use and protect the account details connected with your lobby access, including phone verification and wallet status.

Account accessDevice choicesWallet recordsPrivacy requests
raja5k Open raja5k Privacy Policy With Clarity
REQUEST A HAND

Contact Us When Privacy Questions Stall

A clear support route helps you ask about your Privacy Policy rights without repeating your account story. Start from the account support link, mention the email or phone attached to your profile, and include a payment reference only when your request concerns DANA, OVO, GoPay, QRIS, bank transfer or a virtual account. We use those details to locate the correct record and keep replies limited to the account owner.

Team online

Account support link

Use the support path beside your account area for a Privacy Policy request. Tell us whether you need access, correction or deletion help, and include your registered phone so we can match the request without asking for a wallet password.

Payment status check

If a privacy question relates to a DANA, OVO, GoPay or QRIS record, add the payment reference and date. We can trace the status needed for reconciliation while keeping unrelated account activity outside the support reply.

Login access path

When you cannot reach your account, use the login support route rather than sending identity details through an open message. We may ask for a phone verification step before discussing personal records or changing account contact details.

HOW WE HANDLE DATA

Explore Six Privacy Controls We Use

We handle Privacy Policy requests through practical account controls rather than broad promises.

Account data

We use your registered phone, account identifier and access records to connect you with the correct profile. A phone verification step may be required before we disclose, amend or remove details associated with your account.

Device signals

A mobile browser or desktop session may send device, browser and login-time signals. We use these details to keep account access consistent and identify unusual sign-in activity, not to request your DANA, OVO or GoPay password.

Cookies

Cookies can preserve session choices and help the account page load the right state after you move from login to the lobby. You can manage browser cookie settings, although changing them may require another sign-in.

Account safety

We limit private account responses to the person who can complete the relevant verification step. Support should never need your wallet password, card secret or one-time code to answer a Privacy Policy request.

Retention choices

We retain account, support and payment-reference records only for the period needed for account administration, dispute checks, security review or legal duties. Ask support which record applies and we will explain the reason for continued retention.

Change requests

You can ask us to correct an account detail, provide a copy of relevant records or explain a data use. Include your registered phone and request type; we may verify ownership before making any change.

Find Answers About raja5k Privacy Policy

These Privacy Policy answers focus on the questions you may have before opening an account or returning to the lobby from Indonesia. We explain the data connected with login, device use, cookies, local wallet references and support requests in direct terms. If your situation is not covered, use the account support path and include only the details needed to locate your profile.

The raja5k Privacy Policy covers account details, phone verification, device and browser signals, cookies, support messages and payment references. It explains why we use each category, how we protect access and how you can ask for access, correction, deletion or clarification.

No. Our Privacy Policy concerns the payment reference and status needed to reconcile your account, not your DANA, OVO or GoPay password. QRIS, bank transfer and virtual account checks likewise use transaction details needed to identify the relevant payment step.

Phone verification helps us connect a request with the correct account before discussing private records. We may ask for it when you request a copy, correction or account change, especially after a mobile or desktop login cannot be confirmed.

Use the account support path and state that you want a copy of your personal data under the Privacy Policy. Add your registered phone and the record type you mean, such as login, support or QRIS payment status, then complete ownership checks.

Yes, you can request a correction or deletion through account support. We first identify the relevant record and may verify your phone. Some payment, security or legal records may need to remain for the stated retention purpose, and we will explain that basis.

Cookies can keep a browser session and selected account state available as you move from login to the lobby. You can change cookie settings in your browser, but the Privacy Policy notes that doing so may clear the session and prompt another sign-in.

The Privacy Policy is written for supported Indonesia access, including your account and payment records when local access is available. Eligibility depends on local law and applies where local law permits; contact support if your location or account status needs clarification.