Reference

neraka33 Privacy Policy For Your Account

The neraka33 Privacy Policy explains how we collect, use and protect your account, device and wallet data before you enter the lobby.

Clear data purposesWallet details explainedAccess rights includedCookie choices covered

Explore Our Lobby Read FAQ

How DANA And QRIS Data Is Used

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

Our Privacy Policy separates account data from payment references so you can understand each step. When you choose DANA, OVO, GoPay or QRIS, we may receive a transaction reference, status and account match needed to confirm the wallet action; bank transfer and virtual account records may

1
show a reference linked to BCA, BRI, Mandiri or BNI. We do not need your wallet password for this process. A phone verification step can connect your account to the correct access record, while device details help us spot unusual sign-in activity. We use these records
2
for account operation, payment reconciliation, security checks and support handling, then retain them only as long as needed for those purposes or where local law permits. Your access depends on local law, and the current policy applies to the data practices described on this page.

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

PRIVACY HELP ROUTE

Questions About Your Privacy Policy

A clear support route helps when a privacy request and an account task meet at the same time.

Account data request Use the account support path to ask what personal data is linked to your login. Include your registered phone number so we can locate the correct account without requesting your wallet password.

Wallet status question For DANA, OVO, GoPay or QRIS records, send the transaction reference through support beside the cashier path. We use that reference to check status without asking for private wallet credentials.

Device access concern If a phone or browser record looks unfamiliar, contact us through the account help route before changing details. We can check the sign-in record and guide the next verification step.

DATA PRACTICE

Inside neraka33 Data Handling

We keep this policy practical: each data category has a purpose connected to account access, payment status or a request from you.

Account records

We use your registered phone number and verification result to create and protect account access. These details help us match a sign-in request to the right account when you move from mobile login into the lobby.

Payment references

DANA, OVO, GoPay, QRIS and bank transfer actions can create reference data showing amount status, method and account match. We use it to reconcile the cashier record, not to access your wallet password.

Device signals

Your browser or phone may provide sign-in time, session details and basic device signals. We compare these records when access changes or a verification step is triggered, helping us investigate an unfamiliar session.

Cookies

Cookies can keep a session working, remember selected settings and help us understand which policy page brought your request. You can manage cookies through your browser, though some account steps may then need repeating.

Account security

Phone verification, session checks and account support work together when access appears unusual. We may pause a request until details match, and we will not ask you to share a wallet password through support.

Retention and changes

We retain records for the period needed for account operation, payment reconciliation, security checks or legal duties. To request correction, deletion or a copy, contact support with your registered account details.

Privacy Policy Answers For Indonesia Accounts

These Privacy Policy answers focus on the questions we expect before an account is opened or a wallet is connected. If your situation is not covered, use the support path beside the cashier and include the account detail needed to find your record.

It covers account, phone verification, device, cookie and payment-reference data used for access, security, reconciliation and support. It also explains retention and how you can request changes or a copy.

No. We may receive a DANA, OVO, GoPay or QRIS transaction reference and status, but we do not need your wallet password. Never send wallet credentials through the support route.

Phone verification helps connect an account request to the correct record and supports checks when a device or session changes. We use the result for access and security, subject to local law.

The policy covers basic browser or phone signals, session details and sign-in timing. These records help us investigate unfamiliar access and keep the mobile path connected to your account.

Use the account support path beside the cashier and state whether you want a copy, correction or deletion request. Include your registered phone number so we can identify the right account.

We keep records only for account operation, payment reconciliation, security checks, support handling or legal duties. The period can depend on the record type and where local law permits.

Yes. Send the bank transfer or virtual account reference through support, along with your registered account detail. We can check the status record without requesting your bank password or full credentials.

neraka33 Privacy Policy For Your Account

Questions About Your Privacy Policy

Inside neraka33 Data Handling

Account records

Payment references

Device signals

Cookies

Account security

Retention and changes

Privacy Policy Answers For Indonesia Accounts

01 What does the neraka33 Privacy Policy cover?

02 Does the Privacy Policy store my DANA or QRIS password?

03 Why does neraka33 ask for phone verification?

04 What device data does the Privacy Policy describe?

05 How can I request a copy or correction of my data?

06 How long does neraka33 keep account and wallet records?

07 Can I ask about a BCA or Mandiri transfer record?

Related Pages