Reference

surga19 Privacy Policy, Made Clear

Our surga19 Privacy Policy explains how we handle the account details, device signals and payment records connected with your access to Live Blackjack Diamond, Mahjong Wins Slots and…

Account dataWallet recordsCookie choicesPolicy requests
surga19 surga19 Privacy Policy, Made Clear
CONTACT ROUTES

Privacy Help Beside Account Access

A clear contact route helps when your account details, wallet status or policy request needs attention.

Account request Use the support route beside login when you need to ask what account data…
Wallet record For a DANA, OVO, GoPay or QRIS privacy question, provide the relevant payment reference…
Access concern If a privacy request is affected by sign-in, phone verification or browser behaviour, tell…
DATA HANDLING

How We Manage Your Policy Requests

We keep privacy work tied to real account operations rather than vague promises.

Account details

We use your phone and account details to create access, complete a phone verification step and answer privacy requests.

Security signals

Login time, browser type, device signals and unusual access patterns can be recorded to protect the account.

Cookie controls

Cookies and local browser storage can support sign-in continuity and policy preferences.

Payment records

A cashier reference can show whether a DANA, OVO, GoPay, QRIS, bank transfer or virtual account request is pending or…

Retention period

We keep personal data for the period needed for account operation, security checks, dispute handling or legal duties.

Change request

Ask us to correct eligible account details through the support route beside login.

Privacy Policy Answers for Indonesia

These Privacy Policy answers focus on the questions you may have before opening an account or sending a data request from Indonesia. We explain which records connect to login, phone verification, cookies and local payment rails, along with the steps we use to check ownership. If your situation is not covered here, use the support route beside account access and describe the specific record or request. Availability still depends on local law, so access should only continue where local law permits.

It covers account details, phone verification, login events, device and browser signals, cookie settings, selected lobby pages, support messages and payment references. This includes records linked to DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity.

We use your phone detail to create and protect account access, complete the required verification step and locate the correct record when you ask about Privacy Policy rights. Keep the number current so an ownership check does not stall.

Yes. A DANA or QRIS request can produce a reference, amount, status and timing record. We use those details to match the cashier event, answer a payment question and investigate a missing status without requesting your wallet password.

You can request a correction through the support path beside login. Tell us which account detail is wrong and provide enough information for an ownership check. We assess the request under applicable rules and update eligible records when appropriate.

Cookies and local browser storage may retain sign-in continuity or a policy preference on your device. You can clear them through browser settings. After clearing them, you may need to repeat phone verification or choose your settings again.

We retain payment references for the period needed to operate the account, reconcile DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity, handle disputes and meet legal duties. The period can differ by record purpose and applicable requirements.

You may ask us to delete or restrict eligible personal data through the support route. We first check account ownership and then assess whether a record must remain for security, dispute handling, account administration or legal duties. Access depends on local law.