Reference

guru600 Privacy Policy For Your Account

guru600 Privacy Policy explains how we collect, use and protect the details connected with your account, including phone verification and wallet status for DANA, OVO, GoPay and QRIS.

Clear data purposesWallet detail handlingPhone verification recordsCookie choices
Explore Our Lobby Read FAQ
guru600 guru600 Privacy Policy For Your Account
CONTACT PATHS

Browse Policy Help Through Your Account

A clear contact route helps you act on this Privacy Policy instead of guessing which detail to send. We ask you to contact support through the account help path when you need a copy of your data, a correction, a deletion request or an explanation of a wallet status record. Include only the details needed to locate your account, and never send a DANA, OVO, GoPay or QRIS PIN.

Team online

Account help

Use the account support path for Privacy Policy questions about your phone verification, login record or the personal details attached to your guru600 account. We may ask you to confirm account ownership before discussing or changing those details.

Payment receipt check

If a DANA, OVO, GoPay or QRIS receipt appears in your account history, send its reference through support rather than a wallet PIN. We use the reference to locate the status record and limit the data shared in our reply.

Policy request

For a data copy, correction or deletion request, state the action clearly and use the contact route shown inside your account. We may verify your phone before completing the request, because privacy changes must reach the right account holder.

DATA PRACTICES

Explore How We Handle Personal Data

The Privacy Policy is supported by working controls rather than broad promises. We separate account records from wallet references where practical, limit internal access to the task being handled and retain records…

Account creation

When you open an account, we collect the details needed to create your profile and complete phone verification. We use those details to identify the account, send account-related messages and prevent another person from requesting changes to your records.

Wallet references

DANA, OVO, GoPay and QRIS can provide a payment reference or status linked to your account activity. We use that limited record to match receipts, investigate a stalled status and keep support replies focused without requesting your wallet PIN.

Cookies

Cookies and similar device storage can remember a session, protect an account sign-in and help us understand whether a page loads correctly. You can manage cookie controls through your browser, although refusing necessary cookies may affect account access.

Device signals

We may record browser, device and network signals connected with a sign-in or security check. These signals help us identify unusual access and troubleshoot a mobile path from login to the lobby without treating your device model as a profile preference.

Retention periods

We keep personal data while it serves account operation, support, dispute handling or a legal requirement described by our policy. When a record is no longer needed for those purposes, we remove it, anonymise it or restrict access according to our retention process.

Your requests

You can ask us to access, correct or delete eligible personal data, or ask why a detail is being used. Send the request through account support; we may request phone verification and explain any lawful reason a record cannot be removed immediately.

Check Common guru600 Privacy Policy Answers

These Privacy Policy answers cover the searches we hear most often before account creation. They explain what we collect, why payment references appear, how cookies work and which account step helps us respond safely. If your situation is not listed, use the policy contact path with a short description and avoid sending wallet credentials.

The guru600 Privacy Policy covers account details, phone verification, device signals, cookies, support records and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. It explains purposes, retention, security steps and ways to request access or correction.

Phone verification helps us confirm that a request about your account comes from the account holder. We may use it before discussing personal data, changing account details or handling a Privacy Policy request. The step applies where local law permits and does not require your wallet PIN.

No. Our Privacy Policy does not ask you to send a DANA, OVO, GoPay or QRIS PIN to support. We may handle a masked wallet detail, receipt reference or transaction status so we can match an account record and investigate a payment question.

Use the account support path and state that you want a copy of your personal data. Include the account contact detail needed to locate your record, but not a wallet credential. We may complete phone verification before sending the response to the confirmed account holder.

Yes, you can request correction or deletion of eligible personal data through account support. We first confirm the account and assess whether a record is still needed for account operation, a payment dispute or a legal requirement. Our Privacy Policy explains any restriction.

Cookies can keep a mobile session active, support account security and help a page load in the intended device path. You can adjust them in your browser settings. If necessary cookies are blocked, sign-in, phone verification or the lobby path may not work as expected.

Start with the account help route shown in guru600 and label your message as a Privacy Policy request. Ask about access, correction, deletion, retention or a payment reference. We will use the smallest useful set of details and may verify your phone before replying.

Related Pages

guru600 Indonesia FAQ Live Baccarat Table Account information Mobile APK Download