Reference

Legal terms for your ns2121 account

ns2121 Legal sets out how account access, wallet records and policy requests work before you enter the lobby.

Account termsData requestsLocal-law accessPayment records
ns2121 Legal terms for your ns2121 account
CONTACT ROUTES

Three ways to raise a Legal question

A clear contact path matters when a Legal question affects your account or wallet record. We separate access questions from payment-status questions so the right details reach the right queue. Start with your account reference, the email or phone detail attached to the account, and the relevant date. Do not send a password or one-time verification code. Our team can then explain the applicable policy route, request a correction, or tell you which document is needed.

Team online

Account help

Use the account help route when you need a clause explained, access depends on local law, or a phone-verification step is preventing entry. Include your account reference and the exact Legal wording that raised the question so we can respond without asking you to repeat the full history.

Cashier status

For a DANA, OVO, GoPay or QRIS record, use the cashier support path and include the payment reference, amount and timestamp shown on your receipt. We use those details to separate a policy question from a wallet-status delay without requesting your wallet password.

Policy request

If you want a data copy, correction or clarification of a Legal decision, submit the request through account support with the contact detail registered to you. We may ask for phone verification before discussing private account records or changing information attached to your profile.

RECORDS AND CONTROL

How we handle Legal requests

We handle Legal matters through identifiable account records, not informal messages alone. The process links a request to your registered contact detail, the relevant wallet or account event, and the policy version…

Data handling

We use account details, phone-verification status and payment references to administer access and answer Legal requests. A DANA or QRIS reference is treated as transaction context, not as permission to view your wallet account. Share only the records needed for the question you are raising.

Cookie choices

Cookies may support account continuity, security checks and the display of policy pages. Your browser controls whether cookies remain active. If a cookie setting affects account access, tell support which device and browser you used so we can distinguish a site issue from a browser preference.

Account security

We may require phone verification before discussing private details or changing account data. Keep your password and verification code private, and contact us if a sign-in event or profile change does not look familiar. Legal support will not ask you to disclose a one-time code.

Record retention

We retain account, policy and payment-reference records for the period needed to administer the relationship, address disputes and meet applicable obligations. Retention can differ by record type. A request to remove data may therefore require a specific explanation of which record is being requested.

Correction requests

If your name, phone detail or account record is inaccurate, send the correction through account support from your registered contact route. We may check the requested change against phone verification and payment references before updating it, then explain any part that cannot be changed.

Policy ownership

Legal questions belong with our account support team, including questions about access, data handling, cookies or retained payment records. Quote the policy section, your account reference and the relevant date. We will identify the next step instead of giving a general lobby response.

Answers about ns2121 Legal

These Legal answers cover the questions most often raised before account access or after a wallet record needs checking. We keep the route practical: identify the account, name the policy point, and provide only the evidence needed for that request. If your situation is not listed, use account support and include the relevant date.

ns2121 Legal covers account access, policy wording, data handling, cookies, account security, record retention and requests to correct or discuss account information. It also explains why phone verification or payment references may be used when we review a DANA, OVO, GoPay or QRIS-related question.

Access depends on local law. If you are in Indonesia, the applicable position can affect account eligibility and access to the lobby. We may require phone verification before account access. If the site presents an access notice, follow that notice and contact account support if its meaning is unclear.

Send a data request through account support using the contact detail registered to your account. State that you are asking for a copy of your account data and include the relevant date range. We may verify your phone before discussing private records or preparing the requested response.

Yes, you can ask for a correction through the registered account support route. Tell us which field is wrong and what it should say. We may compare the request with phone verification and payment references, especially when the change affects access, DANA, QRIS or another wallet record.

DANA and QRIS references help us identify a payment event, receipt or cashier-status question connected with your account. They do not give us your wallet password or unrelated wallet data. Include the reference and timestamp when asking us to check a policy or account record.

Retention depends on the type of record and the period needed for account administration, dispute handling and applicable obligations. Account details, policy requests and payment references may not share one retention period. Ask account support about a specific record rather than assuming all data is treated alike.

Use the account support path and quote the Legal section or access message that concerns you. Add your account reference and the date of the decision, but never include your password or one-time code. We can explain the policy route and identify what evidence is needed for a follow-up.