Reference

olo4d Privacy Policy for Account Data

Your account data, wallet records, and access choices stay at the centre of the olo4d Privacy Policy.

Account dataWallet recordsCookie choicesAccess requests

How DANA And QRIS Records Are Used

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

Our Privacy Policy describes the records created when you open an account, complete phone verification, sign in, or select a wallet route such as DANA, OVO, GoPay, or QRIS. We may keep transaction references, status messages, timestamps, and device details so we can match an account

1
action with the correct wallet event without storing a wallet password. Bank transfer and virtual account references can also appear in account history. We use these records to respond to payment-status questions, protect the account from unusual access, and meet obligations that apply where local law
2
permits. The policy also covers data connected with your lobby activity, including access to Speed Baccarat, The Great Icescape, or Counter-Strike 2. We do not ask for data unrelated to an account or support request. If a local rule changes how data may be handled, the
3
applicable rule takes priority over this page.

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

CONTACT YOUR DATA TEAM

Where Privacy Questions Reach Us

A clear contact path helps you resolve a privacy question without repeating your account story.

Account support Send a privacy request through the signed-in account path and state whether you need access, correction, deletion, or clarification about a specific record.

Wallet status If a DANA, OVO, GoPay, or QRIS reference appears incorrectly, share the date and masked reference so we can check the record without requesting secret wallet credentials.

Access concern When login or device activity looks unfamiliar, contact account help through the available support path and describe the device step that needs checking.

ACCOUNT DATA PRACTICE

How We Handle Privacy At olo4d

Privacy work follows the same account steps you see on screen: phone verification, sign-in, wallet status checks, and entry to the lobby.

Collection

We collect account contact details, verification results, sign-in events, device signals, and selected wallet references when those details are needed to operate or protect your account.

Cookies

Cookies can keep your session connected while you move from login to the lobby. You can manage browser cookie settings, although switching them off may affect account access.

Account security

Phone verification helps connect account access to the correct person. We also examine unusual sign-in patterns and never need your DANA, OVO, GoPay, or QRIS secret code.

Retention

We retain records only for operational, security, dispute, or legal needs described in the Privacy Policy. Retention can differ by record type and local requirements.

Data requests

You can ask us to access, correct, or delete eligible account data. Include your registered contact detail and a precise request so we can verify ownership safely.

Third-party handling

Wallet and service partners may process limited references needed to confirm a transaction or status. We share only the data required for that specific account event.

Answers About Your olo4d Privacy Policy

These common questions focus on the Privacy Policy details Indonesian account holders usually need before opening an account. Each answer points to a practical action, from checking a QRIS record to asking how cookies or device signals affect access where local law permits.

It covers account details, phone verification, sign-in events, device signals, cookies, wallet references, support requests, retention, and your choices to access, correct, or delete eligible data.

We use verification results to connect account access with the correct account holder, reduce mistaken access, and investigate unusual sign-ins. We do not need your wallet PIN for this step.

Yes. It explains that DANA and QRIS references may include a masked transaction reference, status, and timestamp so we can check an account event without storing secret wallet credentials.

Use the signed-in account support path, identify the contact detail registered to your account, and ask for an access request. We may verify ownership before releasing eligible records.

You can request correction or deletion of eligible data through account support. Some records may remain when needed for security, dispute handling, operational history, or requirements that apply where local law permits.

Session cookies help keep your login connected as you enter the lobby. Browser settings can restrict them, but turning them off may interrupt sign-in, verification, or account navigation.

Contact account support through the available signed-in or account recovery path and describe the device event. Do not send a wallet PIN, full password, or secret QRIS credential.

olo4d Privacy Policy for Account Data

Where Privacy Questions Reach Us

How We Handle Privacy At olo4d

Collection

Cookies

Account security

Retention

Data requests

Third-party handling

Answers About Your olo4d Privacy Policy

01 What does the olo4d Privacy Policy cover?

02 Why does olo4d need my phone verification data?

03 Does the Privacy Policy mention DANA and QRIS records?

04 How can I request a copy of my olo4d account data?

05 Can I ask olo4d to correct or delete data?

06 How do cookies affect olo4d account access?

07 Who should I contact about an unfamiliar device record?

Related Pages