Reference

omset288 Privacy Policy for Your Account

Our omset288 Privacy Policy shows what we collect when you create an account, verify your phone, sign in on mobile, or use DANA and QRIS at the cashier.

Clear data purposesWallet record detailsAccount request pathMobile cookie choices
omset288 omset288 Privacy Policy for Your Account
CONTACT PATHS

Where To Ask About Privacy Policy

A privacy question should reach the team that can locate the right account record, so we keep the support route visible from your signed-in account area.

Account support route Sign in, open the account support path and state that your request concerns the Privacy Policy. We use your registered phone number to locate the correct account record.
Payment record question For DANA, OVO, GoPay or QRIS questions, provide the transaction reference and date. We compare that reference with our records without asking for your wallet password.
Data change request Ask us to access, correct or remove eligible personal data through the same account route. We may request an account step to confirm that the request is yours.
DATA HANDLING

Privacy Controls Behind Your Account

We handle privacy requests as account operations rather than vague promises: we identify the record, check the request, apply the permitted change and keep a trace of the action.

Account data

We use your registered contact details and phone verification status to maintain the account record and route account requests. We do not ask for a wallet password as part of ordinary support.

Cookies on mobile

Cookies can keep your sign-in session working and record basic page behaviour. You can manage browser cookie settings on your phone, although some account steps may then need repeating.

New device checks

A sign-in from a different phone or browser can create technical security records such as device type, region and time. These details help us examine unusual access without reading wallet credentials.

Payment references

DANA, OVO, GoPay, QRIS, virtual account and bank transfer references help us match a cashier event with an account. We retain the reference needed for reconciliation and support handling.

Retention choices

We keep personal data only while an account, security matter, support case or legal duty requires it. When the purpose ends, records are removed or changed so they no longer identify you where feasible.

Your requested changes

You can ask for a copy, correction or eligible removal of your data through account support. We may confirm your phone or account details before changing records linked to you.

Privacy Policy Questions About Your Account

These Privacy Policy answers cover the searches we hear most often before an account is opened or a wallet record needs checking. We keep the wording practical: you can see what data is involved, why an account step may be required and where to send a request when access is where local law permits.

It covers account details, phone verification, device and browser records, cookies, support requests and payment references connected with DANA, OVO, GoPay, QRIS, virtual account or bank transfer activity.

We use the verification result to connect account access with the registered contact detail and to review requests about that account. We do not need your wallet password for this step.

Yes. A QRIS receipt or reference can be stored with the related account and transaction status so we can reconcile the record and answer a support request without collecting your wallet credentials.

Sign in and use the account support route, then ask for access to your stored personal data. Include your registered phone number and we may confirm ownership before releasing account-linked details.

Yes. Send a correction request through account support and identify the field that is wrong. We check the account step first, then update eligible records and retain a trace of the change.

We keep the payment reference and related status only while it supports reconciliation, security, an open support matter or a legal duty. After that purpose ends, we remove or anonymise it where feasible.

It applies to data created when you access your account on a phone, tablet or computer. Device type, browser details and sign-in time may be recorded for security, while cookie controls remain in your browser.