Reference

Open guru138 Privacy Policy Before Account Access

Our Privacy Policy explains what data we collect when you open an account, sign in, use DANA or QRIS, and move between the casino, sports and game areas.

Account dataWallet recordsCookie choicesSecurity requests
guru138 Open guru138 Privacy Policy Before Account Access
REQUEST HELP DIRECTLY

Contact Support About Your Privacy Policy

A clear support route helps when you need a copy, correction or explanation about personal data held with your account.

Live chat request Open live chat from your account area and ask about a Privacy Policy request, stored account detail or cookie choice. We use the profile contact detail to locate the correct record.
Payment receipt check Send the transaction reference when DANA, OVO, GoPay or QRIS status needs checking. Keep wallet passwords and one-time codes private; the receipt gives our team a safer starting point.
Account access path If sign-in stalls while you are in Semarang or elsewhere in Indonesia, contact support through the account path and explain the device step. We can direct privacy questions without requesting secret credentials.
HOW WE HANDLE DATA

Explore Privacy Policy Controls Inside guru138

We keep the Privacy Policy practical by linking each data area to an account action you can recognise.

Account data

We may hold your account contact details, verification status and sign-in history so we can identify your profile and handle access requests. Review the details shown in your account before sending a correction request.

Payment references

DANA, OVO, GoPay, QRIS, virtual account and bank transfer records can include a reference, amount status and time. We use these details to reconcile activity without asking for your wallet password.

Device signals

A browser or phone may provide session and device signals used to spot unusual sign-in behaviour. These checks support account protection and do not require access to private files, contacts or unrelated apps.

Cookie settings

Cookies can keep a session active and remember selected settings. You can adjust cookie controls in your browser, although removing necessary cookies may require you to sign in again.

Retention requests

We keep records only for the operational, security or legal reason connected to them, then assess whether they are still needed. Ask through live chat for the retention basis linked to your account record.

Changes and access

You may request access, correction or deletion of eligible personal data. Send the request from your account contact route, and we may verify ownership before changing or releasing account details.

Find Answers About guru138 Privacy Policy

These Privacy Policy answers cover the questions we expect before an account is opened or a wallet is connected. They explain the practical path for data access, corrections, cookies, payment references and account security. If your situation is not covered, use live chat and give us the relevant account or receipt reference without sharing a password.

It covers account contact details, sign-in and device signals, cookies, payment references, retention and requests for access or correction. It applies when you use the account path where local law permits.

No. Our payment records are used to match a DANA or QRIS transaction with your account. Do not send a wallet password or one-time code to support; a receipt reference is enough to begin checking.

We may use browser and phone signals to maintain a session and identify unusual sign-in behaviour. These checks support account security and are not a request to inspect private files or unrelated applications.

Yes. Ask through live chat from the account contact path and state that you want a Privacy Policy data access request. We may verify account ownership before preparing eligible records for you.

Keep the DANA, OVO, GoPay, QRIS, virtual account or bank transfer receipt and send its reference through support. We compare that reference with the account record before making an eligible correction.

Use your browser cookie controls to remove or restrict optional cookies. Necessary session cookies may still be required for sign-in, and changing them can return you to the account access screen.

You can request deletion of eligible personal data through live chat. We assess the request against operational and legal retention needs, and access or eligibility depends on local law before any change is made.