Reference

nagitabet Privacy Policy For Your Account

nagitabet Privacy Policy explains what we collect when you open an account, use the mobile lobby, or connect DANA, OVO, GoPay and QRIS.

Account recordsWallet activityCookie choicesContact requests
nagitabet nagitabet Privacy Policy For Your Account
CONTACT ROUTES

Switch To Clear Privacy Support

A clear contact route matters when a Privacy Policy question affects your account or wallet status. We handle privacy requests through the support path linked from the account area, so you can provide the phone number or account detail connected to the request. If a DANA, OVO, GoPay or QRIS receipt needs matching, include its reference and approximate time rather than sending a wallet password. For account access concerns, use the cashier support route and ask for a privacy request to be recorded.

Team online

Account privacy request

Use the account support path to ask what personal details are held, why they are used, or which account step created a record. Include your registered phone number so we can locate the correct account without asking you to share a password.

Wallet record check

When a DANA, OVO, GoPay or QRIS payment reference appears incorrectly, send the receipt reference through the cashier support route. We compare the account record with the payment status and explain what can be corrected under the Privacy Policy.

Access and correction

If your phone verification detail or account name needs attention, contact support from the signed-in device where possible. We may ask for an account step that confirms ownership before changing a record or discussing private account details.

HANDLING DETAILS

Browse How We Handle Your Records

Privacy work is part of the account flow, not a separate promise hidden from the cashier path.

Account data

We may handle your name, phone number, login details and verification results when you create or access an account.

Payment references

For DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity, we may retain reference numbers, amounts and status signals…

Cookies and browser use

Cookies can remember selected settings and help us understand whether a page request belongs to an active session.

Device security

We may use device type, browser details, sign-in time and related signals to identify unusual access.

Retention timing

We retain account, payment and support records only while they serve the stated account, security, dispute or legal purpose.

Your request

You can ask us to access, correct or clarify personal details through the support path connected with your account.

Ask About nagitabet Privacy Policy

These Privacy Policy answers cover the account questions you are most likely to ask before opening access or checking a wallet record. We keep the route practical: start with your account details, use the cashier path for a payment reference, and contact support when you need a correction or explanation. The policy applies to mobile and desktop sessions, including access from Jakarta and other Indonesian locations where local law permits.

The nagitabet Privacy Policy covers account details, phone verification, login and device signals, cookies, support messages and payment references. It explains why we use each category, how long records may remain, and how you can request access or correction through the account support path.

Phone verification helps us confirm that a request comes from the account holder before we discuss private details or change an account record. It can apply when you open access, recover an account, or ask us to correct information connected with DANA, OVO, GoPay or QRIS.

No. The Privacy Policy describes payment references and status details, not your DANA, OVO, GoPay or QRIS wallet password. When we check a receipt, we use the reference and account context supplied through the payment route so support can investigate without requesting private wallet credentials.

Send an access request through the support path linked to your account and identify the registered phone number. We may complete an ownership check before responding. We then explain which account details can be provided, why some records remain, and how the response is delivered.

Yes. Use the account support route and state which detail is incorrect, such as a phone number or account name. We may ask for a verification step before making a change. Payment references can require a separate receipt check through the cashier support path.

Cookies can retain session settings and help connect page activity with an active account visit. You can manage them through your browser controls. Restricting cookies may require repeated login or phone verification steps, and it can affect pages that depend on an active session.

Yes, the Privacy Policy applies when you access the account and lobby from a mobile browser or desktop browser in Indonesia. Device and browser signals may be recorded for security. Access and eligibility depends on local law, including where local law permits account use.