Reference

Privacy Policy for Your nabet Account

Our Privacy Policy explains how we handle the account, wallet and device data connected with your nabet access.

Account dataWallet recordsCookie choicesContact route
Explore Our Lobby Read FAQ
nabet Privacy Policy for Your nabet Account
CONTACT ROUTES

Contact Routes for Privacy Policy Requests

A clear contact path matters when you want to understand a record rather than guess what happened.

Ask about a record Use the support route shown in your account to ask what account, device or wallet data relates to a specific event. A DANA, OVO, GoPay or QRIS reference helps us locate the relevant entry without broad requests.
Request a change If your phone, account contact or personal details need correction, send the requested change through the same privacy contact path. We may ask for account verification before editing records connected with wallet activity.
Check access When login or wallet status stalls, tell us which device path you used and what message appeared. We use that context to separate an access issue from a Privacy Policy request and respond to the right concern.
HANDLING PRACTICE

Six Ways We Handle Your Account Data

We apply this Privacy Policy to practical account events, not just a sign-up screen. Phone verification, wallet status, browser access and support requests can create different records, so we describe their purposes…

Account collection

We collect details you provide during account creation and phone verification so we can identify the account connected with a request. The Privacy Policy explains the purpose of each required field before it is used for account access.

Wallet records

Payment references from DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity help us match status and support requests. We use these records for reconciliation and account assistance, rather than displaying them as public account content.

Cookies

Cookies and similar browser storage can remember a session path or maintain a requested preference. You can review browser controls on your device, while changing them may affect how the account area remembers your Privacy Policy choices.

Device signals

We may use browser, device and sign-in signals to detect unusual access and protect the account. Moving from mobile login to a desktop session can create different technical records, which we handle under the stated security purpose.

Retention

We retain account and transaction records only for the period needed for the stated service, security, dispute and legal purposes. When a record no longer has a valid purpose, our handling follows the deletion or restriction process available to you.

Your requests

You can ask about access, correction, deletion or a processing concern through the account support route. We may verify your identity first, especially when a request could expose phone, wallet or transaction data to another person.

Privacy Policy Questions for nabet Accounts

These answers address the searches we expect before an Indonesian account is opened or used. They explain how the Privacy Policy relates to wallet records, phone verification, cookies, mobile access and direct requests. If your situation involves a particular DANA, OVO, GoPay or QRIS entry, include its reference when contacting us.

The nabet Privacy Policy covers account details, phone verification, wallet and transaction references, browser cookies, device signals, security records, retention and requests you send to us. It explains why each category is used and how you can ask about, correct or restrict a record.

Yes. The Privacy Policy applies when DANA, OVO, GoPay or QRIS is selected for an account transaction. We use the payment reference and status needed to match the request, investigate a discrepancy and provide account support without presenting wallet details publicly.

Phone verification links an access request to the correct account and helps us reduce mistaken or unusual sign-ins. Under the Privacy Policy, the verification detail is handled for account access and security purposes, and you can ask support how it relates to a specific request.

You can request a correction through the support route shown in your account. Tell us which detail is wrong and provide enough account context to locate it. We may verify your identity before changing phone, contact or transaction-linked records under the Privacy Policy.

On a mobile browser, cookies or browser storage may keep a session path or preference available between account screens. You can manage these controls in your device browser. Restricting them may change access behaviour, while the Privacy Policy still explains the related purpose.

We retain wallet, account and device records for the stated service, security, dispute and legal purposes, then follow the applicable deletion or restriction process. The exact period can depend on the record type and local requirements, and support can explain a relevant entry.

Start with the privacy contact path available from your account and describe the record or concern clearly. Add a transaction reference, device path or phone-verification context when relevant. Account verification may be required so we do not disclose personal data to the wrong person.

Related Pages

nabet Indonesia Account information Fruit Fiesta Reels Access guide About Us