Reference

Open the nagacair33 Privacy Policy

The nagacair33 Privacy Policy explains how we collect, use and protect the details connected with your account, device and wallet activity.

Clear data purposesWallet reference controlsAccount request pathIndonesia access wording
nagacair33 Open the nagacair33 Privacy Policy
REQUEST SUPPORT

Ask us about Privacy Policy requests

A direct request helps us locate the correct record without asking you to repeat account details across several conversations. Use the support route attached to your account when you need a Privacy Policy explanation, a data correction or a question about wallet references. Include your registered phone number only through the account path, and we will use the request context to check the next step.

Team online

Policy request path

Send a Privacy Policy question through the account support route, with the subject of your request and registered phone reference. We use those details to find the relevant record.

Wallet status check

If DANA, OVO, GoPay or QRIS status appears beside an account record, share the receipt reference through support. We can investigate the privacy context without requesting your wallet password.

Login access help

When phone verification or sign-in blocks a data request, use the account help route first. We may ask account-specific questions to confirm that the request comes from you.

DATA PRACTICES

See how Privacy Policy controls work

We keep our Privacy Policy practical by linking each data use to an account action, payment check or security need.

Account records

We use registration details, phone verification results and account activity to maintain access and respond to requests. We do not need your wallet password to check a DANA or QRIS reference.

Device signals

Browser type, device identifiers and sign-in signals can help us spot an unusual access attempt. These checks support account protection when you switch from a phone to desktop.

Cookie choices

Essential cookies keep a valid session and remember necessary settings. If optional cookies are presented, their purpose is shown so you can decide whether those settings remain on your device.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account records may show a reference, amount status or timestamp. We use this limited context to reconcile account requests.

Retention checks

We keep account and support records for the period needed to operate services, resolve disputes or meet legal duties. We periodically assess older records instead of storing them without purpose.

Change requests

You can ask for a copy, correction or deletion assessment through the account support route. We may verify your identity before changing a record or disclosing account data.

Find Privacy Policy answers for your account

These Privacy Policy questions address the checks you are most likely to make before opening an account or sending a wallet reference. We keep the answers tied to actual account steps, device behaviour and local payment records. If your situation is different, use the support route and describe the specific record you want us to check.

It covers account registration, phone verification, device signals, cookies, support records and payment references linked to DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

Phone verification helps connect a request to the correct account and reduces mistaken disclosure. If sign-in access stalls, we may use account-specific checks before discussing your stored details.

We do not ask for your DANA, OVO, GoPay or QRIS wallet password through support. Our records may contain payment references or status details needed to match an account request.

We may process browser, device and sign-in signals to maintain a session and identify unusual access. The mobile path can therefore create security records when you move from login to the lobby.

Yes. Send the request through the account support route and identify the record you want checked. We may verify your phone or account details before providing a copy or making a correction.

We retain records for operational needs, support follow-up, dispute handling and legal duties. When a record is no longer needed for those purposes, we assess it for removal or further retention.

Access depends on local law and is provided where local law permits. The Privacy Policy applies to account and device handling for eligible access, including requests connected with Indonesian payment rails.