Reference

nez33 Privacy Policy for Your Account

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

Account clarityWallet recordsCookie choicesLocal access
nez33 nez33 Privacy Policy for Your Account
CONTACT ROUTES

Privacy Help Along Your Account Path

A privacy question should have a practical route, so we connect account concerns with the same help path used for login and wallet status checks. From your account area, you can ask us to clarify a payment receipt, explain a device record or help locate the data connected with your phone verification. If a request concerns another person, we may ask for account details that let us confirm who is asking before we respond. Use the support path near the cashier area so your question stays linked to the correct account record.

Team online

Account privacy request

Ask through the account help path when you want to know which phone, sign-in or verification details are connected with your nez33 account. We use the account step to confirm the request before discussing personal data.

Wallet record question

For DANA, OVO, GoPay, QRIS, bank transfer or virtual account records, include the payment reference shown in your account. This helps us explain the status without asking you to send a full wallet password or private credential.

Device access concern

If a mobile or desktop sign-in looks unfamiliar, contact us through account help and mention the approximate time and device path. We can check the session record, explain the security step and help you regain account access.

DATA PRACTICE

What We Do With Your Personal Data

Privacy work is part of the account flow rather than a separate promise. We limit account access through phone verification, record the actions needed to check wallet status…

Phone verification

Before account access is completed, we use your phone verification result to connect the session with the right account.

Session and device data

We record practical session details such as sign-in time, device type and security events.

Payment references

A DANA, OVO, GoPay or QRIS payment reference lets us match a receipt with the correct account.

Cookies and storage

Cookies and similar storage can keep your session, language choice and security step working between pages.

Retention decisions

We retain account, security and payment records only while they support account operation, dispute checks, fraud prevention or a legal…

Changes and access

You may ask us to correct inaccurate account details, explain how a record is used or request deletion where applicable.

Privacy Policy Answers For Indonesia

These answers address the privacy searches we hear most often before account access. They cover the details collected during phone verification, the records created by local payment rails and the steps available when you want to inspect or change your data. If your question concerns a specific receipt, device or sign-in, include that context through the account support path so we can respond to the correct record.

It covers account details, phone verification, sign-in and device records, cookies, payment references and requests to access or correct data. It applies to your use of the Indonesia-facing site where local law permits, including account activity connected with the lobby.

We may collect your phone number, verification result, sign-in time, device and security signals needed to operate the account. We also keep the account records you create and payment references needed to match DANA, OVO, GoPay, QRIS or bank activity.

Yes. We use DANA and QRIS reference details to match a receipt with your account and show its status. The same approach applies to OVO, GoPay, bank transfer and virtual account records; we do not ask for your wallet password.

Use the account help path and ask for a personal data access request. We may confirm your phone or account details before responding, so one person cannot obtain another person’s records. Include the relevant device or payment reference when it helps locate the data.

You can ask us to correct inaccurate account, phone verification or payment-linked details through account support. We may request an account check before making the change, and some transaction references may need to remain unchanged for reconciliation or a legal requirement.

Cookies and similar storage help maintain your login session, language choice and security checks when you move from a phone browser to the lobby. You can adjust browser settings, but blocking necessary storage may interrupt access or require phone verification again.

We keep records for the time needed to operate your account, investigate security events, reconcile payment receipts, handle disputes or meet a legal requirement. When those purposes end, we remove or restrict the record according to our retention process.