Reference

neo4j Privacy Policy For Your Account

neo4j Privacy Policy explains how we handle the account, wallet and device details you provide before you enter the lobby.

Account clarityWallet contextCookie choicesContact route
Explore Our Lobby Read FAQ
neo4j neo4j Privacy Policy For Your Account
CONTACT THE TEAM

Privacy Help Beside Account Support

A clear contact path helps when your account record, wallet status or privacy request needs attention.

Account contact Use the account support route when your phone verification record, sign-in history or contact detail looks wrong. Tell us which account step needs correction, and we will ask for enough information to identify the record without requesting your password.
Wallet status For DANA, OVO, GoPay, QRIS, bank transfer or virtual account questions, send the payment date and visible status rather than private wallet credentials. We can connect a privacy request with the relevant transaction reference while keeping the request focused.
Data request Ask our support team to route an access, correction or deletion request under this Privacy Policy. State the action clearly and use your account contact so we can verify ownership before discussing personal data or making a change.
DATA HANDLING

How neo4j Handles Privacy Details

Our handling choices follow the practical moments in your account journey: creating access, confirming a phone number, checking a wallet status and keeping a session secure.

Account data

We may hold your account contact, phone verification result and sign-in history because those details support access control. We use them to match your request to the correct account and to investigate an unfamiliar login without exposing another person’s record.

Payment references

DANA, OVO, GoPay and QRIS can return a status or reference connected with your account activity. Bank transfer and virtual account records may serve the same purpose. We use these details to reconcile status, not to request your wallet password.

Device signals

A mobile browser or desktop session can create technical signals such as browser type, time and security events. These signals help us identify unusual access and keep the account path stable when you move from login to a lobby page.

Cookies

Cookies may remember a session choice, preserve a language or region setting, and show whether a page responds correctly. You can manage cookies through your browser controls; changing them may affect remembered settings but does not erase an account record by itself.

Retention

We retain account, security and payment-reference data only for the period needed for the stated service, dispute handling, security checks or legal duties. When a retention reason ends, we delete, anonymise or restrict the record where our process allows.

Your request

You can ask us to access, correct or remove eligible personal data, or ask why a record remains. Send the request through account support with your account contact. We may verify ownership first and explain any data that must remain for security or legal reasons.

Privacy Policy Questions For neo4j

These Privacy Policy answers address the account and payment questions we expect from someone considering neo4j in Indonesia. They explain what a mobile session can disclose, why phone verification matters, how wallet references are handled and where to send a request. The same principles apply whether you are checking Fishing War Quick Arena, Live In-Play Football or a payment status, subject to access where local law permits.

The neo4j Privacy Policy covers account contacts, phone verification, sign-in activity, device signals, cookies and payment references. It explains why we use each category, how we protect account access, how retention works and how you can request access, correction or removal of eligible data.

We collect details needed to create and protect your account, such as your contact information, phone verification result and security events. We may also record the pages or lobby actions needed to maintain a session, but we use that activity in the context of account operation and security.

No. Our Privacy Policy treats DANA, OVO, GoPay and QRIS details as payment status or reference data when supplied through the account path. We do not ask for your wallet password. Bank transfer and virtual account references may also be retained for reconciliation and account support.

Phone verification helps us match an account request to the person controlling its contact detail and can support unusual-login checks. We record the verification result and related security event, not a needlessly broad set of phone activity. Access depends on local law and our stated account process.

Yes. Under this Privacy Policy, you can ask for a copy of eligible personal data by contacting account support with the account contact used for access. We verify ownership before sharing records, then explain the response and any information that cannot be disclosed.

Send a clear correction or deletion request through the privacy request path and identify the account record involved. We may keep information required for account security, dispute handling or legal duties, but we will explain that reason and restrict or remove eligible data where possible.

We keep records for the period needed for the purpose described in this Privacy Policy, including security checks, payment reconciliation, dispute handling or legal duties. After that period, we delete, anonymise or restrict the record through our retention process when the applicable reason has ended.

Related Pages

neo4j Indonesia Account information Live In-Play Football Manado Live Table About Us