Reference

planet 4d Privacy Policy for Your Account

Our Privacy Policy explains how we handle the account details, phone verification and wallet records connected with planet 4d.

Account recordsWallet referencesDevice choicesContact route
planet 4d planet 4d Privacy Policy for Your Account
HELP WITH PRIVACY

Get Clear Answers About Your Data

A privacy question should not be mixed with a general lobby request. Our support path lets you ask about account records, phone verification, device details or a payment reference without sending sensitive wallet credentials. From Jakarta or elsewhere in Indonesia, include your account identifier and the subject of your request so we can route it correctly. Where local law permits, we will explain the available access or correction step.

Team online

Account privacy request

Use the support path connected to your account and state whether you need a copy, correction or explanation of a personal-data record. We may ask for account verification before discussing private details.

Wallet record question

For DANA, OVO, GoPay or QRIS references, include the date and visible transaction reference only. We use that detail to check status without asking you to disclose a wallet password or one-time code.

Security concern

Tell us promptly if a login, phone verification event or device entry does not look familiar. We can review the account record and explain the next privacy and access step.

DATA HANDLING

How planet 4d Applies This Policy

We handle privacy requests through the same account path used for verification and payment-status questions, so the request can be matched to the right record.

Purpose-led records

We collect account and phone-verification details to recognise your account, protect login access and respond to requests. Payment references from DANA or QRIS help us match status without collecting wallet passwords.

Cookies and device signals

Cookies and browser signals can keep a session working, remember selected settings and help identify unusual access. On mobile, you can manage browser permissions and clear stored cookies through device settings.

Account protection

We use login events, verification results and device information to investigate access concerns. Never send a one-time code through support; if an entry seems unfamiliar, raise it through your account contact path.

Retention decisions

We retain account, support and transaction-reference records only for the period needed for the stated service, security and legal purposes. Retention can vary by record type and applicable local requirements.

Correction requests

If your phone number, account identifier or another personal detail is inaccurate, contact us with the change requested. We may verify ownership before editing the record connected with your account.

Who handles contact

Our support team receives privacy questions about account access, device entries, cookies and payment references. Give us the subject and relevant date, and avoid sending wallet passwords or one-time codes.

Privacy Policy Answers for Indonesia

These Privacy Policy answers cover the searches we hear most often before an account is opened or a data request is sent. We explain the practical route for account records, wallet references, cookies, corrections and access questions. If your situation is different, use the support path and describe the specific record without including secret credentials.

It covers personal details linked to your account, phone verification, login activity, device signals, cookies, support messages and payment references such as DANA, OVO, GoPay and QRIS.

We record limited status and reference details so an account action can be matched with a wallet, bank transfer or virtual account event. We do not ask for your wallet password.

Yes, where local law permits. Contact support from your account path, identify the records you want, and complete any ownership check needed before private account data is disclosed.

Send a correction request through support and name the affected field, such as a phone number or account identifier. We may compare the request with phone verification before making a change.

Yes. The policy covers mobile browser sessions, cookies, device signals and login events. You can clear cookies or adjust browser permissions through your phone settings before returning to the account.

Retention depends on the type of record and the purpose for keeping it, including account security, support handling and legal duties. Ask support about a specific record and its available request path.

Some requests may be limited to protect another person, account security or a legal duty. Access eligibility depends on local law, and support will explain the reason and any available alternative.