Reference

Privacy Policy For Your ganool21 Account

ganool21 Privacy Policy shows how we collect, use and protect the details connected with your account, wallet activity and lobby visits.

Account dataWallet recordsCookie choicesPolicy requests
ganool21 Privacy Policy For Your ganool21 Account
REQUEST HELP DIRECTLY

Get Privacy Policy Help Through Your Account

A clear contact route matters when a Privacy Policy question concerns your identity or wallet record.

Account request Open the support path from your signed-in account and state whether you want a…
Wallet reference For a DANA, OVO, GoPay or QRIS question, add the transaction reference and date…
Account access If you cannot reach the account area, explain the sign-in problem through the available…
CONTROL YOUR DETAILS

What Our Privacy Policy Lets You Manage

Privacy choices should be practical, not hidden behind broad wording. We describe the data connected to your account, the reason for each use and the steps for asking us to change it.

Data collection

We collect details needed for account creation, phone verification, sign-in protection and payment matching. Your chosen wallet rail, such as QRIS or DANA, can appear as a transaction reference, while a wallet password stays with the wallet provider.

Cookie settings

Cookies can keep your sign-in session active and help us understand whether a Privacy Policy page loads correctly. You can adjust browser cookie controls, although disabling some cookies may require you to sign in again when moving between account pages.

Account security

We use phone verification and account checks before handling requests about personal data or wallet status. Keep your sign-in details private, and contact us if a device path or account detail looks unfamiliar after you open the lobby.

Data retention

We keep account, payment and support records for the period needed for the stated purpose, dispute handling and legal duties. When a record no longer needs retention, we remove it or separate it from direct account identifiers where permitted.

Correction requests

You can ask us to correct a phone number, contact detail or other account data that is inaccurate. Include the detail that needs changing and use the linked account route so we can verify ownership before making an amendment.

Removal requests

You may request removal of personal data when there is no remaining reason for us to keep it. Some wallet, security or legal records may need retention, and we will explain that limit rather than deleting a required record.

Privacy Policy Answers For Indonesian Accounts

These Privacy Policy answers address the account and payment questions we hear most often from Indonesian customers. We keep the wording tied to actual steps, including phone verification, cookie controls and wallet references. If your situation is different, use the account support path and tell us which data or activity you want us to check.

It covers account details, phone verification, sign-in activity, cookies, support requests and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account use. It also explains why we use each category, how long we retain it and how you can request a change.

No. Our Privacy Policy concerns the account and transaction data needed to match a payment, such as a reference, status, amount and time. Your DANA or QRIS password remains with that wallet service. Do not place passwords or full security codes in a support request.

Use the support path inside your signed-in account and ask for a copy of the personal data linked to your account. Include your linked phone or email, then complete any ownership check we request. Where local law permits, we will explain the available data and any lawful limits.

Yes, you can ask us to correct inaccurate account details, including a phone number or contact record. Send the request through the account support route and describe the exact change. We verify ownership first, then confirm whether the correction was applied or needs further evidence.

Cookies may keep a sign-in session active or help us measure whether a page works properly. Your browser controls can restrict them, but some account steps may then ask you to sign in again. The Privacy Policy explains these purposes without treating cookies as wallet credentials.

We keep payment references for the time needed to match account activity, handle disputes, protect account security and meet legal duties. The period can differ by record type. When retention is no longer required, we remove the record or separate it from direct identifiers where permitted.

You can ask for removal through the account support path and identify the records concerned. We assess the request under the Privacy Policy and local law. Data needed for payment reconciliation, security, disputes or legal duties may remain, and we will explain that reason.