Reference

neraka11 Privacy Policy for Your Account

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

Account dataWallet recordsCookie choicesPrivacy requests
neraka11 neraka11 Privacy Policy for Your Account
CONTACT DATA DESK

Where To Ask About Your Privacy Policy

A direct request helps us locate the correct account record without asking you to repeat the same details.

Account privacy request Use the support contact path while signed in where possible.
Wallet record question For a DANA, OVO, GoPay or QRIS reference, send the date, amount reference shown…
Device access concern If your phone or browser access looks unfamiliar, contact us through the account support…
HANDLING YOUR RECORDS

What We Do With Personal Data

Privacy controls work best when you can see the practical reason for each data category. We use account details to provide sign-in and phone verification, payment references to match wallet activity, and…

Account creation

We use your submitted contact details to create and maintain the account path, send account-related messages and complete phone verification before access. Keeping your phone number current helps us distinguish a genuine access request from an unfamiliar attempt.

Payment matching

A wallet or bank reference helps us match a deposit or withdrawal request with the correct account. We do not ask for your wallet PIN in support messages. DANA, OVO, GoPay, QRIS, bank transfer and virtual account records can be handled separately.

Cookies and storage

Cookies or similar browser storage can keep a session active, remember selected settings and support security checks. You can manage browser permissions, but blocking required storage may interrupt sign-in or prevent the account page from recognising your session.

Security signals

We may record device type, browser details, approximate location, sign-in time and failed access events. These signals help us investigate an account alert without treating your device as proof of identity or collecting your private wallet PIN.

Retention period

We keep personal data only for as long as needed for the stated service purpose, account support, security review or a legal requirement that applies to the request. Retention can differ by record type, so ask support about a specific account item.

Changing your details

You can request correction when your contact detail, device context or account record is inaccurate. Send the old and new detail through support, but leave out passwords and wallet secrets. We may verify the request before changing information tied to account access.

Privacy Policy Answers for Indonesia

These Privacy Policy answers address the account and payment questions you are most likely to ask before opening access. They explain what we collect, why a device may be recognised, how wallet references are handled and how to contact us about your records. If your situation is not covered, use the support path and mention the exact account detail involved. Access and any request outcome depends on local law.

The neraka11 Privacy Policy covers account details, phone verification, sign-in events, device signals, cookies, support messages and payment references. It applies when you open an account, access the lobby, check DANA or QRIS status, or ask us to change or provide personal data.

We use your phone number to create the account path, complete phone verification and help identify an access request. It can also help support locate the right record when you ask about a login or wallet reference. Do not send a verification code in an unsolicited message.

Yes. The Privacy Policy covers payment references connected with DANA, OVO, GoPay and QRIS, along with bank transfer and virtual account references. We use those records to match account activity and resolve status questions, not to request your wallet PIN or secret credentials.

We may receive browser type, device category, language, approximate location, access time and failed sign-in events. These details help protect the account and investigate unfamiliar access. They do not replace phone verification, and you can ask support about a particular device record linked to your account.

Contact support from the signed-in account area where possible and name the exact request: access, correction, deletion or a copy. Include the account email or phone number, but not your password, wallet PIN or full payment credential. We may complete an identity check before responding.

We retain each record for the period needed for its service purpose, account support, security checks or a legal requirement that applies. Account details, device events and DANA or bank references may therefore have different periods. Ask support about the category and account involved.

You can manage optional cookies through your browser settings. Required session or security storage may be needed for sign-in, phone verification and account recognition, so blocking it can interrupt access. Contact support if a cookie choice prevents you from reaching your privacy request path.