Reference

planet 4d Privacy Policy In Plain English

Your account details, wallet status and lobby activity receive clear handling rules under the planet 4d Privacy Policy.

Account dataWallet detailsCookie choicesAccess requests
planet 4d planet 4d Privacy Policy In Plain English
HELP WITH REQUESTS

Get Privacy Help Near Your Account

A clear contact route matters when you want to ask about your Privacy Policy rights or correct an account record.

Account help path Use the account help route for a Privacy Policy question, access request or correction. We can ask you to confirm your phone verification step before discussing account data, especially when the request concerns a login or a device you no longer use.
Wallet status question For DANA, OVO, GoPay or QRIS records, send the payment reference shown in your account rather than a wallet password. This lets us check the stored status and explain which payment detail is retained under the Privacy Policy.
Data change request Ask us to correct a name, phone detail or other account record through the available contact path. We review the request against your account access details and explain if a record must remain for security or legal reasons.
DATA HANDLING

Protecting Details From Login To QRIS

We keep the Privacy Policy practical by connecting each data use to an account action you can recognise.

Account records

We use account details to create your access record, confirm phone verification and respond to account requests. A request to change those details may need a matching login step so we do not reveal or alter private data for the wrong person.

Payment references

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference can help us match a receipt with an account event. We use the reference for status checks and do not need your wallet password to investigate it.

Device signals

When you move from a mobile browser to desktop, we may record device or browser signals linked to login protection. These signals help identify unusual access and support a request when your usual phone or device is unavailable.

Cookies

Cookies can remember a session setting or help us understand whether a privacy choice has been applied. Your browser controls can remove stored cookies, although doing so may require you to repeat account access steps.

Retention choices

We keep records only for the period needed for account security, payment status checks, support handling or obligations that apply where local law permits. You can ask why a particular record remains and what deletion options are available.

Security contact

If you suspect that someone accessed your account, use the account help path and change your account access details when prompted. Include the affected device or login time, but never send a DANA, OVO or GoPay password.

Privacy Policy Answers For Your Account

These Privacy Policy answers focus on the questions we expect you to ask before opening an account or checking a wallet record. They cover collection, cookies, access, correction and contact steps without separating the policy from the account actions you actually take. If your situation is not listed, use the account help path and refer to the relevant phone verification or payment reference.

It covers account details, phone verification, login and device signals, cookies, support messages, payment references and retention. It also explains how you can ask for access or correction, and how local requirements may affect a request where local law permits.

Phone verification helps connect an account request with the right account and supports protection during login changes. We may ask you to repeat that step before discussing private records, including a DANA, OVO or QRIS payment reference.

Yes. The policy explains how payment references from QRIS, DANA, OVO, GoPay, bank transfer and virtual account activity may be used to match a receipt or status. We do not need your wallet password for that check.

Use the account help path and ask for access to your account data under the Privacy Policy. Include the phone detail connected with your account, then complete any identity check needed before we discuss or provide private records.

You can request a correction through the available contact route. Tell us which account detail is wrong and provide the matching account step or phone verification record. We will explain any reason a specific history must remain stored.

Cookies may retain a session setting or record that you made a privacy choice. Your browser can remove them, but you may need to repeat login or consent steps afterward. The Privacy Policy explains which cookie use applies.

You may ask what deletion options apply to your account records through the account help path. We first check the request and explain whether security, payment status or another legal need requires a record to remain.