Reference

Open Your raja akurat Privacy Policy

The raja akurat Privacy Policy explains how we collect, use, protect and retain data when you open an account, verify your phone or reach the lobby from Indonesia.

Account dataWallet statusCookie choices
Explore Our Lobby Read FAQ
raja akurat Open Your raja akurat Privacy Policy
CONTACT ROUTES

Reach Us About Your Privacy Policy

A clear contact route matters when you want to ask what data we hold or why an account check appeared. Start from your signed-in account help area and include the phone number linked to your account, the relevant date and a short description of your request. Our support team can then match the request to the correct account record without asking you to send a wallet PIN. If you cannot sign in, use the account access path and explain that the request concerns the Privacy Policy.

Team online

Account access

If login stalls, use the account help path and state that you need a Privacy Policy request. We may ask for account details that help us confirm ownership before discussing personal data or changing contact information.

Wallet records

For a DANA, OVO, GoPay or QRIS reference, share the date and reference shown in your account rather than a PIN. We use those details to locate the relevant payment event and limit unnecessary disclosure.

Request follow-up

Ask us to clarify, correct or remove eligible account data through support. Include the exact change you want and a reachable contact path, so we can confirm the request and reply without exposing your records.

DATA PRACTICE

Explore Our Account Data Controls

We keep this Privacy Policy practical by tying each data practice to an account action you can recognise.

What we collect

We may collect your phone number, account credentials, verification status, device details, cookie signals and payment references. These records help connect your account request with the correct sign-in, wallet event or security check.

Why we use it

Account and device data support sign-in, phone verification, payment-status matching, fraud detection and support replies. We do not need your DANA, OVO, GoPay or QRIS PIN to handle a Privacy Policy request.

Cookie handling

Session cookies can keep an account path working between sign-in and the lobby, while security cookies help identify unusual access. You can adjust optional cookie storage in your browser, though some account functions may need session cookies.

Account security

We use phone verification before discussing sensitive account details or changing an account contact path. If a sign-in looks unusual, an additional ownership check may be needed before we disclose or edit personal data.

Data retention

We retain account, payment-reference and support records for the period needed to operate the account, investigate security events or meet legal duties. When a retention reason ends, handling follows the applicable deletion or restriction process.

Your request

You can ask what personal data is held, request a correction, ask about processing or seek deletion where local law permits. Send the request through account help with enough detail for us to confirm ownership safely.

Find Answers About Privacy Policy

These Privacy Policy answers address the searches we hear most often before an account is opened. They explain the records connected with login, phone verification, cookies and local wallet references without turning the page into a general lobby description. If your question concerns a specific record, use the account help path and quote the date or reference shown in your account. We will use that context to locate the right entry.

The raja akurat Privacy Policy covers account details, phone verification, device signals, cookies, payment references and support requests. It explains why we use each category, how we protect account access and how you can ask about, correct or delete eligible data where local law permits.

We may collect your phone number, sign-in details, verification status, device and browser signals, cookie records, support messages and payment references. A DANA, OVO, GoPay or QRIS reference can help us match a wallet event, but we do not ask for your wallet PIN.

Use the signed-in account help path and ask for a personal data access request. Include your linked phone number and the records you want us to locate. We may confirm ownership first, then explain what can be provided under the Privacy Policy and local requirements.

Yes, you can ask us to correct inaccurate account details through support. State the field that needs changing and provide the current account contact path. Before making an edit, we may complete phone or ownership verification to protect your account from an unauthorised change.

Session cookies can keep your sign-in path active while you move between account pages, and security cookies help us detect unusual access. You can manage optional cookies in your browser. Blocking required session cookies may prevent parts of the account path from working correctly.

We retain data while it is needed for account operation, security review, support handling or legal duties. The period depends on the record and the reason it was collected. You can ask support which retention reason applies to a specific account or payment reference.

You can request deletion or restriction of eligible personal data through account help. Tell us which records you mean and include a reachable account contact. We first confirm ownership and then explain whether an operational or legal reason requires particular records to remain.

Related Pages

raja akurat Indonesia waptogel FAQ istanabola About Us