Reference

nami555 Privacy Policy for Your Account

Our Privacy Policy tells you what data we collect when you open a nami555 account, sign in from a mobile device, or use DANA, OVO, GoPay and QRIS.

Account dataWallet recordsDevice choicesContact rights
Browse Our Lobby Read FAQ
nami555 nami555 Privacy Policy for Your Account
CONTACT ROUTES

Get Privacy Policy Help Near Account Support

A clear contact route matters when you want to ask about your Privacy Policy rights or the data linked to a wallet event. Start from the support path inside your account and include the phone number or email used for registration, the relevant date and the payment reference when your question concerns DANA, OVO, GoPay or QRIS. We use those details to locate the right record without asking you to send a password or wallet PIN.

Team online

Account data request

Use the account support path to ask which personal data is linked to your sign-in. Include your registered contact detail so we can check ownership before discussing the record.

Wallet record question

For a DANA, OVO, GoPay or QRIS query, share the transaction reference and date through support. We can trace the status record while keeping your wallet PIN and password out of the request.

Privacy correction path

If your name, phone number or contact email needs correction, tell us what changed through support. We may ask for an account check before updating details attached to your access.

DATA PRACTICES

Inside nami555 Privacy Policy Controls

We keep this policy practical by connecting each data use to an account action you can recognise.

Account collection

When you open an account, we collect the contact and verification details needed for sign-in. Before discussing or changing those details, we check that the request comes from the account holder.

Payment references

A DANA, OVO, GoPay or QRIS payment can create a reference, status and timing record. We use that trail to match your cashier activity without requesting your private wallet password or PIN.

Device signals

Your phone or desktop browser may send device type, IP address, browser version and security events. These signals help us recognise unusual login patterns and investigate an account access question.

Cookies and sessions

Cookies can keep a signed-in session working, remember selected settings and help protect account pages. You can manage browser cookie controls, although some account functions may not work correctly when sessions are blocked.

Retention decisions

We retain account, payment and security records only for the period connected to service delivery, dispute handling, security checks or legal duties. When a record no longer has that purpose, our retention process addresses its removal.

Requests and changes

You can ask what data is held, request a correction or question a use through account support. Include your registered contact detail and a clear request; we may verify identity before making a change.

Privacy Policy Answers for nami555 Accounts

These Privacy Policy answers focus on the questions we expect you to ask before opening an account or checking a wallet record. We explain the account step, device data, cookies, local payment references and the contact route in plain English. If your situation is different, send the relevant details through support and we will direct the request to the right policy path.

It covers data from the website, account creation, sign-in, device access, cookies, support requests and payment status pages. It explains how we use contact details, security signals and DANA, OVO, GoPay or QRIS references for account and payment administration.

We may collect your name, phone number, email address, login details and verification records, together with device and security data from sign-in. We use these details to confirm account ownership, protect access and handle questions connected with your account.

Our Privacy Policy does not require us to store your DANA, OVO, GoPay or QRIS wallet PIN. We may retain a payment reference, status, timing and support trail so we can match a transaction question without asking for your private wallet credential.

Use the support path inside your account and state whether you want a data copy, a correction or another privacy request. Add your registered phone or email and the relevant record details; we may verify account ownership before responding.

Device signals help us identify unusual sign-in activity, while cookies can maintain your session and selected browser settings. These functions support account security and page continuity. You can adjust cookie controls in your browser, though blocked cookies may affect access.

We keep account, payment and security records for the period needed for service delivery, dispute handling, security checks or legal duties. Retention depends on the record and its purpose; you can ask support about a specific data category or date.

Yes. Start through the account support path and describe the right or concern you want to raise. Include your registered contact detail and, for DANA, OVO, GoPay or QRIS matters, the payment reference. Availability depends on local law.

Related Pages

nami555 Indonesia Access guide Account information About Us Live Roulette Royal