Reference

Open sigra369 Privacy Policy Clearly

sigra369 Privacy Policy shows what we collect when you create an account, check DANA or QRIS status, and move between the casino lobby and your wallet.

Clear data choicesWallet record contextAccount security stepsPrivacy request path
Explore the lobby Read FAQ
sigra369 Open sigra369 Privacy Policy Clearly
PRIVACY HELP

Reach Support About Your Privacy Policy

A clear support path matters when a privacy question affects your account or wallet record. Open the support link from your account area and include the email or phone detail connected to your profile, without sending a password or one-time code. We can use the account context to locate a DANA, OVO, GoPay or QRIS reference and explain what information is held. If you cannot access the account, describe the issue without sharing secret login details.

Team online

Account support route

Use the support link beside your account area for a Privacy Policy question. Include your registered contact detail and a short description, while keeping passwords, verification codes and wallet PINs private.

Wallet record query

If a DANA, OVO, GoPay or QRIS reference appears in your request, share its date and visible status only. We can then connect the privacy question to the correct payment record without asking for secret credentials.

Access concern

When login access stalls, use the account support route and explain whether the issue affects phone verification, a device session or a privacy request. We will use the details you provide to locate the right account context.

DATA PRACTICE

Explore The Privacy Controls We Use

Privacy choices work best when they match real account actions. We separate identity details, wallet references, device signals and support messages so each request can be understood in context.

Account details

We use the contact details you provide for account access, phone verification and replies to support requests. Check your profile before asking for a correction so we can match the request to the correct sigra369 account.

Payment references

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account entry may contain a reference, amount status and timestamp. We use those records to connect a wallet question with the relevant account event, not to request your wallet PIN.

Cookies and sessions

Cookies and similar session signals can keep account navigation working and help us recognise a returning device. You can manage browser cookie settings, although changing them may affect login continuity or the path from account access to the lobby.

Account security

Phone verification is required before account access, and device or session signals may help us investigate unusual login activity. Never send a password or one-time code through support; tell us if you see an access event you do not recognise.

Record retention

We retain account, payment and support records for as long as needed for the stated service purpose, security checks or applicable obligations. When a record is no longer needed, our handling follows the retention process connected with that data type.

Changes and requests

You can ask what personal data we hold, request a correction or question a stated purpose through the account support link. Include your registered contact detail and the requested change; we may need account checks before acting on it.

Browse Privacy Policy Answers For Your Account

These Privacy Policy answers address the searches we hear most often before an account is opened. They cover the practical points behind phone verification, wallet records, cookies, device access and correction requests. If your situation involves a specific account event, use the support route and share only the details needed to identify it. Access remains subject to local law.

The Privacy Policy covers account details, phone verification, device and session signals, cookies, support messages and payment references. That includes records linked with DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity when those details relate to your account.

Phone verification helps us confirm the contact route connected with your account before access is provided. It also supports account security when a login or device event needs checking. We do not ask you to send a password or one-time code through support.

Yes. The Privacy Policy covers payment references and status details connected with DANA and QRIS, as well as OVO, GoPay, bank transfer and virtual account activity. These records help us investigate a wallet question without needing your wallet PIN or secret credentials.

On mobile, cookies and session signals can support account continuity as you move from login toward the lobby. Browser settings let you manage cookies, but refusing them may interrupt access or require another login. Device signals may also assist unusual-session checks.

You can request a correction through the account support link. State the registered contact detail, identify the field that appears incorrect and explain the requested change. We may perform an account check first, so the update is applied to the right profile.

Retention depends on the type of record and the reason it is needed. Account, payment and support entries may remain for service operation, security checks or applicable obligations. You can ask support to explain the purpose connected with a particular record.

Where local law permits, you can ask for access to personal data associated with your account through the support route. Include your registered contact detail and the scope of the request. We may request reasonable account confirmation before discussing private records.

Related Pages

sigra369 Indonesia FAQ ligaplay77 About Us Access guide