Reference

osg888 Privacy Policy for DANA and QRIS Accounts

DANA and QRIS details stay connected to the account steps you choose, while our Privacy Policy explains what we collect, why we use it and how you can…

Account dataWallet referencesDevice choicesPolicy requests
osg888 osg888 Privacy Policy for DANA and QRIS Accounts
CONTACT PATH

Support for Login and Wallet Data Requests

A clear support path helps when your phone verification, wallet status or personal-data request needs attention.

Account access Use the account support route when phone verification does not match your record. Include your registered phone number in masked form and device type so we can check access without exposing unnecessary data.
Wallet status For a DANA, OVO, GoPay or QRIS status question, share the receipt reference and date rather than wallet credentials. We use those limited details to trace the account record linked to your request.
Data request Ask support to correct, export or remove eligible account data by naming the record involved. We may verify account ownership first, and some records can remain where local law requires retention.
DATA PRACTICE

Device, Cookie and Account Controls

We keep this policy practical by connecting each data practice to an account action you can recognise.

Collection scope

We collect account, verification, transaction and device details needed for access, payment tracing and support. Your selections in the lobby are treated as activity records, not as a reason to request unrelated personal data.

Cookie choices

Cookies can remember a session, protect login flow and record basic page preferences. You can adjust browser controls, although refusing required cookies may interrupt phone verification or the path from login to the lobby.

Account security

Phone verification and account checks help us distinguish your session from an unknown device. Never share a password or wallet credential in support messages; we use limited identifiers and transaction references instead.

Retention checks

We keep records for account operation, dispute handling and legal needs only for the period required for those purposes. When a record is no longer needed, we remove it or separate it from direct account identifiers.

Correction requests

If your phone, contact or account record is inaccurate, contact us with the specific field you want changed. We verify ownership before editing and explain if a legal or transaction record cannot be altered.

Contact ownership

Privacy questions belong with our account support route, including requests about access, deletion or cookie choices. Mention Privacy Policy in your message and provide only the minimum details needed to locate your record.

Privacy Policy Questions for Indonesia

These Privacy Policy answers address the searches we hear most often before an account is opened. We explain the data linked to phone verification, local wallet references, device access and correction requests in plain terms. If your situation is different, use the account support route with a transaction reference or masked phone number rather than sending sensitive credentials.

It covers account details, phone verification, wallet transaction references, device signals, cookies, activity records, retention and requests to access, correct or remove eligible data.

Our Privacy Policy does not require you to send a wallet password. We use limited payment references, status details and timing to connect a DANA or QRIS event with your account.

Phone verification helps confirm account ownership during login and support requests. We may retain the verification result and related account record for security, dispute handling and legal needs.

Yes. Contact support and identify the account record you want to access. We may verify ownership first, then provide eligible records in a practical format where local law permits.

Send a Privacy Policy request through the account support route, name the incorrect field and provide a masked account identifier. We check ownership before making a correction.

Retention depends on the reason for keeping a record, such as account operation, dispute handling or legal needs. We remove or separate records when those purposes no longer apply.

You can request removal of eligible data through support. We first confirm account ownership and explain any transaction or legal records that must remain where local law requires retention.