Reference

Legal access for your nami555 account

nami555 sets out the Legal terms behind account access, wallet records, personal data and policy requests in one place.

Policy termsAccount rightsData requestsLocal access
nami555 Legal access for your nami555 account
POLICY HELP ROUTES

Get help with Legal questions

A clear contact path helps when a Legal question affects your account or wallet status. Start with the route that matches the issue, include your account details only through the requested field, and avoid sending payment credentials in free text. We can check the account record behind a DANA, OVO, GoPay or QRIS status question while keeping the policy request separate from a game decision.

Team online

Account access

Use the account help route when phone verification, identity details or local access wording prevents you from entering your account. Tell us which step stopped, whether you are on a mobile browser or desktop, and we will direct the request to the relevant Legal handling path.

Wallet record

For a DANA, OVO, GoPay, QRIS, bank transfer or virtual account record, provide the reference shown in your account rather than a wallet password. We use that trace to separate a payment-status question from a request about how our Legal terms apply.

Policy request

Ask for a clause explanation, personal-data copy, correction or deletion through the policy contact route. State the exact request and the account email or phone detail used at registration so we can match the request without collecting unnecessary information.

DATA HANDLING PRACTICE

How nami555 handles Legal records

Legal handling is tied to practical account events rather than broad statements. We record the details needed for access checks, connect payment references to the correct account, and protect account activity through…

Data collection

We collect account details needed to create access, complete phone verification and respond to a policy request. Payment references from DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity are used to identify the related transaction record.

Cookie use

Cookies support the account path by keeping session and preference details available while you move between sign-in and the lobby. You can manage browser cookie settings, but changing them may interrupt access checks or require you to sign in again.

Account security

Phone verification is part of our account access process, and we ask you to keep sign-in details private. We do not need a wallet password, card PIN or one-time payment code in a policy request or account-support message.

Record retention

We retain account, access and payment-status records for the period needed to operate the account, address disputes and meet applicable legal duties. A retention question can be sent through the policy route with the specific record you want clarified.

Correction requests

If your name, phone detail or another account field is inaccurate, request a correction and identify the field precisely. We may ask for an account check before changing it, so one person cannot alter another account record.

Deletion requests

You can ask how to remove eligible personal data from your account record. Some records may need to remain for legal, security or transaction purposes; we will explain the applicable reason and the resulting account-access impact.

Questions about Legal and nami555

These Legal answers address the account questions you are most likely to have before opening access. They cover local eligibility, personal data, cookies, wallet references, corrections and contact steps, so you can decide what to submit and where to ask for a policy response.

Legal covers account access, local eligibility, phone verification, personal-data handling, cookies, security records, payment references and requests to correct or remove data. It also explains how to contact us when a policy clause or an account record needs a specific response.

Yes. Access depends on local law and the details connected with your account and region. Before you enter, we may require phone verification or another account check. Do not continue where local law permits wording does not apply to your situation.

DANA and QRIS references are connected to the relevant account record so we can trace a status question without asking for wallet credentials. We may request the transaction reference shown in your account, but never a wallet password or one-time payment code.

You can send a personal-data request through the policy contact route and identify the account email or phone detail used at registration. We may verify account ownership first, then explain which records can be supplied and any limits that apply.

Name the exact field that is wrong, such as a phone detail or account name, and send the request through the policy route. We may complete an account check before making a change, protecting the record from an unauthorised edit.

You can request removal of eligible personal data through the policy contact route. Some account, security or payment records may need to stay for legal or transaction reasons. We will explain the reason and whether removal changes your account access.

Send a focused Legal request that names either cookie use or record retention and includes your registered account detail. We will separate browser-session questions from retained account or payment records, then direct you to the relevant policy response.