Reference

Privacy Policy for Your play4d Account

play4d Privacy Policy explains how we collect, use and protect the details connected with your account, device and wallet activity.

Account dataWallet detailsDevice accessPolicy requests
play4d Privacy Policy for Your play4d Account
CONTACT ROUTES

Get Privacy Help Beside Your Account

A clear contact path matters when you want to ask what a record means or correct an account detail.

Account support form Open the support form after signing in and select the privacy subject.
Access questions If you cannot reach your account, describe the sign-in step that stopped working and…
Record corrections For a wrong phone number, wallet label or payment reference, send the affected field…
DATA HANDLING

What Your Privacy Settings Cover

We separate the information needed to operate an account from data used to keep sessions secure and pages working.

Account details

We use your phone number and verification result to connect you with the correct account.

Wallet activity

A DANA, OVO, GoPay or QRIS selection can create a reference, status or support trail.

Cookies and sessions

Cookies and similar device signals help keep your sign-in session working and remember essential page choices.

Security checks

Before we reveal account data or change a phone-linked detail, we may ask you to complete an account check.

Retention choices

We keep records only for the period needed for account support, security, dispute handling or legal duties.

Your requests

You can ask what personal data we hold, request a correction or ask how a record is used through the…

Privacy Policy Questions for Indonesia

These answers address the searches we hear most often about the play4d Privacy Policy. They cover the account step, device data, local wallet references and ways to request action. If your situation is not listed, use the signed-in support form and describe the specific record or access problem without including unnecessary payment credentials.

It covers account details, phone verification, device and session data, support messages, and wallet references connected with DANA, OVO, GoPay or QRIS. It also explains purposes, retention, security checks and the routes available for access or correction requests.

Phone verification helps connect your access request to the correct account and protects personal details from disclosure. We may use the verification result when you ask about account records, change a phone-linked field or raise a wallet status question.

Yes. A DANA or QRIS selection can create a payment reference and status event associated with your account. We use that record to investigate your request and confirm the correct account, while the payment provider handles its own separate data practices.

Sign in, open the account support form and select the privacy subject. State whether you want a copy, correction or explanation, then provide the minimum account detail needed to locate the record. We may complete an identity check before responding.

Yes. We describe essential cookies and device signals used to keep a session active, remember necessary choices and identify unusual access. Your phone browser may create different technical records from a desktop browser, even when both open the same account.

You can submit a deletion request through the signed-in support route. We assess which records can be removed and which must remain for security, dispute handling or legal duties. The outcome depends on local law and the status of the account record.

Use the account support form and identify whether the issue concerns DANA, OVO, GoPay, QRIS, bank transfer or a virtual account reference. Do not send a password or full payment credential. We match the request with your verified account before discussing details.