Reference

Privacy Policy for Your Account Path

Our nagahitam Privacy Policy explains what we collect when you create an account, verify your phone, browse Cendrawasih Wild Slots or use a wallet.

Account dataWallet recordsDevice sessionsCookie choices
nagahitam Privacy Policy for Your Account Path
CONTACT ROUTE

Get Privacy Policy Help Near Login

A clear contact path matters when you need to ask about personal data rather than a game screen. If login blocks your request, start with the support link shown on the login page and include the account detail we ask for; do not send a password or wallet PIN. Once you reach the account area, the support path beside wallet status can help us locate a payment reference without exposing unrelated records.

Team online

Login support

Use the support link beside the login form when you cannot reach your account. We can explain which identity detail is needed to locate a Privacy Policy request, while you keep your password, PIN and one-time codes private.

Wallet records

For a DANA, OVO, GoPay or QRIS data question, mention the transaction reference shown in your account. We use that reference to narrow the search instead of asking you to resend a full wallet statement.

Data requests

Ask for access, correction or removal through the support contact path displayed in your account area. Include the email or phone detail connected to nagahitam, and we will explain the checks required before changing personal records.

HANDLING DETAILS

What Our Privacy Policy Covers

Our handling follows the account journey rather than collecting every possible detail.

Data collected

We collect details you enter for an account, phone verification results, login events, device signals and activity needed to provide…

Wallet references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity can leave a reference, amount and status connected to your…

Cookies and devices

Cookies can retain session settings on a mobile browser, while device signals help us recognise an unusual login.

Account security

Phone verification comes before account access where that step is requested.

Retention timing

We retain personal data only for the period needed for the stated account purpose, payment reconciliation, security checks or applicable…

Changes and contact

To request a copy, correction or deletion, contact us through the support path shown after login or on the login…

Privacy Policy Answers for Indonesia

These Privacy Policy answers focus on the questions we expect before an account is opened: which details are collected, why wallet references appear, how cookies affect a device and how to ask for a change. If your question involves access or eligibility, the answer depends on local law and the current account requirements shown to you.

It covers account creation, phone verification, login activity, device signals, cookies, wallet references, support requests and retention. It also explains how to ask for access, correction or deletion of personal data, subject to ownership checks and requirements that depend on local law.

Phone verification helps connect an account to the contact detail supplied during registration and supports account protection before access. We record the verification result and related security event, not a request for your password, wallet PIN or one-time code.

Yes. The Privacy Policy explains how we handle payment references and status connected with DANA, QRIS, OVO, GoPay, bank transfer and virtual account activity. The payment provider may keep separate records under its own terms, so check that provider’s policy too.

You can ask through the support contact path shown on the login page or inside your account area. Include the connected phone or email detail, and we will verify account ownership before explaining which records can be supplied and in what format.

Send a correction request through the account support path and identify the field that needs changing. We may ask for an account check before updating it, especially when the change affects phone verification, wallet status or a payment reference.

Cookies can keep a login session, selected settings and basic browser preferences available while you move through the account path. Clearing them may sign you out or reset those settings. You can also review browser controls before returning to the lobby.

You may submit a deletion request through the support route shown on the login page or after login. We will verify ownership and explain what can be removed. Some payment, security or legal records may need to remain where local law permits.