Reference

Open ns2112 With Privacy Clarity

ns2112 Privacy Policy explains what account, device and payment details we use when you open an account and access our Indonesia lobby.

Account dataWallet recordsCookie choices
ns2112 Open ns2112 With Privacy Clarity
CONTACT PATHS

Choose A Privacy Support Route

A clear support path helps when you need to ask what our Privacy Policy means for your account.

Account access Use the account help route when you cannot reach your profile or need to…
Payment records For a Privacy Policy question about DANA, OVO, GoPay, QRIS, bank transfer or virtual…
Data requests Ask through the same support path for a copy, correction or deletion request where…
DATA PRACTICES

Explore Our Privacy Handling

Our Privacy Policy is supported by practical account controls rather than vague promises. We separate sign-in checks from payment references, limit access to people who need a record for support or security…

Account security

Phone verification is part of account access, and we may use sign-in and device-session details to investigate an unusual login. Do not share your password, one-time code or wallet PIN with support. These safeguards help us discuss your data with the right account holder.

Payment matching

A DANA, OVO, GoPay or QRIS reference can be paired with an account event so we can check a receipt or wallet status. Bank transfer and virtual account details serve the same tracing purpose, without giving our team access to your wallet credentials.

Cookies

Cookies can preserve your sign-in session and selected page preferences on mobile or desktop. You can manage them in your browser settings, although restricting some cookies may require another account check or interrupt the path from login to the lobby.

Retention

We keep personal data only while it supports account operation, security investigation, payment tracing or a legal requirement. When a record no longer serves one of those purposes, we remove it or use a form that no longer identifies your account.

Correction requests

If your phone detail or account contact record is wrong, ask support to correct it. We will confirm that you control the account before changing personal data, then explain whether the request can be completed under the Privacy Policy and local rules.

Policy contact

For a question about how ns2112 handles your information, name the account step, device path or payment reference involved. We can explain the relevant Privacy Policy section and tell you how to continue when access depends on local law.

Browse Privacy Policy Answers

These Privacy Policy answers address the searches we hear most often before an account is opened. They cover the data collected during sign-in, the records attached to Indonesian payment rails, browser cookies, account access and requests to change or remove personal details. If your situation is unusual, use the support path with a specific account event or payment reference.

The ns2112 Privacy Policy covers account details, phone verification, device-session data, cookies and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. It also explains retention, security handling and how to request access, correction or deletion where local law permits.

We use phone verification to support account access and confirm that a privacy request comes from the account holder. If you ask about a personal record, we may require an account check before explaining or changing it. Never send your password, one-time code or wallet PIN.

Yes. The Privacy Policy covers references created when you use DANA or QRIS, as well as OVO, GoPay, bank transfer and virtual account records. We use those references to match a receipt or status event to your account, not to request access to your private wallet.

Cookies can keep your session active and remember selected page preferences when you access the lobby from a mobile browser. Your browser controls cookie storage. Restricting cookies may sign you out, require another account check or affect the path between login and account pages.

You can contact support and specify the records you want, such as account contact data, phone verification, cookie preferences or payment references. We will confirm account control, assess the request under the Privacy Policy and local rules, then explain what can be supplied.

Send a focused request through the account support path and identify the incorrect or unwanted record. Where local law permits, we can process a correction or deletion request after verification. Some records may remain while needed for security, payment tracing or a legal requirement.

Access and eligibility depend on local law. Our Privacy Policy does not change the rules that apply in your location. Check your local requirements before opening an account, and contact support if you need clarification about a data request tied to your access status.