Reference

Legal terms for your neo4j account

neo4j Legal sets out how we handle account access, payment records, cookies and requests about your personal data in Indonesia.

Account termsData choicesPolicy contactLocal access
neo4j Legal terms for your neo4j account
CONTACT THE POLICY TEAM

Get help with Legal questions

A clear contact path helps when a Legal question blocks your account or leaves a payment status unclear.

Account access Ask about a login, phone verification step or access decision through the account help route. Include the profile detail connected to your request so we can match the question to the correct Legal wording and explain what action is available to you.
Wallet records For a receipt or wallet status question, provide the payment name, transaction date and reference visible in your account. We can then direct the request to the relevant record without asking you to disclose a wallet password or unrelated account data.
Policy changes Use the same contact route to ask how to request a correction, deletion or change to stored account details. State the exact field or policy passage you are asking about, and we will explain the next verification step before making a change.
DATA AND ACCOUNT CARE

How we handle policy requests

Legal is also about the practical handling of information after you create an account. We use account details to provide access, confirm requested changes and trace payment records when a status needs…

Account details

We connect your submitted account details to the access and verification steps shown during registration. If a name, phone detail or email is inaccurate, use the policy contact route and be ready to confirm ownership before we alter the record.

Cookies

Cookies may keep a session available and help pages remember device behaviour. Your browser controls whether they remain on the device. Turning them off can affect sign-in or form flow, so check the account path again after changing browser settings.

Payment records

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference can be used to investigate a cashier status. We limit the request to the details needed for matching and do not ask for your wallet PIN or banking password.

Account security

A phone verification step can be part of account access and policy changes. Keep your sign-in details private, and contact us if a session or profile detail appears unfamiliar. We may ask for ownership checks before discussing protected account information.

Retention

Some account and payment records may need to remain available for operational, dispute or legal reasons. The retention period depends on the record and applicable rules. A request to remove data may therefore require a clear explanation of what can be changed.

Your request

When you ask for access, correction or removal, name the account detail involved and the result you want. We may verify ownership first, then explain the available action, any reason it cannot be completed, and the next contact step.

Questions about neo4j Legal

These Legal answers focus on the questions you may have before opening or using an account in Indonesia. They cover access, personal data, cookies, payment references, account security and contact steps. Read the applicable terms for your location, because access depends on local law; our support route can clarify a policy passage or request process.

neo4j Legal covers account access, phone verification, personal data, cookies, payment references, security checks, retention and requests to correct or remove information. It also explains how to contact us when a term affects your login, wallet status or ability to use the account where local law permits.

Access depends on local law and the conditions shown for your location. The account path may include phone verification and other ownership checks before access. If a decision is unclear, contact the policy route with your account detail so we can explain the applicable wording and next step.

A payment record can include the selected rail, a transaction reference, date and status needed to trace the cashier action. The same principle applies to OVO, GoPay, bank transfer and virtual account payments. Do not send a wallet PIN or banking password when asking for a status check.

Yes. Send a Legal request identifying the inaccurate field, such as a phone detail or email, and state the correction you need. We may verify account ownership before changing it. After that check, we can explain whether the correction is available and what happens to the prior record.

Cookies can keep a sign-in session available and help the account pages remember device behaviour. Your browser controls cookie storage, but switching it off may interrupt login or form steps. If access changes after a browser setting update, contact account help and mention the device path you used.

We may use phone verification and ownership checks before discussing protected details or changing a profile record. Keep your sign-in information private and report an unfamiliar session through account help. Include the relevant date and account detail, without sending passwords, wallet PINs or banking credentials.

Use the policy contact route and identify the record or account detail you want removed. Where local law permits, we assess the request against the purpose and retention rules for that record. We may verify ownership, then explain what can be removed, what must remain, and why.