Reference

Privacy Policy For Your sydney pool Account

sydney pool Privacy Policy explains what we collect when you open an account, access Dragon Tiger or Mega Fishing, and use DANA, OVO, GoPay or QRIS.

Clear data purposesWallet record controlsAccount access requestsIndonesia privacy contact

Explore the lobby Read FAQ

How Privacy Policy Covers DANA And QRIS

sydney pool Service availability depends on jurisdiction. Users are responsible for checking local law before access.

Our Privacy Policy applies to the details you provide during account creation, including your contact details and phone verification before account access. It also covers records created when you use DANA, OVO, GoPay, QRIS, bank transfer or a virtual account, such as payment status, reference details

1
and support correspondence. Device and connection data may help us keep a session linked to the right account when you move from a phone login to the lobby. We use this material for account operation, payment reconciliation, security checks and replies to your requests. We do
2
not describe access as universal: eligibility depends on local law. If a legal requirement changes how we retain or disclose data, we update our handling and this policy page.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

CONTACT ROUTES

Privacy Policy Help Beside Your Account Path

A clear contact route matters when you want to ask about the Privacy Policy rather than a game or wallet result. We connect policy questions with the same account details used for login, phone verification and cashier status checks. Share only the request needed to identify the record, and we can explain the relevant handling without asking you to repeat unrelated account history. Your route remains subject to local law.

Team online

Policy questions

Ask us which account details, device signals or payment records relate to your Privacy Policy question. Include your account identifier and the subject of the request, but do not send a wallet PIN or password.

Wallet records

If your DANA, OVO, GoPay or QRIS receipt appears beside an unclear account status, contact support through the account help path near the cashier area. We use the reference shown in your receipt to locate the relevant record.

Access concerns

When phone verification or a device session prevents account access, tell us the device path and approximate time of the issue. We can review the access request while keeping your password, PIN and authentication codes private.

DATA PRACTICES

Six Privacy Controls Behind Your Account

We handle Privacy Policy requests through practical account controls, not vague promises. Phone verification helps connect a login to your account before access is granted, while device signals help identify unusual session…

Account details

We use the details you enter at account creation to establish your account path and respond to account requests. Check your submitted contact details carefully, because an incorrect phone number can delay verification or a later Privacy Policy request.

Phone verification

Phone verification occurs before account access so we can connect the login attempt with the account record. Keep verification codes private and contact us if a code arrives without your request or if your access path changes unexpectedly.

Device sessions

A move from mobile login to the lobby can create device and connection signals linked to the session. We use those signals for account security and access checks, not as a substitute for your password or phone verification.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity may create reference records used to match a payment with your account. We do not need your wallet PIN to check a receipt or payment status.

Cookies and storage

Cookies or similar storage can keep a session connected to the account path and remember necessary access settings. You can adjust browser controls, although blocking required storage may interrupt phone verification or a return to the lobby.

Retention requests

We retain account, security and payment records for the period needed for operation, dispute handling and legal duties. Ask us to explain a record, correct eligible details or request removal where local law permits, and we will assess the request.

Privacy Policy Questions For Indonesian Accounts

These Privacy Policy answers cover the account steps you are most likely to question before opening access from Indonesia. We address payment references, phone verification, mobile sessions, cookies, retention and contact requests in plain terms. If your circumstances do not fit an answer, use the policy contact route and include the smallest amount of account detail needed for us to respond.

It covers details supplied during account creation, phone verification records, device and connection signals, payment references, cookies, support messages and related security records. It explains why we use them, how retention works and how you can ask about correction or removal where local law permits.

We use phone verification before account access to connect a login attempt with the correct account and reduce mistaken or unauthorised access. We do not ask you to disclose a verification code to support, and you should keep every code private.

Yes. DANA and QRIS activity can create payment references, status records and receipt details linked to your account. OVO, GoPay, bank transfer and virtual account activity can create similar records. These details help us reconcile a payment without requesting your wallet PIN.

The policy covers device and connection signals created when you sign in on mobile or move from login to the lobby. We use them for session continuity and security checks. They do not replace your password or phone verification, and you can ask about an eligible record.

Cookies or similar browser storage may keep necessary account settings and session links available when you return to the lobby. Browser controls can block them, but required storage may be needed for phone verification and account access. The Privacy Policy explains this use.

We keep account, payment, security and support records for the time needed for account operation, dispute handling and legal duties. The exact period can depend on the record and applicable requirements. You may ask us to explain retention or request removal where local law permits.

Use the account support contact path and state whether you want an explanation, correction or removal request. Include your account identifier and the affected record, such as a QRIS reference, but never send your password, wallet PIN or verification code.

Privacy Policy For Your sydney pool Account

Privacy Policy Help Beside Your Account Path

Policy questions

Wallet records

Access concerns

Six Privacy Controls Behind Your Account

Account details

Phone verification

Device sessions

Payment references

Cookies and storage

Retention requests

Privacy Policy Questions For Indonesian Accounts

01 What does the sydney pool Privacy Policy cover?

02 Why does sydney pool need phone verification?

03 Does the Privacy Policy include DANA and QRIS data?

04 Does the Privacy Policy track my mobile device?

05 How do cookies affect my sydney pool account?

06 How long does sydney pool keep my data?

07 How can I request a Privacy Policy data change?

Related Pages