Reference

Privacy Policy for Your Indonesia Account

nusa228 slot Privacy Policy explains how we handle the account, device and payment details connected with your access to Live Blackjack Salon, Dragon Tiger Live and other lobby…

Clear data purposesPhone verificationMobile account accessIndonesia payment context
nusa228 slot Privacy Policy for Your Indonesia Account
PRIVACY CONTACT ROUTES

Contact Paths For Privacy Questions

A clear contact path helps you act on this Privacy Policy without searching through the lobby. Start from the support channel shown inside your account area and describe the data question in plain English, including the phone number or account reference connected with it. We may ask for a limited verification step before discussing personal records. If a wallet status appears beside a DANA or QRIS transaction, include its reference rather than sending a wallet password or full payment credential.

Team online

Account support

Use the support route inside your signed-in account for questions about your name, phone verification, login history or a request to correct personal details. We check the account reference first, so you can avoid sending private credentials in a message.

Payment privacy

For DANA, OVO, GoPay, QRIS, bank transfer or virtual account records, share the transaction reference and approximate date through the account support channel. We use those details to locate the record while keeping your wallet password and full banking credentials out of the request.

Access questions

If you cannot reach the policy page or account area on a mobile browser, tell us your device type and browser path. We can direct you to the privacy contact route without asking for unrelated game details from Live Blackjack Salon or Dragon Tiger Live.

SIX PRIVACY CHECKS

Six Checks Behind Account Data Care

We keep the Privacy Policy practical by connecting each data category with a specific account task.

Data collected

We may handle your account name, phone number, verification result, login events, device details and transaction references. These records help connect a requested account action with the correct session, wallet status or support question without treating every lobby visit as a request for extra personal data.

Cookie choices

Cookies and similar browser storage can keep a signed-in path working, remember basic session settings and help us detect unusual access. On a phone browser, you can clear site storage through the browser privacy controls; doing so may require phone verification again before account access.

Account security

Phone verification is used before account access, and we may compare login signals such as device or browser changes when a session looks unusual. We will not ask you to disclose a wallet password. Keep your login details private and contact support if an access record is not yours.

Retention period

We keep account, payment-reference and security records only for the period needed for the purpose explained here, account support, dispute handling or a legal requirement. When a record is no longer needed, we remove it, anonymise it or restrict access according to our operational process.

Your requests

You can ask us to access, correct or clarify personal data connected with your account. Send the request through the account support route with a matching account reference. We may verify ownership first, then explain any data that cannot be changed because a legal or security record still applies.

Policy contact

Privacy questions belong with our account support channel rather than a wallet provider or game table. Include the subject of your request, such as cookies, phone data or a QRIS reference. We use the smallest practical set of details to identify the matter and respond.

Privacy Policy Questions Indonesian Account Holders Ask

These Privacy Policy answers focus on the questions you may have before opening or using a nusa228 slot account in Indonesia. They cover the records created during phone verification, mobile access, cookies, local payment references and requests for data changes. If your situation is not covered, use the support route inside your account and avoid including passwords or complete wallet credentials.

It covers account details, phone verification, login and device records, cookies, selected lobby activity, payment references and support requests. It explains why we use each category, how we protect access and how you can ask for a copy, correction or clarification of data linked with your account.

Yes. When you use DANA or QRIS, we may receive a transaction reference and status needed to match the cashier action with your account. The same principle applies to OVO, GoPay, bank transfer and virtual account records; wallet passwords are not needed for this matching step.

We may collect your phone number, verification result, time of the request and related security signals. These details help us confirm the account path before access. If you change devices or clear mobile browser storage, another verification step may be requested to protect the same account.

Use the support channel shown in your signed-in account and state whether you want access, correction or clarification. Add your account reference, but do not send a password or full wallet credential. We may verify account ownership before changing a record or explaining why retention is required.

Cookies or browser storage may remain while needed for session continuity, basic settings and access checks. You can clear them through your Android, iPhone or desktop browser controls. Clearing storage can sign you out and may trigger phone verification when you return to the account.

We retain information for the period needed for the stated account, security, support, dispute or legal purpose. Payment references and login records may need a different period from cookie data. When retention ends, we remove, anonymise or restrict the relevant record under our process.

Yes. You can read this Privacy Policy and send a data question through the support route, while account access itself depends on local law. We apply the same data explanations to supported Indonesia access where local law permits, including mobile paths from Bandung or other locations.