Reference

Privacy Policy For Your 1131gg Account

1131gg Privacy Policy explains what we collect when you open an account, check wallet status, or access titles such as Auto Roulette Live.

Account dataWallet recordsCookie choicesAccess requests
1131gg Privacy Policy For Your 1131gg Account
PRIVACY HELP DESK

Get Clear Answers About Your Data

A direct privacy request helps us locate the right account record without guesswork. Include your account identifier and the subject of your request, but do not send a wallet password or one-time verification code. Our support path can also connect a payment receipt or wallet-status question to the relevant Privacy Policy process.

Team online

Account requests

Ask us to confirm the personal data linked with your 1131gg account, explain its purpose, or correct a detail that changed after phone verification. We may ask for account checks before discussing records, so your request reaches the right account rather than another person.

Wallet records

For a DANA, OVO, GoPay or QRIS privacy question, share the transaction reference and date shown in your account. We use that narrow detail to trace the relevant record, while we avoid asking you to disclose a wallet PIN, password or verification code.

Access support

If your policy page or account access stalls on mobile, tell us the device path, sign-in step and visible message. We can separate a browser issue from an account-data request, then explain which Privacy Policy choice or verification step applies.

DATA CONTROL ROOM

What We Do With Your Account Data

Privacy controls work best when each record has a clear reason for being present. We use account, device and transaction details to operate requested access, protect sign-in activity and respond to account…

Account creation

When you open an account, we collect the details needed to create your profile and complete phone verification before account access. This lets us distinguish your sign-in from an unknown attempt and gives us a clear record when you ask us to change or remove account details.

Device signals

A mobile browser may provide device and connection signals around sign-in, session protection and page delivery. We use them to identify unusual access patterns and keep the policy page available across your phone or desktop path; they are not a substitute for your account identity.

Cookies

Cookies can remember a session choice, support page operation and help us understand whether a policy page loads correctly. You can manage cookie settings through your browser. Blocking some cookies may require another sign-in or may affect the account path you requested.

Payment records

A selected DANA, OVO, GoPay, QRIS, bank transfer or virtual account rail can create a reference, amount and status record. We use those details to match your requested payment action and answer receipt questions, not to request your private wallet credentials.

Retention choices

We keep information only while it serves an account, security, dispute or legal purpose described in this Privacy Policy. When that purpose ends, records are deleted, anonymised or otherwise restricted where appropriate. A retention request can be assessed against the reason the record exists.

Your contact route

You can ask about access, correction, deletion, cookie choices or the use of a particular record through our support path. Provide your account identifier and a concise request. We may verify ownership first, then explain the available action and any limit required by local law.

Privacy Policy Questions For 1131gg

These Privacy Policy answers cover the account actions you are most likely to check before opening an account. They explain what to send us, how wallet records fit the policy, and what can affect an access request when local rules apply.

The 1131gg Privacy Policy covers account creation, phone verification, sign-in, device signals, cookies, payment references and support requests. It also explains retention, security checks and your routes for access, correction or deletion. Access depends on local law, so some requests may have limits.

We collect the account details needed for setup, phone verification and sign-in protection. When you request a payment action, the related DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference may also be recorded so we can match status and receipts.

Yes. The Privacy Policy covers records created when you choose QRIS, DANA, OVO or GoPay, including a transaction reference and status connected with your request. We do not need your wallet PIN or password for a policy enquiry, and you should not send either.

Contact our support path with your account identifier and state whether you want access to a record or correction of a specific detail. We may verify account ownership before responding. Describe the sign-in or payment step clearly, such as phone verification or a QRIS receipt.

Send a deletion request through the support path and identify the account records involved. We assess the request against active account, security, dispute and legal needs described in the Privacy Policy. Where local law requires retention, we explain why the relevant record cannot yet be removed.

The retention period depends on why a record exists, such as account access, payment matching, security, dispute handling or a legal duty. We do not promise one period for every record. Ask us about a specific DANA, QRIS or account entry and we will assess its status.

Cookies can keep a session active, remember a page choice or help us detect loading problems. You can manage them in your browser, but blocking required cookies may cause another sign-in or prevent a requested account path from working. Cookie questions remain covered by this Privacy Policy.