Reference

gems 365 Privacy Policy for Indonesia Accounts

The gems 365 Privacy Policy explains what we collect when you open an account, browse Blackjack or Great Rhino, and use DANA or QRIS.

Account data explainedCookie choicesPayment recordsContact request path
gems 365 gems 365 Privacy Policy for Indonesia Accounts
CONTACT ROUTES

Where To Ask About Account Data

A clear support path helps when you want to ask about the Privacy Policy, correct an account record or check why a wallet receipt is still pending.

Policy questions Use our support chat for Privacy Policy questions, including what data we hold, why a phone check is needed, and which cookie setting applies to your mobile session.
Correction requests Ask us to correct an inaccurate name, phone detail or account record through the account support path. We may request a matching account step before changing personal data.
Receipt checks For DANA, OVO, GoPay or QRIS records, share the payment reference and status shown in your account. We can investigate the record without asking for your wallet password.
DATA PRACTICE

Cookies And Account Security On Mobile

We keep this policy practical by linking each data use to a visible account action. Your phone verification supports account access, cookies support page settings, and security signals help us review unfamiliar…

Account collection

We collect account details you submit, including contact data used for phone verification. This lets us connect your login, account requests and payment references without treating unrelated device data as account content.

Payment handling

DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity can create transaction records. We use references and status fields to reconcile payments, receipts and account balance requests.

Cookie controls

Cookies can retain session settings and help us understand whether a page is functioning on your device. You can adjust browser cookie controls, though some account steps may then need repeating.

Device signals

We may use device, browser and login signals to identify unusual account access. These signals support a security check; they are not a request for your wallet PIN or private message content.

Retention period

We keep personal and payment records for the operational, security or legal period connected to their purpose. When a record is no longer needed, our handling follows the retention approach stated in this policy.

Change requests

To request access, correction or deletion where available, contact support chat from your account path. Include the request type and registered phone detail so we can confirm which record you mean.

Privacy Policy Answers For Your Account

These Privacy Policy answers focus on the account, device and payment questions you are most likely to have before opening an account. If your situation needs a record-level check, use the support chat path and provide only the account detail needed to locate it.

It covers account details, phone verification, cookies, device signals, payment references and support requests connected with your use of gems 365. It also explains purposes, retention and available requests.

We use phone verification to connect you with the correct account and reduce mistaken access. The check supports login security and account recovery; access depends on local law and the applicable account conditions.

Yes. The Privacy Policy covers transaction references, receipt details and status changes created when you use DANA or QRIS, as well as OVO, GoPay, bank transfer and virtual account routes.

Open support chat from your account area and state whether you want access to a record or correction of a detail. Include your registered phone detail so we can confirm the relevant account.

Cookies may keep session settings and help us assess page function on your phone or tablet. You can change browser controls, but disabling some cookies may require repeated login or account steps.

Retention depends on why the record exists, including payment reconciliation, account security and legal needs. We remove or stop using records when the stated operational, security or legal purpose ends.

Yes. Use the support chat linked from your account path and describe the Privacy Policy concern, such as a cookie choice, device signal or payment record. We will route the request for review.