Reference

Privacy Policy For Your nawasena slot Account

Our Privacy Policy explains what we collect when you open a nawasena slot account, use the iOS App Install path, or move between the lobby and wallet area.

Clear data purposeWallet record contextCookie choicesAccount request path
nawasena slot Privacy Policy For Your nawasena slot Account
HELP WITH REQUESTS

Contact Steps For Privacy Policy Questions

A clear request helps us check the right account without exposing details to the wrong person. Start from the account support path and describe whether you need a copy of your data, a correction, a cookie explanation, or removal of an eligible record. Include the phone number linked to your account and a payment reference only when it helps us locate a DANA, OVO, GoPay, or QRIS entry. We may ask for an account step before discussing private records.

Team online

Account data request

Ask us to locate the personal details connected with your account, including the phone verification record and recent login markers. We first match your request to the account step you provide, then explain which records can be supplied under the Privacy Policy and where local law permits.

Wallet record question

If a DANA, OVO, GoPay, or QRIS receipt appears unclear, share its reference through the account support path rather than sending unrelated personal documents. We use the reference to check status and explain the data held for that payment event under our Privacy Policy.

Correction or removal

Tell us which detail is wrong or which eligible record you want removed. We review the request against account security, active transaction checks, and retention duties. Where local law permits, we correct or remove the record and explain any data that must remain.

DATA HANDLING

What We Protect Across Your Account

Privacy is tied to each practical account action, not just a page of definitions.

Account details

We use your submitted contact details and phone verification result to create and protect your account.

Device signals

Browser type, device settings, session time, and the iOS App Install path may create technical records.

Cookies

Cookies can keep your session choice available and help us understand basic page performance.

Payment references

A DANA, QRIS, OVO, GoPay, bank transfer, or virtual account reference lets us match a receipt to the correct account…

Account security

Phone verification before account access, session checks, and limited device signals help reduce unauthorised entry.

Retention and changes

We retain account, security, and transaction records only for operational, dispute, or legal needs.

Privacy Policy Answers For Indonesia Accounts

These Privacy Policy answers cover the account actions you are most likely to question before opening access from Indonesia. They explain what we record during phone verification, how wallet references are handled, what cookies do, and how to send a request. If your situation is not listed, use the account support path and describe the exact record or session involved.

It covers personal details, phone verification, device signals, cookies, account security events, payment references, retention, and requests to access or correct data. It applies to your nawasena slot account and related sessions where local law permits, with eligibility depending on local law.

DANA and QRIS references help us match a receipt with the correct account event and check a payment status when you contact support. We keep the reference for reconciliation and dispute handling, not as a broad record of unrelated wallet activity.

Use the account support path and state that you are making a data access request. Include the phone number linked to your account and enough session detail for matching. We verify the request before explaining which records can be provided under the Privacy Policy.

Yes, you can identify the detail that is inaccurate and ask us to correct it. We compare the request with your account step and security checks before making a change. Where local law permits, we update the record and confirm what was changed.

Cookies can preserve a session choice and provide basic page-performance signals. They do not replace phone verification or your account credentials. You can clear or restrict them through your browser settings, though a later visit may require another account or session check.

We keep payment references and related account records for as long as they are needed for service operation, receipt matching, disputes, security, or legal duties. When they are no longer needed, we remove or anonymise them where local law permits.

Do not post the detail publicly or send your password. Use the account support path, describe the incorrect record, and include a safe account identifier or payment reference only when relevant. We check the request, protect the account, and explain the next Privacy Policy step.