Reference

Privacy Policy For Your ocean89 Account

Our Privacy Policy explains what we collect when you open an ocean89 account, sign in, verify your phone and move between Live Roulette Gold, Batik Royale Slots and…

Account recordsWallet detailsCookie choicesSecurity checks
ocean89 Privacy Policy For Your ocean89 Account
CONTACT ROUTES

Privacy Questions Near Your Wallet

A clear contact route helps when your Privacy Policy question is linked to a real account event.

Account email Send your Privacy Policy request from the email attached to your account. Include the relevant account step, such as phone verification or a DANA receipt reference, so we can identify the correct record without asking you to send a password.
Support chat Use support chat when a privacy question appears beside a wallet or sign-in status. We may ask for limited account details to confirm ownership, but we will not ask for your password, one-time code or complete wallet credentials in the conversation.
Receipt check If your request concerns QRIS, OVO, GoPay or bank transfer data, keep the payment receipt and its reference available. We use that narrow detail to trace the record, explain its retention status and avoid searching unrelated account activity.
DATA HANDLING

Inside ocean89 Privacy Controls

Our handling process separates account access, wallet records and lobby activity so a privacy request can stay focused.

Account creation

When you open an account, we collect the details needed to create your profile and complete phone verification. We use the result to confirm that the person requesting account access matches the account record, rather than relying only on a typed login.

Wallet matching

A DANA, OVO, GoPay or QRIS reference can be linked to your account activity so a deposit or status question reaches the correct record. We limit that use to payment tracing, account servicing and security checks connected with your request.

Game activity

Opening Live Roulette Gold, Fortune Fishing Game or Futsal League Bet can create session and activity records. Those records help us keep the requested page working, investigate account access and answer a specific data request without treating every lobby visit as a separate profile.

Cookie settings

Cookies can preserve a sign-in session or remember a browser preference, depending on your settings. You can review or clear them through your browser controls; clearing them may require another login or phone-verification step before account access continues.

Security records

We may retain sign-in time, device signals and verification events when they are needed to protect your account. These records help us examine an unfamiliar access path from phone browser to lobby and support a response when you report a security concern.

Change requests

You can ask us to correct eligible account details, explain how a record is used or provide a copy where the request is allowed. Contact us through your account email or support chat, and we may verify ownership before making a change.

Privacy Policy Questions For ocean89

These Privacy Policy answers address the account steps you are most likely to question before opening an ocean89 profile. We cover phone verification, cookies, payment references, device records, access requests and deletion limits in plain language. If your situation involves a specific DANA, QRIS, OVO or GoPay reference, contact us through the account route described above so we can check the relevant record rather than provide a general reply.

It covers details collected during account creation and phone verification, sign-in and device records, cookie use, lobby activity and payment references. It also explains how to contact us about access, correction or deletion requests. Eligibility and access depend on local law, including for accounts in Indonesia.

We use the phone-verification result to support account ownership and reduce confusion when you sign in from a mobile browser. It can also help us investigate an unusual access event. We do not need your password or one-time code in a Privacy Policy support conversation.

Yes. The policy covers payment references connected with DANA, QRIS, OVO, GoPay, bank transfer and virtual account activity. We use those references to match a receipt or status with the correct account, respond to a request and protect wallet-related account access.

Cookies may preserve a session or remember a browser setting while you move from login to the lobby. You can clear or manage them through your browser controls. After clearing cookies, you may need to sign in again and complete phone verification before access resumes.

You can contact us through the email attached to your account or support chat and ask for access to eligible records. We may confirm ownership before responding. The request can cover account details, verification events, cookie-related records and payment references held for the stated purpose.

Yes, ask us to correct eligible account details through your account email or support chat. Tell us which field is inaccurate and, where relevant, name the account step involved. We may request a verification check before changing a record connected with access or payments.

We remove eligible details when they are no longer needed for the stated service, security review or a legal requirement. Some account, verification or payment records may need to remain for a defined retention purpose. We explain the applicable limit when responding to your request.