Reference

Privacy Policy for Your Account

This page explains what we collect, why we keep it, and how you can ask for changes on nagabet76.

Account dataDevice logsCookie settingsDANA, OVO, GoPay, QRIS

What This Policy Covers

nagabet76 Service availability depends on jurisdiction. Users are responsible for checking local law before access.

We collect the account data you enter, browser and device signals, and payment references from DANA, OVO, GoPay, and QRIS only to confirm transactions, prevent duplicate requests, and answer support tickets. We also keep session logs so we can recognise your login, remember your chosen language,

1
and spot unusual access attempts. Where local law permits, you can ask us to correct, export, or delete selected records after we verify that the account is yours. We share only what is needed with service partners that process messages, store files, or move payment records
2
through the system. We do not use this policy to sell your data, and we do not keep more than we need for disputes, audit checks, or security work. If the law in your region asks for a different retention or disclosure rule, that rule comes
3
first, and we will follow it before any internal preference.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

CONTACT ROUTES

How to Reach Our Team

If you want a copy of the details we hold, a correction, or an explanation of a payment record, contact us through the route that matches your account.

Live Chat Use live chat for quick privacy questions. We can check consent settings, confirm what is stored, or point you to the form for a change request. Keep your registered email ready so we can verify the account before we discuss records.

Email Send a message if you want a copy of our stored account fields or need to correct a name, phone number, or payment reference. Attach the screenshot or transaction code so we can trace the record faster.

Account Form Open the account form when you need a deletion request or a change to what we keep. We compare the request against the login history and the latest device session before we act.

CAREFUL HANDLING

How We Handle Data Safely

We keep data minimised: only what is needed to run your account, process DANA, OVO, GoPay, or QRIS records, and answer privacy requests.

Data Minimisation

We collect only the fields needed to run your account, confirm DANA, OVO, GoPay, or QRIS activity, and answer privacy requests. Extra notes are stripped out before they move beyond the support queue.

Cookie Controls

Cookies remember your session and language choice so you do not reset the page each time. You can clear them in Chrome, Safari, or Firefox, and the policy text remains available.

Account Security

Before we change a profile, we compare the registered email, the latest login device, and a recent account action. That check reduces mistaken edits and keeps requests tied to the right holder.

Retention Windows

We keep logs only as long as needed for account service, dispute handling, or local law. When that period ends, we remove the record or turn it into anonymous form.

Request Changes

Where local law permits, you can ask us to correct, export, or delete selected records. Send the request from the email tied to the account so we can confirm it quickly.

Contact Path

For anything unclear, write through live chat or email and include the account identifier, the device you used, and the payment trail if relevant. We use that detail to locate the right file.

Common Privacy Questions and Answers

These questions cover what we store, when we share it, and how you can ask for edits. If you use mobile first and return on desktop later, or if you move between DANA and QRIS, the same policy still applies to the same account. We answer privacy requests by checking the record against your registered contact details, the latest session data, and any reference number you include.

We collect the details you type in, plus device type, browser data, login time, and support history. If you add DANA, OVO, GoPay, or QRIS references, we keep those codes to match the right transaction and account.

Only where needed to process the record, answer a dispute, or meet a legal request. We pass the minimum data required to the service partner handling the payment trail, and we keep the rest inside your account file.

Yes. Send the registered email, the item you want corrected, and a recent login or payment reference. After we confirm the account belongs to you, we update the record or explain why a field must stay.

We keep it while the account is active and after that only as long as needed for disputes, fraud checks, or local law. When the retention period ends, we remove or anonymise the record.

No. Cookies keep session and preference data, such as language choice and login state. Message content stays in the support record, not in the browser cookie, so clearing cookies does not erase your contact history.

Yes. The same policy covers phone browsers, desktop browsers, and login sessions that move between them. Your device may change, but the account record, consent choice, and request process stay the same.

Use live chat, email, or the account form and include your registered email plus any relevant transaction code. That helps us verify the request quickly and respond to the exact record you want checked.

Privacy Policy for Your Account

How to Reach Our Team

How We Handle Data Safely

Data Minimisation

Cookie Controls

Account Security

Retention Windows

Request Changes

Contact Path

Common Privacy Questions and Answers

01 What data do you collect when I open an account?

02 Do you share my DANA, OVO, GoPay, or QRIS details?

03 Can I ask you to change my stored details?

04 How long do you keep my data?

05 Do cookies store my messages?

06 Does this policy apply on mobile and desktop?

07 How do I contact you about privacy?

Related Pages