Reference

dinas 138 slot Privacy Policy

Clear account data choices, wallet records and access requests are set out in the dinas 138 slot Privacy Policy.

Account dataWallet recordsCookie choicesAccess requests
Explore Lobby Read FAQ
dinas 138 slot dinas 138 slot Privacy Policy
CONTACT PATHS

Privacy Help Beside Account Support

A clear contact route matters when a privacy question is connected to a login, phone check or wallet record. We keep policy help close to the account-support path so you do not need to describe the same issue repeatedly. Tell us the account email or phone reference, the data concern, and the action you want; do not send a password or wallet PIN. We will use the details you provide to locate the relevant record and explain the next step.

Team online

Account help

Use the account help route when you want to ask about personal data held with your account. Include your registered contact detail and request type, such as access, correction or deletion. We may ask for an account step to confirm that the request comes from you.

Wallet record query

For a DANA, OVO, GoPay or QRIS record, provide the payment reference and approximate date rather than a PIN. We can check how the reference is stored, whether it is linked to an account status, and what detail may be corrected.

Security concern

If you suspect another device has accessed your account, contact support through the account route and state the device concern. We can review login records, help secure the account path, and explain which security data may be retained for follow-up.

HANDLING DETAILS

What We Do With Your Account Data

Privacy choices work best when the handling process is visible. We separate account identity details from payment references where our operational process allows, restrict internal access by task, and use security checks…

Account creation

When you open an account, we collect the contact details needed for account access and phone verification. We use those details to send account-related messages and connect your request to the correct record. You can ask us what is held against your account.

Phone verification

A phone verification step helps us distinguish an account holder from an unknown requester. If you ask for access or correction, we may repeat an identity check before releasing account data. We will not ask you to disclose a password or wallet PIN.

Device and session data

Opening the lobby on a phone or desktop browser can create session, browser and security entries. These records help us identify sign-in patterns and investigate access concerns. They are not used as a reason to disclose personal data to another account.

Cookies and preferences

Cookies or similar browser storage may remember a session setting, language choice or cookie preference. You can clear them through your browser controls, although clearing session storage may require you to complete the account access step again.

Retention and removal

We keep account, payment-reference and security records for as long as an operational, dispute, security or legal purpose requires. When that purpose ends, we remove or anonymise the record according to our retention process. Ask support to explain the category and reason.

Change request route

To request access, correction or a privacy change, contact us through account help with your registered contact detail and a precise request. We may confirm ownership, identify any data affected, and reply with the action available under local law.

Privacy Policy Questions About Your Account

These Privacy Policy answers address the searches we hear most often about account records, local wallets, cookies and access requests. If your situation involves a specific transaction or device, include its reference when you contact account help. We can then give a more useful response without asking you to share unnecessary personal details.

The Privacy Policy covers account details, phone verification, login and device records, cookie preferences, payment references and security logs. It also explains retention, access requests, corrections and contact steps. Eligibility and access depends on local law, so the policy should be read with your local requirements.

Phone verification helps connect account access and privacy requests to the correct account holder. We use the verification status for account security and support handling. If you ask what is stored, contact account help with your registered phone detail; never include your password or wallet PIN.

Yes. The Privacy Policy covers references connected with DANA, QRIS, OVO, GoPay, bank transfer and virtual account activity. We use those references to match status or investigate a disputed entry. Send the payment reference, not sensitive wallet credentials, when asking about a record.

Use the account help route and state whether you want access, correction or clarification. Add your registered email or phone reference and identify the data category. We may complete an ownership check before responding, and the available action depends on local law and the purpose for retaining the record.

Cookies or browser storage may remember a session setting, language choice or cookie preference. You can clear them in your mobile browser controls. Clearing session data may sign you out and require phone verification or another account access step when you return.

We retain account, payment-reference and security records while an operational, dispute, security or legal purpose remains. After that purpose ends, we remove or anonymise them through our retention process. Ask account help about a specific category and we will explain the relevant handling route.

Yes. Contact support through account help and describe the unfamiliar device, approximate time and account contact detail. We can review available login and session records, help secure the account path, and explain which security data may remain for follow-up where local law permits.

Related Pages

dinas 138 slot Indonesia About Us FAQ Goal Fast Round Access guide