Reference

neraca4d Privacy Policy Explained

The neraca4d Privacy Policy shows what we collect, why we use it and how you can request changes before opening an account.

Clear data purposesWallet details coveredMobile access explainedContact route included
Explore Our Lobby Read FAQ
neraca4d neraca4d Privacy Policy Explained
CONTACT ROUTES

Get Privacy Policy Help Near Login

A direct support route helps when you want to ask about a record, correct an account field or understand a wallet reference. Use the contact path shown beside the account and cashier areas, and include only the details needed to locate your request. We can then explain the next account step without asking you to post passwords, full wallet credentials or unrelated personal material in a message.

Team online

Account data request

Ask us to identify the account data connected with your login or phone verification. Include your account identifier and a clear request through our support route; do not send your password, one-time code or complete DANA, OVO, GoPay or QRIS credentials.

Correction request

If your phone number or account detail is inaccurate, tell us which field needs attention and why. We may ask for a verification step before making a change, so the request remains connected to the correct account rather than a different person.

Wallet status question

For a payment reference linked to DANA, QRIS, bank transfer or a virtual account, share the transaction reference and approximate time only. We use that narrow detail to trace status while keeping your wallet login, PIN and unrelated account history out of the message.

DATA HANDLING

What We Protect And Retain

Privacy depends on practical handling, not vague promises, so we describe the account actions behind each record.

Account records

We use your account identifier, phone verification result and sign-in history to connect requests with the right account. These details help us confirm an account step and investigate an unfamiliar login without exposing your information to another account holder.

Mobile and device signals

When you sign in from a phone or desktop browser, we may record device type, browser details, connection data and security events. These signals help us spot unusual access; they are not a request for files, photos or contact lists on your device.

Cookies and session data

Cookies and similar session records help keep a login connected to the correct account and remember basic page settings. You can manage browser storage through your device settings, although removing it may require another sign-in or affect saved policy preferences.

Wallet references

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference may be stored with a request so we can match status to your account. We do not need your wallet PIN or full banking password to investigate a payment record.

Retention controls

We retain account, support and transaction-linked records only while they serve account operations, dispute handling, security checks or legal duties. When a record is no longer needed for those purposes, our handling process moves it toward deletion or removal of direct identifiers.

Changes and objections

You can contact us to ask what personal data is held, request a correction or raise a concern about its use. We may verify your identity before responding, because sending account details to an unverified requester could expose your login or wallet history.

Privacy Policy Questions For Your Account

These answers focus on the questions you may have before creating an account or using neraca4d from Indonesia. They explain the practical link between the Privacy Policy, phone verification, mobile browsing and local wallet references. If your question is not listed, use the support route near the account area and describe the specific data point you want us to check.

It covers personal data connected with account creation, phone verification, sign-in activity, device signals, cookies, support messages and payment references. It also explains why we use those details, how long we may retain them and how you can request access or correction.

Phone verification helps connect account access with the person completing the account step and helps us investigate unusual sign-ins. We record the verification result and related account details, not the private contents of your phone or unrelated contacts.

Yes. The Privacy Policy includes references needed to match DANA or QRIS activity with your account, along with OVO, GoPay, bank transfer and virtual account references. We ask you to share a transaction reference, never a wallet PIN or banking password.

When you use a mobile browser, we may receive device type, browser details, connection data and security events. We do not need access to your photos, contacts or files. These signals support account protection and help us understand an unfamiliar sign-in.

Use the support contact path beside the account area and state whether you want access to your data or correction of a specific field. Include your account identifier, but leave out passwords, one-time codes and complete wallet credentials.

We keep account, support and transaction-linked records while they are needed for account operations, security checks, dispute handling or legal duties. After that need ends, our process moves the record toward deletion or removal of direct identifiers.

Yes. You can ask us how cookies or session data relate to your account, and you can manage browser storage through your phone or desktop settings. Clearing it may sign you out or require your device to load account preferences again.

Related Pages

neraca4d Indonesia FAQ About Us neraca4d Casino MMA One Championship