Reference

one77 Privacy Policy for Your Account

The one77 Privacy Policy explains what we collect when you open an account, verify your phone, use DANA or QRIS, and contact our support path.

Account clarityWallet recordsCookie choicesAccess where local law permits
one77 one77 Privacy Policy for Your Account
CONTACT THE TEAM

Privacy Policy Help Beside Account Support

A clear support path helps you ask about the Privacy Policy without sending sensitive wallet credentials. Open your account support route and include the phone number linked to your account, the subject of your request and any relevant reference code. We use those details to locate the right record, while you should never send a wallet PIN, password or full authentication code. Questions about access, correction or deletion can follow the same route.

Team online

Account privacy request

Use the support route connected to your account when you want to ask what personal details we hold or why a phone verification record appears. Include your registered phone number and request type so we can check the correct account without asking you to disclose a wallet PIN.

Wallet record check

If a DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference looks unfamiliar, send the date, amount reference and account phone number through support. We can compare the payment record with the account history while keeping your wallet password and private PIN out of the request.

Cookie question

For questions about cookies or device recognition, tell us which device path you used, such as a mobile browser or desktop browser, and describe the issue. We can explain the relevant session record and the available request path without requiring your login password in a message.

DATA HANDLING

What Our Privacy Process Covers

The policy is practical: it connects each data category with a defined account or service purpose.

Account details

We may hold the name, phone number and verification result you provide during account creation. These details help us identify your account and complete the phone check before access. If a detail is wrong, send a correction request through support with enough context to locate the account.

Device signals

A mobile or desktop browser can create session, device and login records linked to account protection. We use these signals to notice unusual access and help investigate a stalled login. They are not a request for your device password, wallet PIN or private message content.

Cookie controls

Cookies and similar browser records can keep a session working and remember security settings. You can manage cookies through your browser controls, although removing them may require another phone check or make some account pages harder to reach on that device.

Payment references

DANA, OVO, GoPay and QRIS references, along with bank transfer or virtual account details, help us match a wallet event to the right account. We use the reference for reconciliation and support checks, not to request your private wallet password or PIN.

Retention checks

We keep account, security, support and payment records for as long as needed for the purpose described in the policy, including dispute handling and applicable legal duties. When a record is no longer required, our process is to delete it or remove its account link.

Change requests

You can ask for access to your personal data, correction of inaccurate details or deletion where applicable. Send the request through account support, identify the phone number on the account and describe the requested change. We may verify ownership before releasing or changing records.

Privacy Policy Answers for one77 Accounts

These Privacy Policy answers focus on the searches you are most likely to make before opening an account or asking about a wallet record. We explain the account step, device signals, payment references, cookies, retention and request process in plain terms. If your question is not listed, use the support path and include only the details needed to identify your account.

It covers the personal and technical data connected with your account, including your phone verification, login events, device signals, cookies, support messages and payment references. It also explains why we use those records, how long they may remain and how you can request access or correction.

We use your phone number to create and identify your account and to complete the phone verification step before account access. It can also help us locate a support request. Keep your verification code private; support will not need your wallet PIN or account password.

Yes. The Privacy Policy covers payment references linked to DANA, OVO, GoPay and QRIS, as well as bank transfer and virtual account records. We use those references to check status and match activity with your account, not to collect your private wallet PIN.

You can send an access request through the account support route. State the phone number connected with your account and ask for the records covered by the Privacy Policy. We may verify account ownership first, so another person cannot obtain your personal account details.

Send a correction request through support and describe the inaccurate item, such as a phone detail or account identity field. Include the registered phone number and useful context, but do not include your password, wallet PIN or full verification code in the message.

Cookies can keep your session active, remember security settings and help us understand whether a login belongs to the expected device path. You can adjust them in your mobile or desktop browser. Removing cookies may lead to another phone check when you return.

You may request deletion through account support where applicable. We assess the request against account security, payment reconciliation, dispute handling and legal duties. If a record must remain, we will explain the reason where required; otherwise, we aim to remove it or disconnect it from your account.