Reference

neo38 Privacy Policy for Your Account

neo38 Privacy Policy explains how we handle the details connected with your account, browser, wallet status and policy requests.

Account dataWallet detailsCookie choicesPolicy requests
Explore Our Lobby Read FAQ
neo38 neo38 Privacy Policy for Your Account
POLICY SUPPORT ROUTE

Privacy Help Beside Wallet Status

A clear request path helps when a Privacy Policy question concerns a wallet reference, an account sign-in or a device session. Start from the support link presented in your account area and include the email or phone detail attached to your account, plus the relevant DANA, OVO, GoPay or QRIS reference when applicable. We use those details to locate the right record without asking you to send a wallet password. If you are in Yogyakarta and a policy request relates to a mobile browser, mention the device type so we can explain the matching data path.

Team online

Account privacy request

Use the account support route to ask what personal details are connected to your neo38 profile. Include your registered contact detail so we can verify the request before discussing account records or making a change.

Wallet record question

For a DANA, OVO, GoPay or QRIS reference, share the transaction reference rather than a wallet password. We can use the record to explain how payment data is matched, stored and checked against your account.

Device data request

If your question concerns a phone, desktop or browser session, tell us which device path you used and when. This lets our support team connect your Privacy Policy request with the correct security event.

SECURITY PRACTICE

Account Security Across Wallet Devices

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

Data handling

We separate contact details, verification records, device signals and payment references by purpose. For example, a QRIS reference can help reconcile an account event, while a browser signal can help identify an unusual sign-in.

Cookie controls

Cookies can keep a session recognised and remember selected settings. If you clear them or block them in your browser, you may need to repeat an account step, and some policy preferences may need to be selected again.

Account security

We use sign-in records, verification checks and device activity to protect account access. We will not ask you to disclose a DANA, OVO, GoPay or bank password when handling a privacy request.

Retention periods

We keep each record only while it serves account security, payment reconciliation, dispute handling or a legal requirement. When a retention purpose ends, the record is removed or handled in a form that no longer identifies you where practicable.

Who handles requests

Our account support team receives questions about this Privacy Policy and routes them to the people responsible for account records and security checks. The support path shown after sign-in is the starting point for a personal data request.

Change requests

You can ask us to correct an account detail, explain a data category or clarify a retention point. Provide your registered contact detail and the requested change; we verify ownership before editing or disclosing personal records.

neo38 Privacy Policy Questions

These Privacy Policy answers focus on the actions you are most likely to take before opening an account or contacting support. They cover account data, cookies, local payment references, device behaviour and requests to change or access personal details. If your situation involves a specific record, use the support route in your account area and describe the exact step, such as QRIS confirmation or a mobile sign-in.

It covers account details, verification records, sign-in events, browser signals, cookies and payment references linked to DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. It also explains our purposes, retention approach, security checks and the route for personal data requests.

We use limited device and browser signals to keep an account session working, recognise unusual sign-in activity and investigate a security concern. If you switch from a phone to a desktop, the new session may create a separate security event without revealing your wallet password.

No. A DANA or QRIS reference can help us match a payment event to your account, but your wallet password is not needed for a policy request. The same principle applies to OVO, GoPay, bank transfer and virtual account details.

Start through the support path shown in your account area and state that you want to access your personal data under this Privacy Policy. Include your registered contact detail and the relevant account step; we verify ownership before discussing or sending records.

Yes. Send a correction request through the account support route, identify the detail that is wrong and provide the replacement wording. We may confirm your registered phone or email before making the change, so another person cannot edit your account record.

Cookies can preserve a browser session and remember a selected preference. Clearing or blocking them may require another sign-in or repeat choice. Your browser settings control many cookie actions, while our Privacy Policy explains why the related data is used.

Yes, a request or access route depends on local law. We assess the request against the applicable rules and may need to limit, verify or explain part of the response. Contact support with your account detail if you need a case-specific answer.

Related Pages

neo38 Indonesia neo38 Casino Nusantara Treasure Slots FAQ Access guide