Reference

sutra303 Privacy Policy For Your Account

The sutra303 Privacy Policy explains what we collect when you open an account, browse Live Roulette Gold or use DANA and QRIS, and how we use those details…

Account clarityWallet recordsCookie choicesMobile access
sutra303 sutra303 Privacy Policy For Your Account
CONTACT ROUTES

Privacy Help For Account Questions

A clear contact route matters when you want to understand a record rather than simply change a setting. We ask you to include the account identifier connected with your request, the relevant date, and the specific data question. That helps us locate a login, QRIS reference or device entry without asking you to send wallet passwords or full payment credentials. Use the support path shown in your account area, and we will explain the next verification step before discussing protected information.

Team online

Data request

Ask us what account details we hold, why a record appears, or which category it belongs to. Include your registered contact detail and a short description of the request so we can separate your account from a similar DANA, OVO or GoPay reference.

Correction path

If your phone number, identity detail or account profile is inaccurate, contact us through the account support route. We may ask you to complete a clear account step before changing it, which helps prevent a stranger from taking control through a false correction request.

Wallet record help

For a QRIS, bank transfer or virtual account record you do not recognise, share the date and reference shown in your account rather than a password or complete wallet credential. We use that information to check the event while keeping sensitive payment details limited.

DATA HANDLING

Six Privacy Controls We Keep Clear

Privacy choices should remain understandable while you move from account access to the lobby on a phone or desktop.

Account data

We collect details you submit when opening or maintaining an account, such as contact information and verification responses. We use them to provide account access, match your requests and protect the account. We do not need your wallet password to answer a normal policy question.

Session cookies

Essential cookies help keep a signed-in session connected while you move between account settings and the lobby. Preference cookies may remember a selected language or display choice where that option is available. You can clear browser cookies, though this may sign you out or reset preferences.

Device signals

We may record device type, browser details, approximate connection data and login time to detect unusual access. A change from mobile browser to desktop can trigger an account check. These signals support security review; they are not a substitute for your own login details.

Payment references

A DANA, QRIS, OVO, GoPay, bank transfer or virtual account event may leave a reference, amount and status in account records. We use those fields to match a transaction question and investigate a mismatch. We limit access to the payment detail needed for that task.

Retention choices

We keep information while it supports account operation, security checks, dispute handling or a legal duty. When the reason ends, we remove it or make it less identifiable where practical. A deletion request may not remove records that must be retained for those specific purposes.

Change requests

You can ask us to access, correct or erase eligible information by using the contact path linked with your account. Tell us which record you mean and how we can verify ownership. We will explain any limit before taking action, especially where local law permits only partial changes.

Privacy Policy Questions For Indonesia

These Privacy Policy answers focus on the account actions you are most likely to search for before opening an account or checking a wallet record. We explain the practical route for data access, cookie control, device checks and correction requests without treating a general lobby question as a privacy request. If your situation is unusual, use the account contact path and describe the record clearly.

The sutra303 Privacy Policy covers account details, verification information, cookies, device signals, game activity and payment references. It explains why we use those records, how we protect account access, how long we may retain them, and how you can ask for access, correction or eligible removal.

We record limited DANA or QRIS reference details so we can match an account event, check a wallet status question and investigate a disputed entry. The record is not your wallet password. We use only the payment fields needed for support, security and required account administration.

Yes, you can ask for an account data copy through the contact path shown in your account area. State the registered contact detail and the categories you want, such as login records or payment references. We verify account ownership first, then explain the available format and any lawful restriction.

Send a correction request through the account support route and identify the inaccurate field, such as a phone number or profile detail. We may require a verification step before changing it. This protects your account from unauthorised edits and lets us keep the record consistent across account access.

The Privacy Policy allows us to use device type, browser details and login time to protect access when you move between a mobile browser and desktop. We may request an account check after an unusual change. You can ask us what device-related record is associated with your account.

We retain account data for as long as it supports account operation, security, dispute handling or a legal duty. Once the purpose ends, we remove or anonymise it where practical. Some records may remain for a required period, and we will explain that reason if you request removal.

Use the contact path connected with your account and describe whether you want access, correction, deletion or an explanation of a record. Include the relevant date and reference, but never send a wallet password. Access depends on local law, and we will outline the verification and response steps.