Reference

Privacy Policy for Your negobos Account

Our Privacy Policy explains how we handle the details connected to your negobos account, including phone verification, device access, cookies and wallet records.

Account dataDevice controlsWallet recordsCookie choices
negobos Privacy Policy for Your negobos Account
CONTACT YOUR WAY

Three Paths For Privacy Questions

A clear contact path helps you act on this Privacy Policy rather than simply read it. We ask you to include the phone number or account detail connected to your request, without sending a wallet password or full payment credential. Our support route can help you understand a data use, locate a policy answer or pass a correction request to the right account team. If your question concerns a cashier record, name the rail involved, such as QRIS or bank transfer, so we can check the relevant status.

Team online

Account support

Use the support path inside your account when you need help with phone verification, a login record or a request to correct account details. We use the account context you provide to identify the right record and avoid asking you to share your password.

Wallet status

For a privacy question about DANA, OVO, GoPay, QRIS, bank transfer or a virtual account, include the payment rail and transaction reference. We can explain which status record is connected to your account without requesting the wallet PIN or complete financial credentials.

Policy request

If you want a copy, correction or clarification under this Privacy Policy, send the request through our available support contact and describe the action clearly. We may ask for account verification before changing or disclosing personal data tied to your account.

SIX DATA CHECKS

What We Handle And Why

We keep our Privacy Policy practical by separating account operation from optional device preferences.

Account details

We use the account details you submit to create and maintain your profile, connect phone verification with the correct sign-in…

Payment references

A DANA, OVO, GoPay or QRIS reference lets us match a wallet event with the right account and investigate a…

Device behaviour

Login time, device type and session signals can help us identify unusual account access and protect the sign-in flow.

Cookie choices

Cookies may remember a setting, support a session or show whether a page loads correctly.

Retention timing

We keep personal records only for the account, wallet reconciliation, security or legal purpose that requires them, subject to local…

Change requests

You can contact us to ask what data is connected to your account, request a correction or ask how a…

Privacy Policy Answers For Indonesia

These Privacy Policy answers cover the questions we expect you to ask before opening an account or contacting support. They explain the account step, wallet record and device context in plain language, while leaving room for local legal requirements. If your situation is specific, use the account support path and include only the details needed to locate the request. Never send a password, wallet PIN or complete payment credential in a message.

The Privacy Policy covers account details, phone verification, login and device signals, cookies, payment references and support requests connected with your account. It explains why we use each category, how we retain it and how you can ask for clarification or a correction.

We collect the account details you submit and the phone verification result needed for account access. We may also record login and device signals related to the session. The exact handling depends on the stated purpose and where local law permits that activity.

Yes. The Privacy Policy covers payment references and status records connected with DANA, OVO, GoPay and QRIS. These records help us match a wallet event to your account and respond to a status question. They are not your wallet PIN or complete credential.

You can request a correction through the available account support path. Tell us which detail is wrong, such as your phone record, and provide enough account context for us to locate it. We may verify ownership before changing the record.

We retain records for the account, payment reconciliation, security or legal purpose that requires them, subject to local law. A request about retention should identify the record, such as a QRIS reference or device event, so we can give a useful answer.

Cookies can remember a session or selected preference and help us see whether an account page works correctly. Your browser can limit or remove cookies. If you change those controls, sign-in continuity or saved choices may work differently on your mobile browser.

Yes. Requests about access, correction, deletion or retention depend on local law and the purpose for which the record is held. Where local law permits, we will assess your request after verifying the account context and explain the available next step.