Reference

nina168 Privacy Policy For Your Account

Our Privacy Policy explains how nina168 handles the details you provide when you create an account, verify your phone, enter the lobby, or check a wallet status.

Account data explainedWallet checks outlinedCookie choices availableContact steps included
nina168 nina168 Privacy Policy For Your Account
CONTACT YOUR WAY

Privacy Policy Help Near Account Access

A clear contact route matters when you have a question about personal data rather than a lobby screen. We keep policy questions separate from game or wallet troubleshooting so your request reaches the right handling path. When you contact us, include the account phone number, the subject of your request, and the relevant date; do not send a full wallet password or one-time code. Our help route is available every day from 09:00 to 22:00 WIB through the site chat and account support form.

Team online

Policy request

Use the account support form to ask for a copy of the personal data connected with your nina168 profile. Add your registered phone number and the request type, such as access, correction, deletion, or an explanation of processing.

Cookie question

Site chat can help you understand cookie choices, browser storage, and device signals used during account access. We can explain which setting affects your session without asking you to reveal a password, PIN, or verification code.

Wallet record

For a DANA, OVO, GoPay, QRIS, virtual account, or bank transfer record, send the date and reference shown in your account. We use that detail to locate the correct entry before discussing any personal data request.

SIX DATA PROMISES

Inside Our Data Handling Process

The Privacy Policy is backed by practical account controls rather than broad wording. We limit staff access to details needed for a defined task, record security events around sign-in and phone verification…

Data collection

We collect details you enter during account creation, including your phone number and selected account settings. We also receive technical signals such as browser type, device path, login time, and error events when those details are needed to operate or protect your access.

Cookie controls

Cookies and local browser storage can preserve a sign-in session, remember a language or display choice, and help us detect repeated failed access. You can manage browser settings, although removing essential storage may require another account sign-in.

Account security

Phone verification is checked before account access, while unusual device changes, repeated login failures, and wallet-status changes can trigger an additional review. We will not ask for your password or one-time code through site chat or a policy request.

Payment references

Our records may include a payment rail, amount reference, status, and timestamp for DANA, OVO, GoPay, QRIS, virtual account, or bank transfer activity. These records help match an account event without giving our team access to your separate wallet credentials.

Retention choices

We keep personal data only while an account, support case, security matter, dispute, or legal need requires it. When the purpose ends, records are deleted, anonymised, or separated where practical, while some transaction references may remain for a defined operational reason.

Change requests

Ask us to access, correct, or delete eligible personal data through the account support form. We may request account details to confirm identity, explain a lawful retention need, and respond using the same contact route within the period allowed by local law.

Privacy Policy Answers For nina168

These Privacy Policy answers cover the searches we hear most often before account creation or a data request. They focus on what we collect, why a check appears, how cookies affect access, and how you can contact us. If your situation involves a DANA, OVO, GoPay, QRIS, bank transfer, or a phone change, include that specific detail so we can identify the relevant record.

The nina168 Privacy Policy covers account details, phone verification, device and browser signals, cookies, payment references, support requests, security events, and retention. It explains how we use those records for access, account protection, payment matching, and lawful operational needs where local law permits.

We may collect the phone number and account details you submit, plus device type, browser information, login times, cookie settings, and security events. If you use DANA, OVO, GoPay, QRIS, a virtual account, or bank transfer, payment references may also be recorded.

Phone verification links account access to the number you provided and helps us respond to unusual sign-ins or account changes. It does not give us your personal phone content. Keep verification codes private, and contact support through the account form if your number changes.

Our Privacy Policy treats cookies and browser storage as tools for keeping a session active, remembering selected settings, and identifying repeated access attempts. You can adjust browser controls, but removing essential cookies may sign you out or require phone verification again.

Yes. Send an access or correction request through the account support form with your registered phone number and the record you want checked. We verify the request, explain any restriction that depends on local law, and reply through the contact route you provide.

We retain records while they support your account, a payment-status question, a security event, a dispute, or a legal requirement. DANA, OVO, GoPay, QRIS, virtual account, and bank transfer references can remain for operational matching before deletion, anonymisation, or separation.

Use site chat or the account support form from 09:00 to 22:00 WIB each day. State that your request concerns the Privacy Policy, then include your account phone number and subject. Never include a password, PIN, or one-time verification code in the message.