Reference

nekatwin Privacy Policy for Your Account

The nekatwin Privacy Policy explains how we handle your account, device, wallet and support details from the first phone verification step onward.

Account dataWallet recordsDevice accessPolicy requests
nekatwin nekatwin Privacy Policy for Your Account
PRIVATE HELP PATHS

Get Privacy Help Beside Your Cashier

A clear support route helps you act on the Privacy Policy without searching through unrelated pages.

Account access request If your phone verification or sign-in record looks wrong, contact us through the account support link. We can check the relevant access event and explain which detail needs correction.
Wallet record request For a DANA, OVO, GoPay or QRIS entry, send the transaction reference shown in your cashier history. We use that reference to locate the payment record without asking for your wallet password.
Policy change request To ask about deletion, correction or a copy of personal data, use the privacy contact path in support. Tell us the requested action and account contact so we can verify ownership first.
DATA CONTROL POINTS

What Our Data Handling Gives You

The Privacy Policy is applied through ordinary account actions rather than hidden settings. We separate sign-in records from wallet references, use access events to investigate account security, and keep support requests tied…

Phone verification

Before account access is completed, we use the phone verification step to connect the account with the contact detail you provided. This helps us avoid sending private account replies to an unverified address.

Cookie choices

Cookies and similar browser storage can keep a signed-in path working and remember basic preferences. Your browser settings let you clear them, though clearing storage may require another account sign-in.

Device records

We may retain device type, browser path, session time and sign-in result when you access Auto Roulette, Bingo or another lobby page. These records help us investigate access issues without storing your screen contents.

Payment matching

A wallet reference or bank transfer detail is used to match a cashier request with the correct account. We do not need your wallet password to check whether a DANA or QRIS status was recorded.

Retention choices

We keep personal data while it supports account service, payment reconciliation, security checks or a legal need. When that purpose ends, records are removed or changed so they no longer identify you where practical.

Correction contact

You can ask us to correct inaccurate account or support details through the signed-in privacy contact path. We verify the request, review the requested field and reply with the next available step.

Privacy Policy Answers for nekatwin Accounts

These answers focus on the questions you may have before opening an account or sending a wallet request. If your situation is not covered, use the signed-in support path and refer to the exact account, device or payment record involved.

It covers account details, phone verification, device and session records, cookies, payment references, support messages and retention. It also explains how to request access, correction or removal where local law permits.

We record the selected rail, reference, amount, status and time so we can match a cashier request with your account and resolve a payment question. We do not need your wallet password for that check.

Sign in, open the support link beside the cashier area and ask for a data copy under the Privacy Policy. We verify account ownership before locating the relevant account, device and payment records.

Yes. Use the privacy contact path in support, identify the field that is inaccurate and provide your verified account contact. We review the request and explain whether a correction can be made.

Cookies or browser storage may keep your sign-in path and basic preferences available. You can clear them in your browser, but doing so may remove the saved session and require phone verification again.

We may keep device type, browser path, session time and sign-in result to investigate account access and unusual activity. These records support account security and are retained only for an operational, legal or dispute need.

The policy is intended for access where local law permits. Eligibility and available account actions depend on local law, so we may need to limit or adjust a request based on the applicable rule.