Reference

Privacy Policy For Your omo168 Account

Our Privacy Policy explains what we collect when you open an omo168 account, use DANA or QRIS, and move between the lobby and cashier path.

Account dataWallet recordsCookie choicesSecurity steps
omo168 Privacy Policy For Your omo168 Account
CONTACT ROUTES

Privacy Help Beside Your Cashier Path

A clear support route matters when you want to ask about the Privacy Policy, correct an account detail or check a wallet record.

Account request Ask us to correct contact details, phone verification data or another account record by…
Wallet query For a DANA, OVO, GoPay or QRIS record, share the visible receipt reference and…
Policy question If a Privacy Policy paragraph is unclear, point to the section or data type…
DATA PRACTICE

What We Do With Account Records

We handle Privacy Policy matters around real account actions rather than abstract categories.

Account details

We use the contact details you provide to create and protect your account, complete phone verification and connect your requests…

Cookie controls

Cookies may keep a selected language setting, preserve a session or show whether a Privacy Policy page opened correctly.

Session security

Login time, device type and session signals help us investigate access that does not match your normal account pattern.

Payment references

A DANA, OVO, GoPay or QRIS receipt can create a reference used to match cashier status with your account.

Retention purpose

We keep account, security, payment and support records for the period needed to operate the requested service, resolve a dispute…

Change requests

You can ask what account data we hold, request a correction or raise a question about deletion through our support…

Privacy Policy Answers For omo168

These Privacy Policy answers address the account and wallet questions you may search before opening an omo168 account. We focus on the records created by phone verification, device access, cookies, cashier references and support requests. If your situation depends on a local requirement, access depends on local law and we will use the applicable process where local law permits.

The omo168 Privacy Policy covers account details, phone verification, device and session signals, cookies, payment references and support requests. It explains why each record is used, how long it may be retained and how you can ask for access, correction or removal where local law permits.

Yes. Our Privacy Policy covers the receipt references and status records created when you use DANA, OVO, GoPay or QRIS through the cashier path. We use those references to trace a transaction and do not ask you to send a wallet password in a support request.

We collect details needed to create and protect your account, including contact data used for phone verification before access. We may also record login time, device type and support details so we can investigate unusual access, connect a request to your account and correct a submitted detail.

Use the account support route and state which detail you want corrected, such as a contact field or phone verification record. Add a safe contact detail and the relevant account step. We may verify account ownership before making a change or discussing the requested record.

You can delete or restrict cookies through your browser and device settings. Cookies may remember a session or selected setting, so restricting them can require another login or affect page behaviour. Our Privacy Policy explains the purpose of these files without requesting your wallet credentials.

We retain payment references for the operational, security, dispute or legal purpose that requires them. This can include DANA, OVO, GoPay, QRIS, bank transfer or virtual account records. When the relevant purpose ends, we remove, anonymise or restrict the record where applicable.

Yes. Access and eligibility depend on local law. Where local law permits, you can read the Privacy Policy, open an account and contact us about your records through the stated account path. If a local requirement affects access, the applicable process takes priority over general page wording.