Reference

orca 128 Privacy Policy for Your Account

orca 128 Privacy Policy explains what we collect when you open an account, sign in, use DANA or QRIS, and contact our support team.

Account dataWallet recordsCookie choicesAccess requests
orca 128 orca 128 Privacy Policy for Your Account
CONTACT PATHS

Privacy Help Beside Your Account

A clear contact path matters when a Privacy Policy question is tied to a real account event. Send us the phone number linked to your account, the date of the relevant wallet action and the question you want answered; do not send a password or one-time code. Our support route can help with access requests, wallet record questions and policy clarification for your account.

Team online

Account contact

Use the account support route when you need a copy of personal data, a correction to your phone number or an explanation of why a verification record appears in your account.

Wallet record check

For DANA, OVO, GoPay or QRIS questions, include the payment reference and date. We check the account-side record without asking you to reveal your wallet PIN or login password.

Security concern

If your sign-in, device or account details look unfamiliar, contact support through the account route promptly. We may ask for account identifiers before discussing records or changing access details.

DATA HANDLING

What Privacy Policy Covers Daily

We apply the Privacy Policy at each practical point in your account journey, from phone verification to a return visit on mobile or desktop.

Account details

We may store your phone number, sign-in identifiers, verification state and support messages so we can maintain account access and answer a Privacy Policy request connected to your own records.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity can create reference data. We use those references to match account events, investigate status questions and keep required records.

Cookies and devices

Cookies and similar device signals can remember a session, protect sign-in and show whether a page works on mobile or desktop. You can adjust browser controls, although some account functions may then need another sign-in.

Account protection

We use sign-in signals, verification steps and unusual-device checks to reduce unauthorised access. Never share a password, wallet PIN or one-time code in support chat, even when asking about this policy.

Retention choices

We keep personal records for account operation, security, support and legal needs, then remove or separate them when those purposes end where local law permits. Some records may remain when a legal duty requires retention.

Requests and changes

You can ask what personal data we hold, request a correction or ask whether deletion is available. Include your account phone number and request type; we verify ownership before making a change.

Privacy Policy Questions About orca 128

These Privacy Policy answers address the account and wallet questions we expect you to ask before opening access. They explain what may be collected, how payment references are used, what happens on a mobile device and how to reach us without exposing private credentials. If your situation is different, send the account details needed to locate the record and ask for a specific response.

The Privacy Policy covers account details, phone verification, device and cookie signals, support messages, payment references and retention. It also explains how we handle requests for access, correction or deletion, subject to local law and the need to protect account security.

Yes. The Privacy Policy covers account-side references connected with DANA, OVO, GoPay and QRIS, plus bank transfer and virtual account records. We use those references to check status and reconcile an account event, not to request your wallet PIN.

When you open an account, we may collect your phone number, login identifiers, verification state and support history. We can also receive device and security signals linked to sign-in. We use these details for access, protection, support and required record keeping.

You can contact our account support route to ask what personal data we hold about your account. Include the linked phone number and describe the records you want. We verify ownership first, then explain the available response and any local-law limits.

Send a correction request through account support with the phone number linked to your account and the detail that needs changing. We may ask for an account verification step before editing records, especially when the change affects sign-in or payment matching.

On mobile, cookies and device signals can keep a session secure and help us identify repeated sign-in activity. Browser controls can limit them, but you may need to sign in again or complete another verification step when moving from login to the lobby.

Use the account support route if a device, login event or wallet reference looks unfamiliar. Share the account phone number, event date and reference where safe, but never send a password, wallet PIN or one-time code. Access action depends on local law.