Reference

play303 Privacy Policy For Your Account

The play303 Privacy Policy explains what we collect when you open an account, use the lobby, contact support or choose DANA, OVO, GoPay and QRIS.

Clear data purposesWallet record contextAccount request pathIndonesia access wording
play303 play303 Privacy Policy For Your Account
CONTACT THE DESK

Privacy Help For Login And Wallet Questions

A clear contact path helps when you want to ask about the Privacy Policy, correct account details or understand a wallet record.

Policy questions Ask us which account details are held, why they are needed and how they relate to the Privacy Policy. Include your registered phone number in the account contact form, but never include your password or one-time verification code.
Wallet receipt check For a DANA, OVO, GoPay or QRIS query, attach the payment reference or receipt detail shown by your wallet. We use that reference to locate the account event rather than requesting unrelated personal details.
Account correction If your phone detail or account record needs correction, tell us what appears wrong and what should replace it. We may ask for an account check before changing the record, helping prevent another person from taking control.
DATA CONTROL ROOM

What We Handle Behind The Policy

We keep the Privacy Policy practical by connecting each data type to an account task. Phone verification supports account access, device signals help us spot unusual sign-in behaviour, and payment references help…

Account details

When you open an account, we handle the details needed to create and maintain that account, including your phone verification status. We use the record to connect your sign-in activity with the correct account and to respond to account-related requests.

Device and session data

A browser or mobile device may send session and device signals when you sign in. These signals help us recognise unusual access patterns, protect the account and investigate a login concern without treating every device change as a policy breach.

Cookie choices

Cookies can support sign-in continuity, session security and basic page settings. You can manage cookies through your browser controls, although changing them may affect account access steps or require you to sign in again on that device.

Payment references

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account event may create a reference, amount and status record. We use those details to match a receipt to your account and resolve a missing or pending wallet status.

Retention and closure

We retain records for as long as needed for the stated account, security, support and legal purposes. If you ask about closure or removal, we explain which records can be handled and which may need to remain for those purposes.

Security requests

If you suspect that another person accessed your account, contact us through the account support path promptly. We may check phone verification, recent sign-in details and payment references before helping secure the account or correct its record.

Privacy Policy Answers For play303

These Privacy Policy answers address the account questions we expect before you open an account or connect a local wallet. We keep the wording tied to real actions: phone verification, browser sessions, wallet receipts, account correction and contact requests. Where access or eligibility is discussed, it depends on local law.

The Privacy Policy covers details connected with your account, sign-in, phone verification, device sessions, cookies, support requests and payment references. It explains why we handle those records, how they support account security and how you can contact us about access, correction or retention.

We use phone verification to connect account access with the correct person and to help detect unusual sign-in activity. It also gives our support desk a practical account reference when you ask about a login, a data correction or a wallet status.

Yes. The Privacy Policy covers payment references and status details created when you use DANA or QRIS, as well as OVO, GoPay, bank transfer and virtual account routes. We use those records to match a receipt to your account and investigate a payment question.

Use the account support path and state which detail appears incorrect, such as a phone record or account contact detail. We may request an account check before making a change. Do not send your password or one-time verification code with the request.

Cookies may keep a browser session available, support security checks and remember basic page choices. You can manage them through your browser settings. If you remove or block them, you may need to sign in again or repeat a session step.

We keep each record only for the period needed for its stated account, security, support or legal purpose. The period can differ between a sign-in record, a wallet reference and a support request. Contact us if you want the retention basis for your record.

Start with the support route connected to your account and describe whether your request concerns access, correction, deletion or a payment reference. Include only the details needed to locate the record. We will explain the next account step and any local-law condition.