Reference

Open pgs22 slot Privacy Policy

pgs22 slot Privacy Policy shows how we handle your account details while you access Live Roulette Gold, Aviator Crash Game and local wallet steps in Indonesia.

Account dataWallet recordsCookie choicesContact path
pgs22 slot Open pgs22 slot Privacy Policy
CONTACT ROUTES

Check your Privacy Policy questions

A direct contact route helps when a Privacy Policy question concerns your login, wallet record or device session. Start from the account support path and include the email or phone detail attached to your account, plus the date and issue you want checked. For a DANA or QRIS reference, share only the transaction identifier, never a wallet password or one-time code. We use the supplied details to locate the relevant record and reply with the next account step.

Team online

Account data request

Ask us to locate the personal details attached to your account, including phone verification records and login history. We may request an account step to confirm that the request comes from you before sending or changing any private data.

Wallet record check

For DANA, OVO, GoPay or QRIS references, send the account identifier and payment date through our support contact path. We can check how the reference is stored without asking you to reveal a wallet password, PIN or one-time code.

Cookie access help

If cookies affect your login on mobile or desktop, contact us with your device path and browser setting. We can explain which session record is involved, while you remain responsible for protecting the device used to open your account.

DATA PRACTICES

Explore our Privacy Policy controls

We keep the policy practical by linking each data use to an account action: phone verification, login, wallet matching, security checks or support.

Collection purpose

We collect account details for phone verification, sign-in, wallet matching and support handling. Activity labels such as Live Roulette Gold or Volleyball Match Bet can appear in records because they connect a request to a specific account session.

Cookie handling

Cookies can keep a session connected and help us recognise a return from the same browser. Your mobile and desktop paths may create separate signals, and you can adjust cookie settings through the browser used for account access.

Account security

We use phone verification, session checks and device signals to reduce unauthorised account access. Never send us your wallet PIN or one-time code. If a login looks unfamiliar, contact support and include the affected device path.

Record retention

We retain account, payment-reference and support records only for the period needed for account administration, dispute handling, security checks and legal duties. A deletion request may be limited where a record must remain for those purposes.

Request changes

You can ask us to access, correct or clarify eligible personal data by using the account support contact path. Include the account email or phone detail, describe the requested change, and complete any identity check we require.

Local access

Our handling of account access and eligibility depends on local law. If you connect from Yogyakarta or another Indonesian location, we may need to apply a local requirement before confirming an account or data request.

Ask about Privacy Policy access

These Privacy Policy answers cover the account questions we hear around login, cookies, payment references and personal data requests. We keep the wording tied to actual account steps, including phone verification and the support path. If your situation involves a legal requirement or a local access question, the outcome depends on local law.

It covers the personal data used for account creation, phone verification, login, wallet references, cookies, device sessions, support and security checks. It also explains retention and the way you can request access, correction or clarification for eligible records.

Those payment names can appear in account records when you use a local wallet or QRIS reference. We use the reference to match a status question or receipt with your account, while you should keep wallet passwords, PINs and one-time codes private.

Use the account support contact path and provide the email or phone detail linked to your account. Describe the records you want, such as login or wallet references. We may ask for phone verification or another account step before releasing private data.

Yes, you can ask us to correct inaccurate eligible details through support. Include the account identifier, explain what is wrong, and provide the accurate replacement. We check the request against your account before changing records used for login or phone verification.

Cookies can keep a browser session connected and help us recognise account access. A phone and desktop may create different session signals. You can change cookie settings in your browser, but clearing them may require you to complete login or phone verification again.

We keep account, payment-reference and support records for the period needed for account administration, security checks, disputes and legal duties. If you request deletion, some records may remain when a legal or security reason requires continued retention.

Yes. Account access, eligibility and some data requests depend on local law. If you are in Indonesia, we may apply a local requirement before confirming an account action. Contact support with your location context if a policy decision needs clarification.