Reference

Privacy Policy for Your play aja Account

Our Privacy Policy explains how we collect, use and protect the details you provide when opening a play aja account, signing in from a mobile device or checking…

Clear data purposesWallet details handled carefullyPhone verification explainedYour request path
play aja Privacy Policy for Your play aja Account
REQUEST HELP DIRECTLY

Where to Ask About Your Privacy

A clear support route helps you act on this Privacy Policy without searching through the lobby. Contact our account-help team when you need to check a phone detail, understand a wallet reference, request a copy of personal data or ask why a record is being retained. Include the phone number linked to your account and a short description of your request, but never send a password or full payment credential. We can also explain the next step when access is restricted where local law permits.

Team online

Account request

Use the account-help path for a data copy, correction or access question. We may ask you to confirm the phone number connected to your account before discussing personal details, so a third party cannot receive your records by mistake.

Wallet reference

For DANA, OVO, GoPay, QRIS, bank transfer or virtual account questions, share the transaction reference and date rather than wallet credentials. We use that limited context to locate the relevant record and explain its status without requesting your private wallet password.

Policy concern

If you believe our handling of your data does not match this Privacy Policy, send the concern through support with the affected account step. We will review the details, identify the applicable record and tell you what action is available under local law.

DATA HANDLING DETAILS

What We Do With Account Information

Privacy controls matter most at the points where your account changes state: phone verification, sign-in, wallet selection and support contact.

Account security

Phone verification helps connect account access with the number you supplied. We use sign-in and device signals to identify unusual access patterns, while you should keep passwords and one-time codes private. If a device is shared, sign out after checking your account.

Payment references

A DANA, OVO, GoPay or QRIS action can create a reference, amount and status record. Bank transfer and virtual account steps can create similar reconciliation details. We use these records to match account activity, resolve disputes and answer receipt questions.

Cookies and devices

Cookies and device signals can remember a session and help us detect repeated failed access attempts. Your browser settings may restrict cookies, although some account steps may then require another sign-in or lose saved session preferences on that device.

Retention period

We retain account, support and payment-reference records only while they support account service, dispute handling, security checks or legal duties. When a record is no longer needed for those purposes, we assess it for deletion or continued restricted storage.

Data changes

You can ask us to correct inaccurate account details or clarify how a record is used. Include the affected phone number and the change you want. We may verify your identity first, then confirm whether the correction can be made under this Privacy Policy.

Who receives requests

Our account-help team handles Privacy Policy questions and routes payment-status matters to the relevant internal process. We do not ask you to disclose wallet passwords. Where a payment partner or legal authority must be involved, we share only the details needed for that request.

Privacy Policy Answers for Indonesia

These Privacy Policy answers focus on the account situations you are most likely to search for before opening or using play aja. They explain what data may be collected, how wallet references are handled, how to make a request and what can affect account access. If your question is not covered, use the account-help route and include enough detail for us to locate the correct record.

It covers data connected with your account, including phone verification, sign-in activity, device signals, support messages and payment references. It also explains cookies, retention, correction requests and the way we respond when you ask about records linked to DANA, OVO, GoPay or QRIS.

We use your phone number to create an account path, complete phone verification and help protect access from an unfamiliar device. It can also help us locate a support request. We will not ask you to send a password or one-time code through a support message.

No. We may receive a payment reference, status and related account details when you use DANA or OVO, but your wallet password remains with the wallet service. The same approach applies to GoPay, QRIS, bank transfer and virtual account references.

Use our account-help path and state whether you want a copy, correction or clarification. Provide the phone number linked to your account and the relevant date or account step. We may verify that you are the account holder before sharing or changing personal data.

We keep records while they are needed for account service, payment reconciliation, support, security checks, dispute handling or legal duties. We then assess whether deletion or restricted storage is appropriate. The exact period can depend on the record type and where local law permits access.

Yes. Ask support which cookie or device signal relates to your question and tell us whether you are using a mobile browser or desktop browser. Browser settings can restrict cookies, but that may require repeated sign-ins or remove saved session choices from the device.

Yes. Requests for account access, correction or deletion depend on local law and on our need to retain certain records for security, disputes or legal duties. We will explain the available route after confirming the account details needed to identify your request.