Reference

gilaslot Privacy Policy For Your Account

Our Privacy Policy explains how gilaslot handles the account details, wallet references and device signals used when you access the lobby in Indonesia.

Clear data purposesWallet details explainedCookie choicesAccount access rights
gilaslot gilaslot Privacy Policy For Your Account
PRIVACY CONTACT

How To Ask About Your Data

A clear contact route helps you resolve a Privacy Policy question without sending sensitive details through an open message. Use the account support path shown on gilaslot, describe the request in plain English and include the account step involved, such as phone verification, sign-in or a DANA receipt reference. We may ask for account confirmation before discussing personal data.

Team online

Account support path

Open the support route from your account area and state whether your request concerns access, correction, deletion or a Privacy Policy question. We use account confirmation before sharing personal details.

Payment reference check

For a DANA, OVO, GoPay or QRIS data question, provide the relevant payment reference rather than a wallet password or full secret credential. This helps us locate the record safely.

Access clarification

If your request concerns eligibility or regional access, tell us the country shown in your account details. We explain the available policy route where local law permits and avoid collecting unnecessary extra data.

DATA PRACTICE

How We Handle Six Data Areas

Our handling process follows the actions you take rather than collecting unrelated personal details.

Account details

We use the details supplied during account creation and phone verification to create your profile, confirm requested access and respond to account-related questions. Please keep those details accurate.

Device signals

Browser type, device information and connection signals can help us recognise unusual sign-in patterns. We use these signals for account protection and do not treat them as a substitute for your identity details.

Cookie settings

Cookies and similar storage can remember session choices and support page operation. Your browser settings can restrict them, although changing those controls may affect sign-in continuity or policy-page preferences.

Wallet references

DANA, OVO, GoPay and QRIS references help us match a payment status to the correct account. We focus on transaction identifiers and status details, not wallet passwords or secret access codes.

Security records

Sign-in events, phone checks and account changes may be retained to investigate access concerns. If we need to confirm ownership, we ask for an account step rather than unnecessary personal documents.

Retention requests

We keep personal data for operational or legal needs, then assess whether it can be removed. You can ask for correction, access or deletion through the account support route where local law permits.

Privacy Policy Answers For Indonesia

These Privacy Policy answers focus on the questions you may have before creating an account from Indonesia. We explain the practical data steps around wallets, devices, cookies and account requests, while keeping regional eligibility tied to the wording where local law permits. For a personal case, use the account support path rather than sharing private credentials in a general message.

It covers account details, phone verification, device signals, cookies, support requests and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity.

Phone verification helps connect an access request to the correct account and supports sign-in protection. We may use the verification event when investigating an account-access concern.

Yes. The policy covers transaction references and payment status linked to DANA and QRIS, as well as OVO, GoPay, bank transfer and virtual account records used for account reconciliation.

We may receive browser type, device details, connection signals and session events. These details help identify unusual sign-in behaviour and keep an account request connected to the right session.

Use the account support path, describe whether you want access or correction, and confirm account ownership when asked. We assess the request against security needs and applicable requirements.

You can request deletion of eligible data through account support. We first check whether transaction, security or legal records must remain, and action is available where local law permits.

We retain information for the period needed to operate account security, match payment status, answer requests or meet a valid legal requirement. Retention can differ by record type and purpose.