Reference

Your Data Before the Lobby

Aviator, Bonanza, Sportsbook and live table access all begin with the same privacy step: we collect only the account, device and payment data needed to run your wallet…

Account data explainedDANA and OVO contextGoPay and QRIS recordsCookie choices
qqvictory Your Data Before the Lobby
CONTACT PATHS

Three Ways to Reach Privacy Help

Privacy questions should not feel hidden behind the lobby. We route account-data requests through live chat, email and the account message centre so you can choose the path that fits your situation. If you are in Denpasar using a mobile browser, the same privacy contact options appear after login under Account, Help, then Privacy Request. We may ask for a recent wallet reference or device check before changing sensitive details.

Team online

Live chat

Use live chat from 10:00 to 22:00 WIB for quick privacy questions, cookie settings or account-access concerns. We will not ask for your full password, and we may move complex data requests to email.

Email desk

Send privacy requests from the email linked to your account, especially for data copies, corrections or closure questions. Include your username and the last payment rail used, such as QRIS, not full wallet credentials.

Account message centre

After login, open Account, Help, then Privacy Request to keep the conversation attached to your profile. This helps us confirm device history, support replies and any DANA, OVO or GoPay reference you mention.

ACCOUNT CONTROLS

Six Controls Around Your Account Data

We handle privacy work inside the same account flow you use for login, wallet checks and lobby access.

Data we collect

We collect your username, contact details, login records, device type, IP region and wallet activity. Game names such as Mega Fishing or Super Bingo may appear in logs only to resolve account or transaction questions.

Payment records

DANA, OVO, GoPay and QRIS entries are stored as transaction references, time stamps and status messages. We do not need your full wallet password, and support will direct you away from sharing it.

Cookies and device checks

Cookies help keep your session active, remember language preference and spot repeated failed logins. You can clear browser cookies on Chrome for Android through Settings, Privacy and security, then Clear browsing data.

Access changes

For email, phone or payment-link changes, we compare your request with recent login records and wallet references. This extra step helps prevent a stranger from redirecting recovery messages or altering withdrawal details.

Retention period

We keep account and transaction records only as long as needed for wallet checks, dispute handling, security review and legal record duties. When data is no longer required, we delete or separate it from your profile.

Your request trail

Every privacy request receives a support record with date, channel and action taken. If you ask again later, the team can see the earlier context without making you repeat the same account history.

Privacy Questions You May Search

The questions below focus only on how we handle your account data, payment references, cookies, device records and privacy requests. They are written for the account flow you actually use: registration, login, wallet checks, support contact and record changes. If your issue includes a payment dispute, include the rail name and time so we can connect the privacy request to the right account event.

We collect your username, email or phone, password record, registration time, device type and IP region. If you add DANA, OVO, GoPay or QRIS activity later, we store transaction references linked to your account.

Yes. The policy covers payment references, status messages, time stamps and support records connected to DANA, OVO, GoPay and QRIS. We use those records to confirm wallet activity, resolve disputes and protect account access.

Email us from the address on your account or use Account, Help, then Privacy Request after login. We may ask for your username, phone check and a recent wallet reference before releasing account data.

You can request corrections through live chat, email or the account message centre. For sensitive changes, we compare your request with recent device history and wallet records before updating the profile.

Device and login records help us detect unusual access, repeated failed passwords and account recovery risks. They also help support understand whether a privacy request came from a familiar browser or a new location.

We keep request records for as long as needed to answer follow-up questions, handle disputes and meet record duties where local law permits. Older records may be deleted or separated from your active profile.

Reply to the same email thread or open Account, Help, then Privacy Request and ask for a second check. Include the request date, channel used and the account detail you want us to examine again.