Reference

Privacy Policy For Your garuda138 Account

Our garuda138 Privacy Policy explains what we collect when you create an account, complete phone verification and use the casino, slots or sportsbook areas.

Account recordsWallet activityDevice choicesContact requests
garuda138 Privacy Policy For Your garuda138 Account
CONTACT ROUTES

Privacy Help Beside Your Account Path

A privacy question should have a clear route, so we keep requests close to the account area rather than asking you to repeat your details across unrelated pages. Use the contact path shown in our account help area when you want to ask about stored data, cookie choices or a correction. Include your account phone number only through the protected route, and never send a wallet passcode in a message.

Team online

Account help path

Open the account help route and select the privacy subject when you need to ask about a phone verification record, a login event or the personal details attached to your account. We use the account context to reduce repeated identity questions.

Wallet record request

If a DANA, OVO, GoPay or QRIS reference appears incorrect, describe the date, amount reference and account step through the available support route. We can then compare the privacy record with the transaction status without asking for your wallet PIN.

Access and correction

Ask us to see, correct or explain personal data through the contact route displayed with this Privacy Policy. We may ask for account verification before making a change, because a privacy request must not expose your details to another person.

DATA PRACTICE

What We Do With Your Records

Our handling starts with a practical question: what data is needed for the account action you requested?

Account identity

We use your submitted account details and phone verification result to identify the correct account, answer privacy requests and protect access. If you ask for a correction, we compare the request with the account record before changing a name, phone detail or contact preference.

Wallet references

DANA, OVO, GoPay, QRIS, virtual account and bank transfer activity can create reference data linked to your account. We use those references to check a transaction step, investigate a mismatch and respond to a privacy question about the related record.

Mobile device signals

When you open the account on a mobile browser, we may record device and session signals such as browser type, login time and security events. These signals help protect the session; they are not treated as a replacement for the personal details you provide.

Cookies and sessions

Cookies can keep your login session active, remember a selected page and support security checks. You can manage cookie settings through your browser, although turning some cookies off may interrupt account access or require another phone verification step.

Retention periods

We retain personal and transaction records only while they support the stated account purpose, dispute handling, security checks or legal duties. When a record is no longer needed, our process is to remove it, anonymise it or restrict access where retention still applies.

Your privacy request

You may ask what personal data we hold, request a correction, ask about a deletion route or question a processing purpose through the contact path on this page. Handling depends on local law, and we may verify your account before responding.

Privacy Policy Questions From Indonesia

These answers address the searches we most often expect before someone opens an account or checks a wallet record. They focus on garuda138 Privacy Policy topics: collection, cookies, account access, payment references, correction requests and contact steps. If your question is more specific, use the account help route shown above and include only the details needed to identify the record.

It covers account details, phone verification, login and device signals, cookies, wallet references, support requests and retention. It also explains how we use records connected with DANA, OVO, GoPay, QRIS, bank transfer and account activity across casino, slots and sportsbook areas.

Yes. The Privacy Policy covers transaction references and status details connected with DANA and QRIS, along with OVO, GoPay, virtual account and bank transfer records. We use those details to match an account action, check a mismatch and respond to a related request.

Phone verification helps us connect the person requesting account access with the correct account record and helps protect a session from unauthorised use. The result can be used when you ask for a correction or access request, subject to local legal requirements.

You can send a correction request through the account help route shown with this Privacy Policy. Tell us which detail is wrong and provide the account context requested by the form. We may verify your identity first, and the outcome depends on local law.

Mobile cookies can support login sessions, page preferences and security checks when you use a phone browser. Your browser settings let you manage them, but blocking required cookies may interrupt account access or trigger another phone verification step.

We keep account, transaction and security records while they serve the stated purpose, support dispute handling or meet applicable legal duties. After that period, we aim to remove, anonymise or restrict the record. A specific retention response depends on the record and local law.

Use the account help and contact route displayed alongside this Privacy Policy. Choose the privacy subject and describe the record involved without sending a password, wallet PIN or unnecessary identity documents. We may request account verification before discussing personal data.