Reference

prabu33 Privacy Policy for Your Account

Our Privacy Policy explains how we collect, use and protect the details connected with your prabu33 account, including login records, device signals and wallet activity.

Clear data purposesWallet activity contextAccount request path
prabu33 prabu33 Privacy Policy for Your Account
POLICY HELP ROUTES

Where to Ask About Privacy Policy

A clear contact path matters when your account details or wallet record need attention.

Account request Use the account support path to ask for a copy, correction or deletion of…
Wallet record For a DANA, OVO, GoPay or QRIS question, include the payment reference and approximate…
Access concern If a device or login record looks unfamiliar, tell us through the account help…
DATA CONTROL DETAILS

What Our Privacy Policy Covers

This Privacy Policy is designed around the records we actually need to operate account access and investigate account requests.

Account details

We may collect your name, phone number, login credentials in protected form and account timestamps. A clear phone verification step helps connect the account to you before access, while support requests may add the details needed to answer a specific Privacy Policy question.

Payment references

We record the status and reference needed to match DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. We do not need your wallet password or banking PIN for this matching process, and you should never place either secret in a support message.

Cookies and devices

Cookies and similar device signals can keep a session working, remember selected settings and help detect repeated failed access. You can clear browser data or adjust cookie controls, though some account functions may require a fresh login after those changes.

Security checks

We compare login time, browser details and device patterns to spot access that does not fit your account history. A sign-in from a new phone may prompt another account check, and we use that step to reduce the chance of an unauthorised person viewing your records.

Retention periods

We keep account, payment and support records only for as long as needed for the stated purpose, account protection, dispute handling or legal duties. When a record no longer serves one of those reasons, we delete it or remove details that can identify you.

Change requests

You can ask us to access, correct or delete eligible data through the account support route. We may verify your identity first, explain any record that must remain for legal or security reasons, and confirm the action taken through the contact detail on file.

Privacy Policy Questions About prabu33

These answers address the Privacy Policy searches we hear most often from Indonesian account holders. They cover the records linked with login, mobile use, wallet references and support requests, rather than describing unrelated lobby content. If your situation is not covered, use the account help route and describe the exact record or action you want us to check. For access or eligibility, where local law permits, we will explain the available path.

The prabu33 Privacy Policy covers account details, phone verification, login activity, cookies, device signals, payment references and support messages. It explains why we use each category, how we protect it, how long we may retain it and how you can request access or a correction.

We use your phone number to create and protect the account, complete the clear phone verification step and send account-related replies. It can also help us locate a request about DANA, OVO, GoPay or QRIS without asking you to share a wallet password.

Yes. The Privacy Policy covers the payment status and reference needed to match DANA or QRIS activity with your account. The same approach applies to OVO, GoPay, bank transfer and virtual account records. We do not ask for your wallet PIN or banking secret.

Cookies and device signals can keep your login session active, remember selected settings and help identify unusual access. You can clear them or change browser controls, but doing so may end the current session. The policy still applies when you use a mobile browser.

You can request a copy of eligible account data through the account support route. Tell us the phone number connected with your account and the records you want checked. We may verify your identity first, then explain the scope and any records that must remain.

Send a correction request through account support and identify the inaccurate field, such as a phone detail or account contact record. We may ask for verification before making a change. Payment references are checked carefully so a correction does not disconnect a valid status.

A request may be limited when releasing or deleting a record would weaken account security, affect a payment dispute or conflict with a legal duty. We will explain the reason where permitted and can still help separate removable details from records that must remain.