Reference

Privacy Policy For Your open123 Account

open123 Privacy Policy explains what we collect when you create an account, verify your phone, use the mobile lobby and check wallet status.

Account clarityCookie choicesWallet records
open123 Privacy Policy For Your open123 Account
CONTACT PATHS

Get Privacy Policy Help Near Wallet Support

A clear contact path matters when you want to ask about personal data, a cookie choice or a payment record.

Data questions Ask our account support team which details are connected to your open123 profile, why a verification step is needed and how we use contact data. We will first check account ownership before discussing records tied to your phone number.
Wallet records For a DANA, OVO, GoPay or QRIS receipt question, send the payment reference through the account support path. We use that reference to locate the relevant record without asking you to share a wallet password or full payment credentials.
Change requests If your phone, contact detail or privacy preference needs correction, tell us through the signed-in support route. We may request a phone verification step before changing account data, helping prevent another person from altering your profile.
DATA HANDLING

How open123 Applies This Policy

The practical details below show how we apply the Privacy Policy during ordinary account activity.

Account creation

When you open an account, we collect the details needed for account setup and phone verification. We use them to connect login activity with the right profile, respond to account requests and reduce confusion when you move from the mobile login page to the lobby.

Payment references

A DANA, OVO, GoPay or QRIS transaction can leave a reference, amount and status record for reconciliation. Bank transfer and virtual account records may follow the same process. We do not need your wallet password to check whether a receipt matches your account.

Cookie controls

Cookies can keep a session active, remember selected settings and help us understand which policy pages are being opened. Browser controls let you clear or restrict them, although removing essential session cookies may require you to sign in again.

Security checks

Phone verification, login records and device signals help us identify unusual account access. If a sign-in looks different from your usual mobile browser or desktop path, we may ask for an additional account check before discussing private records.

Retention choices

We keep account, support and payment records only for as long as operational, security or legal needs require. When a record no longer serves one of those purposes, we work to delete it or remove details that can identify you.

Your requests

You can ask about access, correction, deletion or the use of your personal data through the account support route. Include enough detail for us to locate your profile, and expect an ownership check before we disclose or change private account records.

Privacy Policy Questions About open123

These Privacy Policy answers address the account and wallet questions you are most likely to have before opening an account. They explain the practical handling of login data, cookies, payment references, retention and requests for access or correction. If your situation is not covered, use the account support route and include the details needed to identify your profile.

The open123 Privacy Policy covers account details, phone verification, login and device signals, cookies, support requests and payment references. It explains why we use each category, how long records may be kept and how you can ask about, correct or remove data where local law permits.

We collect the details needed to create your profile, verify your phone and protect account access. We may also record sign-in activity, device signals and support messages. We use these details to connect you with the correct account rather than to request unnecessary wallet credentials.

Yes. The Privacy Policy covers payment references and status records linked to DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity. These records help us match a receipt to your account and investigate a cashier question without asking for your wallet password.

We use essential cookies to maintain a signed-in session and may use other cookies to remember settings or understand page use. You can clear or restrict cookies in your browser. If essential cookies are blocked, the mobile or desktop login path may ask you to sign in again.

Send a correction request through the signed-in account support route and identify the detail that needs updating. We may ask you to complete phone verification before making a change. This check protects your profile from an unauthorised alteration and keeps the request attached to the right account.

We retain account, payment and support records while they serve operational, security or legal purposes. After that need ends, we work to delete or anonymise them. Some records may remain longer when local requirements apply, and we can explain the reason through account support.

You can ask through the account support route which categories of data are held and how they are used. We verify account ownership before sharing private details. Access and any available request rights depends on local law, and payment references may require extra receipt checks.