Reference

Open Privacy Policy Before Account Access

Your account details, wallet references and device activity are handled under the sinar777 Privacy Policy, so you can see what we collect before opening an account.

Account dataWallet referencesCookie choicesMobile browser path
sinar777 Open Privacy Policy Before Account Access
CONTACT ROUTE

Reach Us About Your Privacy Policy

A clear contact path matters when a record looks unfamiliar or your privacy request needs checking. We ask you to contact us through the support route displayed after account sign-in, with the phone or account detail used during registration. This helps us confirm the request before discussing account data, whether you are checking a QRIS receipt reference from Makassar or a mobile sign-in record.

Team online

Account privacy request

Use the support path inside your signed-in account to ask what personal records we hold, why a record exists, or which policy section applies to your request.

Wallet record question

Send the relevant DANA, OVO, GoPay or QRIS reference through the account support route. We can use that detail to locate the matching privacy record.

Access concern

If a new device opens the account or a phone verification step looks unfamiliar, contact support from the account page so we can check the access record.

DATA PRACTICE

Browse How We Handle Account Data

Privacy controls work best when each account step has a clear purpose. We connect phone verification, sign-in records and wallet references to the account they belong to, while cookie settings help us…

Account creation

When you open an account, we collect the details needed to create your profile and complete phone verification. We use those details to identify the account during later privacy requests.

Cookie controls

Cookies can keep a browser session working and record selected preferences. Your browser settings provide a way to restrict cookies, although some account access functions may then need another check.

Wallet references

A DANA, OVO, GoPay or QRIS reference may be stored beside an account payment status. We use the reference to match activity, not as a substitute for your wallet credentials.

Session security

Device and sign-in details help us spot unusual account entry. A new mobile browser may trigger phone verification before we discuss records or allow the session to continue.

Retention periods

We keep personal records for the period needed for account operation, legal duties, security checks or disputes. After that purpose ends, deletion or further restriction may apply.

Change requests

You can ask us to correct account details, explain a data use or request deletion where local law permits. Include your account contact so we can verify the request safely.

Find Privacy Policy Answers Quickly

These Privacy Policy answers address the account, device and wallet questions we hear most often. If your case involves a particular sign-in, phone verification event or payment reference, use the signed-in support path so we can check the relevant record.

The sinar777 Privacy Policy covers account details, phone verification, cookie preferences, device access, security records and wallet references linked with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

Phone verification helps connect an account request to the correct account holder and supports safer access from a new device. We may use the result when checking a privacy request or an unfamiliar mobile sign-in.

Yes. Send a request through the support route shown after account sign-in, using the phone or account detail attached to registration. We will check your identity before discussing records, where local law permits.

DANA and QRIS references may be stored with an account payment status so we can match a request or receipt. We do not treat those references as your wallet password or wider wallet access.

Yes. The policy covers relevant mobile browser sessions, cookie choices, device signals and sign-in events used for account security. A move from login toward VIP Baccarat or Aviator may create a session record.

Contact us through the signed-in account support route and describe the detail that needs correction. Include the account contact used during registration so we can verify the request before changing the record.

You may request deletion or restriction where local law permits. Some records can remain for security, legal, payment matching or dispute purposes. We will explain the applicable reason through the account support path.