Reference

Privacy Policy for play1221 Accounts

Our Privacy Policy explains how play1221 uses the details you provide when you open an account, verify your phone, enter the lobby or request wallet support.

Clear data purposesWallet record detailsCookie choicesAccount request path
play1221 Privacy Policy for play1221 Accounts
CONTACT ROUTES

Get Privacy Help Through Your Account

A clear contact route matters when a privacy request is tied to login or a wallet receipt.

Account help Use the account help path for requests about your phone number, login record, device…
Payment reference For a privacy request involving DANA, OVO, GoPay, QRIS, bank transfer or a virtual…
Policy request Ask us to explain a data use, correct an account detail or clarify retention…
DATA PRACTICES

Six Ways We Handle Your Details

Privacy is handled through account steps rather than a single promise on a page. Phone verification helps us distinguish your request from an unknown login, while device and session signals help us…

Account identity

We connect your phone verification result and account details so an access request reaches the right account. If a detail is wrong, contact us through account help and describe the correction; we may verify ownership before changing it.

Device signals

A mobile browser or desktop session can create technical signals such as device type, session time and browser context. We use these signals to examine unusual login activity, not to publish a personal profile about you.

Cookie controls

Necessary cookies help keep your signed-in path and selected page state available as you move through the lobby. Browser settings can restrict optional cookies, while blocking necessary cookies may interrupt account access or request handling.

Wallet references

When you use DANA, OVO, GoPay or QRIS, our records may contain a transaction reference, status and time. We do not need your wallet password for a support check, so never send that password in a message.

Retention choices

We keep information for the period needed to provide account support, examine security events, resolve a payment dispute or meet an applicable legal duty. When a record is no longer needed for those purposes, our process removes or de-identifies it.

Change requests

You can ask about the data connected to your account, request a correction or question a particular use. Start with the support path, include your account reference, and complete any ownership check needed to protect your private details.

Privacy Policy Questions Before Account Access

These Privacy Policy answers cover the questions we expect before you open an account or return from a mobile device. They explain the records connected with login, wallets, cookies and support requests without turning the policy into a general lobby description. If your situation is not covered, use the account help route and ask us to connect your question with the relevant record. Account eligibility and access depends on local law.

It explains how we handle account details, phone verification, device signals, cookies, payment references and support messages connected with your use of play1221. It also describes how to ask about your data, request a correction and contact us when account access depends on local law.

Phone verification helps us link an account request to the correct person and reduce mistaken or suspicious access. If you ask about private account data, we may repeat an ownership check before sharing or changing details connected with your verified phone number.

Yes. The policy covers payment references and status details connected with DANA, OVO, GoPay and QRIS, as well as bank transfer and virtual account records. We use those details to investigate a request, while your wallet password should remain private and never be sent to support.

Cookies can keep a signed-in path, security state and selected page settings available while you use a mobile browser. You can adjust browser controls for optional cookies. Blocking necessary cookies may stop account access or prevent a privacy request from being submitted correctly.

You can request a correction through account help and explain which detail is inaccurate. We may ask for a phone or account verification step before making a change. This protects your record from an unauthorised request and keeps the correction linked to you.

We keep records for the period needed for account support, security checks, payment disputes or an applicable legal duty. After that need ends, our process removes or de-identifies the record where appropriate. Support can explain the purpose connected with a particular retention question.

Start with the support contact shown through your account help path and state that your request concerns the Privacy Policy. Include an account or payment reference only when needed, never a wallet password, and complete the ownership check required for private data.