Reference

Privacy Policy for Your nemo666 Account

Our Privacy Policy explains what nemo666 collects when you open an account, sign in from a mobile device, or use DANA, OVO, GoPay and QRIS.

Account dataWallet referencesCookie choicesAccess requests
nemo666 Privacy Policy for Your nemo666 Account
CONTACT PATH

Where Your Privacy Questions Go

A privacy question should not get lost beside a payment question, so we keep a clear route through account help and the cashier path. Tell us which account email or phone number you used, what you want changed, and whether the matter concerns DANA, QRIS, a bank transfer or device access. We may ask for account details to confirm that the request comes from you. You can also raise a concern after signing in from the mobile lobby.

Team online

Account help

Use the account help path when you want a copy of personal data, a correction to contact details, or clarification about the Privacy Policy. Include your account identifier and the phone verification status so we can locate the right record without asking for a wallet password.

Cashier path

Payment questions belong beside the cashier path when a DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference appears incorrectly. Share the transaction reference and date, while keeping your wallet PIN, one-time code and banking password private.

Security concern

If a login or device seems unfamiliar, contact us through account help before changing repeated details. Tell us the device type, approximate sign-in time and affected account step; we can use those signals to investigate without requesting full payment credentials.

DATA PRACTICE

Data Controls Behind Your Account

We handle this policy area through practical controls rather than broad promises. Account records, device signals and payment references are separated by purpose, and access is limited to the work needed for…

Collection

We collect the details needed for an account path, including contact information, phone verification status and login events. When you open Live Roulette Prestige or another lobby page, technical signals may record the device and session route rather than the contents of your private wallet.

Payment references

A DANA, OVO, GoPay or QRIS selection can create a payment reference linked to your account. Bank transfer and virtual account records may also be stored for matching and status checks. We do not ask for your wallet PIN or banking password through this policy process.

Cookies

Cookies can keep a signed-in path stable, remember selected settings and help us identify broken pages on mobile. If you clear browser data, you may need to complete the login and phone verification steps again before reaching the lobby.

Account security

Phone verification helps connect account access to the contact detail you supplied. We use login and device signals to investigate unusual access, including a new mobile route. Please keep codes private and tell account help if a sign-in does not match your activity.

Retention

We keep personal data only while it serves the account, payment matching, security, dispute or legal purpose described here. When a retention reason ends, records are removed or separated from direct account identifiers where that process is available to us.

Your requests

You can ask what data we hold, request a correction, ask about deletion where applicable, or question a cookie choice. Send the request through account help with enough detail to identify your account; we may verify ownership before making a change.

Privacy Policy Questions About nemo666

These answers address the questions we expect you to ask before opening an account or connecting a local wallet. Each response stays within the Privacy Policy scope: what we collect, why we use it, how you can reach us, and what may happen when you change devices or payment details.

The Privacy Policy covers account details, phone verification, device and login signals, cookies, and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or a virtual account. It also explains how to ask about access, correction, deletion where applicable and retention.

We do not ask for your DANA, OVO, GoPay or QRIS wallet password, PIN or banking password through the Privacy Policy process. We may retain a payment reference, method name and status so an account question can be matched to the correct activity.

Device type, browser signals, login time and session route help us keep account access working and investigate unfamiliar sign-ins. If you move from one mobile device to another, these signals may help explain why phone verification is requested again.

Use the account help path and state that your request concerns the Privacy Policy. Include the account email or phone number, the data category you want, and the reason if relevant. We may verify ownership before sending records or discussing a change.

You can request a correction and ask whether deletion is available for a particular record. We first check the account and any operational, security, dispute or legal reason for retention. Where local law permits, we explain the result and any remaining record.

Cookies can retain login preferences, support session continuity and show us when a page fails on mobile. Clearing them may remove saved settings and require login or phone verification again. You can contact account help if a cookie choice affects your access.

The policy is written for access from Indonesia, including account activity connected with local wallets and bank rails. Data handling and account eligibility depends on local law. If a local rule changes what we can provide or retain, we will explain that through the available account help route.