Reference

Open naga33 Privacy Policy clearly

naga33 Privacy Policy shows how we collect, use, protect, and retain details connected with your account, device, and wallet activity.

Account dataCookie choicesWallet recordsRequest support
naga33 Open naga33 Privacy Policy clearly
REQUEST HELP

Ask us about your privacy request

A direct support path helps you ask about a data record without sending sensitive wallet credentials. From your account help area, tell us whether your request concerns access, correction, deletion, cookies, or a payment receipt. We may ask you to confirm the phone number linked to your account before discussing personal data, and we will explain the next step through the available support channel.

Team online

Account data request

Use the account help path to ask what personal data we hold, why we use it, or how to receive a copy. We may confirm your phone before replying.

Wallet record check

If a DANA, OVO, GoPay, or QRIS receipt is linked incorrectly, send the transaction reference through support. We use the account match to investigate status.

Cookie question

Ask support which browser cookies affect your sign-in path and how to adjust them. We can explain the practical result before you change device settings.

DATA PRACTICES

Check naga33 data safeguards

We handle privacy as part of the account path, not as a separate promise. Our records help connect phone verification, sign-in events, wallet status, and support requests without asking you to share…

Data we collect

We may collect your account contact details, phone verification result, sign-in activity, device signals, support messages, and payment references needed to match DANA, QRIS, or bank activity.

Cookie choices

Cookies can keep your session connected and remember selected settings on the mobile browser path. Your browser controls can remove or restrict them, though sign-in may need repeating.

Account security

Phone verification comes before account access, while sign-in records help us spot unusual activity. Never send a wallet PIN, password, or one-time code through support.

Record retention

We retain account, support, and payment records only for the period needed for the stated service, security, dispute, and legal purposes described in this policy.

Request changes

You can ask us to correct outdated account details or clarify how a record is used. Include the phone-linked account path so we can locate the right record.

Access confirmation

For a copy, deletion request, or other privacy request, we may verify that you control the account before releasing or changing personal data.

Find answers about Privacy Policy

These Privacy Policy answers address the searches we hear most often before an account is opened. We focus on account records, wallet references, cookies, device access, and contact steps so you know what to expect from naga33 in Indonesia. If your situation is unusual, use the support path above and describe the specific record or request you want us to check.

It covers personal data linked to your account, phone verification, device sign-ins, cookies, support messages, and payment references from DANA, OVO, GoPay, QRIS, bank transfer, or virtual account activity.

Phone verification helps confirm account control before access and before we discuss personal records. It also helps us connect a support request with the correct account without asking for your wallet credentials.

Yes. The policy covers payment status, reference details, and account matching records connected with DANA, OVO, GoPay, QRIS, bank transfer, and virtual account steps.

Use the account help path and ask for a personal data copy. State the phone-linked account details we can use to locate you; we may confirm account control before sending the response.

Yes. Send a correction request through support and identify the outdated detail. We may verify your account first, then explain whether the change affects phone access, payment matching, or support records.

Cookies can maintain your sign-in session and remember browser settings. You can restrict them through your mobile or desktop browser, but some account access steps may need to be repeated.

Where local law permits, you can ask us to delete eligible personal data through support. Some account, security, payment, or dispute records may need retention for stated legal or operational reasons.