Reference

Open playstar demo Privacy Policy

playstar demo Privacy Policy explains how we handle the account details you provide before you enter rooms such as Andar Bahar or Rocket Crash.

Account dataWallet recordsDevice accessCookie choices
playstardemo.club page image
ASK OUR TEAM

Contact us about Privacy Policy requests

If a Privacy Policy question affects your account, use the support route shown after sign-in and describe the exact request in your own words.

Account access Ask our support team which account details we hold and why they are linked to phone verification or a sign-in check. We will explain the next account step.
Wallet record For DANA, OVO, GoPay or QRIS questions, share the payment reference rather than private wallet credentials. We use the reference to locate the related record.
Change request Request a correction or removal through the signed-in support path. We may verify ownership first, then confirm what can change under local law and our retention duties.
DATA IN PRACTICE

Explore how playstar demo protects policy choices

Privacy Policy work is tied to ordinary account events rather than hidden profile building.

Collected details

We may hold your contact details, phone verification result, sign-in records, device signals and payment references. We collect them when you take an account action or ask for support.

Cookie settings

Cookies can retain session settings and help us understand whether a page loads correctly. You can manage cookie choices through your browser, although some account steps may then need repeating.

Account security

Phone verification and sign-in checks help us compare an account request with its existing record. Never send your password, PIN or one-time code through a support message.

Retention period

We keep records for as long as needed for the stated account, payment, support or security purpose, then assess whether deletion is allowed under applicable local requirements.

Your choices

You can ask what personal data we hold, request a correction, question its use or ask about deletion. We may need identity checks before changing an account record.

Contact route

Send Privacy Policy requests through the support path attached to your account. Include the affected email or phone detail and request type, but leave passwords and wallet PINs out.

Browse Privacy Policy answers before opening

These Privacy Policy answers cover the searches we hear most often before an account is opened. If your question concerns a particular phone record, QRIS reference or mobile sign-in event, use the account support path so we can check the relevant details.

It covers account details, phone verification, sign-in and device records, cookies, support messages, payment references and how we handle requests to access, correct or remove personal data.

We use your phone number for account identification and verification before access. It can also help support locate the correct record when you ask about sign-in or wallet activity.

Yes. The Privacy Policy covers payment references connected with DANA, OVO, GoPay and QRIS, along with bank transfer or virtual account details needed to match an account request.

We may record technical details such as device type, browser signals, session events and security markers when you move from mobile login to the lobby. These support access and fraud checks.

Use the signed-in support path and ask for an account data access request. Tell us which phone or contact detail is involved; we may verify ownership before responding.

Yes. Send a correction request through support and identify the inaccurate field. We will review the account record, confirm ownership when needed and explain any local-law restriction.

You can ask about deletion through support. We assess the request against account, payment and security record needs, then explain which data can be removed and which must remain.