Reference

Privacy Policy for Your Account Data

obor 138 Privacy Policy explains what we collect, why we use it, and how you can ask about account, wallet or device records.

Account clarityWallet data contextDevice privacy

Browse Our Lobby Read FAQ

How DANA And QRIS Data Is Used

obor 138 Service availability depends on jurisdiction. Users are responsible for checking local law before access.

Our Privacy Policy covers the details needed to create and protect your account, confirm phone ownership, process wallet activity and respond to support requests. When you choose DANA, OVO, GoPay or QRIS, we may receive transaction references, status results and account-matching details rather than unrestricted access

1
to your wallet balance. Bank transfer and virtual account checks can include a reference number, sending bank and settlement status. We use these records to match deposits, investigate a missing receipt and confirm a withdrawal request. Device and browser details help us detect unusual sign-ins and
2
keep sessions connected to the right account. We retain records for the period needed for security, service handling and applicable legal duties. Access to account features depends on local law, and we will explain any relevant restriction when you contact us.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

CONTACT WHEN NEEDED

Three Ways To Ask About Privacy

A clear contact path matters when a Privacy Policy question affects your account or wallet record.

SIX DATA CONTROLS

Six Privacy Controls Behind Your Account

Privacy work is handled through practical account controls rather than broad promises. We separate sign-in checks from wallet status data, review unusual device activity, and limit account details…

Data collected

We may handle your account identifier, phone verification result, device and browser signals, support messages, and transaction references.

Cookie choices

Cookies and similar session tools help keep you signed in during a mobile or desktop visit and help us remember…

Account security

Phone verification, sign-in records and device signals help us identify unusual access.

Retention periods

We keep account, support and transaction records only for as long as needed for security checks, receipt matching, dispute handling…

Access requests

You can ask what personal data we hold about your account and request a copy or explanation.

Changes and contact

For a correction, privacy question or deletion request, use the account help path and describe the specific record.

Seven Questions About Privacy Policy

These Privacy Policy answers focus on the account actions you are most likely to take before opening an account or checking a wallet receipt. We keep the wording direct so you know what to send, what we may verify and where local law affects access or retention. If your situation is not listed, use the account help path with a short description.

It covers account details, phone verification, device and browser signals, support messages, cookies, and payment references linked to DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. It also explains retention, access requests, corrections and contact steps.

We use your phone number and verification result to connect you with the correct account and reduce mistaken access. If you ask about private records, we may repeat an account verification step before discussing sign-in or wallet details.

No password or wallet PIN should be sent through account support. For DANA, OVO, GoPay and QRIS activity, we may handle a transaction reference, status and matching account detail so we can check a receipt without receiving your private wallet credential.

Use the account help path and state that you are making a Privacy Policy access request. Add your account identifier and the data category you want checked. We may verify phone ownership before providing records connected with your account.

Yes. Describe the incorrect field, such as a phone detail or account identifier, and explain the correction needed. We will confirm your identity, check the source record and tell you whether the change can be made or needs further evidence.

Session cookies help keep your account connected while you move between login, wallet status and the lobby on mobile or desktop. Browser controls can restrict them, but doing so may interrupt access. We do not treat a cookie as your password.

Yes. Account access and some data handling steps depend on local law. Where local law permits, we provide the relevant account path; if a restriction applies, support can explain the affected request, record or access step.

Privacy Policy for Your Account Data

Three Ways To Ask About Privacy

Six Privacy Controls Behind Your Account

Data collected

Cookie choices

Account security

Retention periods

Access requests

Changes and contact

Seven Questions About Privacy Policy

01 What does the obor 138 Privacy Policy cover?

02 Why does Privacy Policy mention my phone number?

03 Does obor 138 see my DANA or QRIS password?

04 How can I request my personal data?

05 Can I ask obor 138 to correct account data?

06 How do cookies affect my privacy and login?

07 Does local law affect this Privacy Policy?

Related Pages