Reference

Privacy Policy For Your olo303 Account

Our Privacy Policy explains what we collect when you open an olo303 account, sign in on mobile or desktop, and use the lobby in Indonesia.

Account dataWallet recordsCookie choicesSecurity checks
olo303 Privacy Policy For Your olo303 Account
CONTACT ROUTES

Where Your Privacy Questions Go

A clear contact path matters when your account record or wallet status needs attention. Our support process lets you ask about personal data connected to your olo303 account, explain a payment reference that does not match, or request help with the phone verification step. Keep your account email, transaction reference and approximate request date ready, but do not send your password or full wallet credentials. If you access the lobby from Yogyakarta, the same privacy request path applies as it does from Jakarta, subject to local law.

Team online

Account details

Ask us to clarify the personal details linked to your account, including the phone verification record used before access. We may ask for account identifiers so we can confirm that the request comes from you before discussing or changing the record.

Wallet records

For DANA, OVO, GoPay, QRIS, bank transfer or virtual account questions, provide the transaction reference and status shown in your account. We use those details to locate the relevant record without asking you to disclose a password.

Privacy requests

Use our support route to ask about access, correction, deletion or retention of your personal data. We assess each request against account security, legal duties and the local rules that apply to your access.

DATA HANDLING

What We Do With Your Account Data

We keep the Privacy Policy practical by connecting each data category to a real account action. Phone verification supports account access, device signals help protect sign-in, and payment references help us reconcile…

Collection

We collect details you submit for an account, such as contact information and phone verification data. We also receive technical details from the device and browser used to sign in, so the session can be checked against normal account activity.

Payment matching

A DANA, OVO, GoPay or QRIS reference helps us connect a payment status with your account. Bank transfer and virtual account records may carry the selected bank name and reference needed to resolve a balance question.

Cookies

Cookies can keep a session active, remember selected settings and help us understand whether a page loads correctly. You can manage cookie controls in your browser, although changing them may affect sign-in or page continuity.

Account security

We use sign-in details, phone verification and device signals to identify unusual access. If a security check is triggered, we may limit account actions until we can confirm the request belongs to you.

Retention

We retain records only for the period connected to the purpose for collection, account security, dispute handling or a legal requirement. When a record is no longer needed for those purposes, our process moves it toward deletion or anonymisation.

Your requests

You can ask for a copy, correction or deletion of personal data linked to your account, subject to identity checks and applicable law. Include the account contact and request type so we can direct the request to the right record.

Privacy Policy Answers For olo303

These Privacy Policy answers focus on the account questions you are most likely to have before access. We explain payment records, device details, cookies, phone verification, retention and contact steps in plain English for Indonesia. If your request involves eligibility or access, the outcome depends on local law and the rules applying where local law permits.

The olo303 Privacy Policy covers account details, phone verification, device and browser signals, cookies, support requests and payment records. It explains why we use each category, how security checks work and how you can ask about, correct or delete data connected with your account.

Yes. The Privacy Policy includes payment references and status records connected with DANA, OVO, GoPay and QRIS. These details help us match a wallet request to your account and investigate a missing or mismatched status without requesting your password.

We use the phone verification step to confirm account access and reduce the chance of an unauthorised sign-in. The related record can also help us handle an account request. We only discuss or change it after checking that the request comes from you.

Cookies may keep your session active, remember settings and show whether a page is loading correctly. You can manage them through your browser. Blocking some cookies may interrupt sign-in or page continuity, but your browser controls remain available for changing those choices.

You can contact our support route to request access to personal data or correction of an inaccurate record. Include the account contact and a clear description of the issue. We may verify your identity first and assess the request under applicable local law.

Retention depends on the purpose for collection, account security, dispute handling and legal duties. Payment references from wallets, bank transfer or virtual account activity may remain while those needs continue. When no valid need remains, records move toward deletion or anonymisation.

Use the account support route and state that your question concerns the Privacy Policy. You can ask about account data, cookies, phone verification or a DANA, OVO, GoPay, QRIS or bank reference. Do not include your password or complete wallet credentials.