Reference

Privacy Policy for Your gandum99 Account

Your account details, wallet records and device choices receive a clear explanation here.

Account dataWallet recordsCookie choicesMobile access
gandum99 Privacy Policy for Your gandum99 Account
SUPPORT ROUTE

Request Help Through Your Account Path

A clear contact path matters when a privacy request concerns login, phone verification or a wallet receipt. From your account support route, tell us which record you want checked and include the relevant transaction reference without sending a password. We use the same path for questions about the Privacy Policy, cookie choices or a correction request. Support availability and the active contact route are shown in your account area, including when you reach us from Surabaya on mobile.

Team online

Policy questions

Use the support route shown in your account to ask how we collect, use or retain a particular record. Include your account identifier and the section you are asking about, but leave passwords, wallet PINs and full card details out of your message.

Access requests

If you want a copy of account details linked to your gandum99 profile, request it through support after signing in. We may ask for phone verification before releasing records, helping us send the response to the person connected with that account.

Wallet record checks

For a DANA, OVO, GoPay, QRIS, bank transfer or virtual account question, provide the date and reference shown on your receipt. We use those details to locate the relevant record without asking you to disclose a wallet password.

DATA PRACTICE

Data Choices Across Wallet and Device Use

We handle privacy as an account process rather than a hidden setting. The Privacy Policy explains why we need phone verification, how cookie choices affect a mobile browser, and how transaction records…

Account collection

When you open an account, we collect the details needed to create your profile and confirm phone ownership. We do not ask you to place a wallet PIN or login password inside a support message, and the policy explains each account field's purpose.

Cookie controls

Cookies and similar device storage can help keep a login path working and remember selected settings. On a mobile browser, you can adjust browser controls or contact us about a cookie choice; changing them may affect saved preferences during account access.

Payment matching

A DANA, OVO, GoPay or QRIS reference helps us match a wallet event to the correct account. For bank transfer and virtual account records, we use the reference and status needed to investigate a mismatch, not unrelated wallet credentials.

Account security

Phone verification helps protect account access when you sign in or ask for account records. If a request concerns a mobile device, wallet status or a Baccarat session, we may verify ownership before discussing details connected to your profile.

Retention periods

We retain account, support and payment references only for the period described in the Privacy Policy or needed for a stated operational and legal purpose. When a record no longer needs retention, handling follows our deletion or anonymisation process.

Change requests

You can ask us to correct inaccurate profile details or explain how a record is used through the account support route. We review the request against your account and applicable rules, then respond where local law permits and verification is complete.

Privacy Policy Questions About gandum99

These answers address the policy searches you are most likely to make before opening an account. They focus on account records, local wallet references, device choices and requests sent through support. If your situation is different, use the account contact path and identify the relevant Privacy Policy section so we can check the correct record.

The gandum99 Privacy Policy covers account creation, phone verification, login activity, cookie settings, support messages and payment references. It explains how we use those records for account access, status checks and requests, with access handled where local law permits.

Phone verification helps us connect an account request with the correct account holder and reduce mistaken disclosure. We may use it before discussing profile records, a QRIS receipt or a request to change account details, as described in the Privacy Policy.

Yes. The Privacy Policy explains how we handle DANA and QRIS references received during an account transaction. We use a reference and status to match the event, while your wallet PIN and separate wallet login remain outside a support message.

Sign in and use the support route shown in your account to ask for a copy of linked account records. Include your account identifier, complete any requested phone verification and avoid sending passwords. We process the request where local law permits.

You can request a correction through the account support path and identify the field that needs changing. We may verify ownership before making an update, then assess the request against the Privacy Policy and applicable rules before responding.

The Privacy Policy explains that cookies or device storage may support login continuity and saved settings on a mobile browser. You can adjust browser controls or contact support about a preference, though changing cookies may affect parts of the account path.

Retention depends on the record and the purpose stated in the Privacy Policy. DANA, OVO, GoPay, QRIS, bank transfer and virtual account references may be kept for account matching, support checks or applicable legal needs before deletion or anonymisation.