Reference

Open okta88 Privacy Policy Details

okta88 Privacy Policy explains how we collect, use and protect the details connected to your account, including phone verification and wallet status for DANA, OVO, GoPay and QRIS.

Account dataWallet recordsCookie choicesAccess requests
Explore Our Lobby Read FAQ
okta88 Open okta88 Privacy Policy Details
CONTACT ROUTES

Ask About Privacy Through Your Account

A clear account contact path helps you ask about the Privacy Policy without sending sensitive details through an unrelated channel. Start from the signed-in support route and include the phone number or account identifier linked to your profile; we use that step to match the request safely. If a wallet status or payment receipt is part of the question, mention DANA, OVO, GoPay, QRIS, bank transfer or virtual account and the date shown in your account. We respond through the available support contact route.

Team online

Account request

Use the support contact route after signing in and identify the account detail you want checked. We may ask for a confirmation step before discussing personal data, so your request about the Privacy Policy stays connected to the right okta88 account.

Wallet question

For a privacy question involving DANA, OVO, GoPay or QRIS, provide the wallet name and the status visible in your account. We can then separate payment reference data from the rest of your profile instead of asking you to resend a full receipt.

Correction path

If your phone, name or account detail needs correction, tell us which field is inaccurate through the account support route. We review the request against the account record and explain any verification step required before making a change.

DATA PRACTICES

Browse okta88 Data Handling Steps

We handle Privacy Policy requests through practical account controls rather than broad promises. Phone verification helps us connect access to your account, while device and browser signals help identify unusual login activity.

Account details

We may hold the details you enter for an account, such as your phone contact and verification state. These records help us return you to the correct profile when you move from login to the lobby, and the Privacy Policy explains their purpose.

Payment references

A DANA, OVO, GoPay or QRIS action can create a reference, amount, rail name and status in account records. Bank transfer and virtual account activity can carry similar references. We use these details to match payment questions without treating them as casual browsing data.

Cookies

Cookies can remember a session, support sign-in continuity and help us understand which policy page was opened. Your browser controls whether cookies remain. On mobile, clearing site data may sign you out and remove saved session choices.

Device security

When you sign in from a new phone or browser, technical signals may be checked alongside phone verification. This can help us spot unusual access around the lobby or a wallet screen. We do not describe a device signal as a replacement for your account step.

Retention requests

You can ask how long a category of account or payment data is kept and why it remains on record. Some records may need to stay available for security, dispute handling or legal duties. We explain the applicable reason when responding to your request.

Data changes

To request access, correction or deletion where applicable, contact us through the signed-in support path and name the relevant field or record. We may verify ownership before acting, then confirm whether the request was completed or limited by a legal requirement.

Check Privacy Policy Answers Before Opening

These Privacy Policy answers focus on the questions you may have before creating an account or checking a wallet status. We explain what can appear in account records, how mobile access affects cookies, which details help us investigate a payment reference and how to make a request. If your situation is not covered, use the account support route with the smallest amount of personal detail needed to identify your request.

The okta88 Privacy Policy covers account details, phone verification, login activity, device signals, cookies, support messages and payment references. It also explains how we use records connected with DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity.

Phone verification helps us connect a login and account request to the correct profile. It can also add a security check when access comes from a new browser or device. We describe this use in the Privacy Policy rather than treating your phone detail as general browsing data.

Yes. The Privacy Policy covers payment references linked to DANA, QRIS, OVO, GoPay, bank transfer and virtual account activity. A record may include the selected rail, status and reference details needed to match a receipt question with the account that made the request.

Sign in, use the account support route and ask for access to the personal data linked to your profile. Include the relevant phone contact or account identifier, but do not send extra wallet credentials. We may complete an ownership check before sharing the response.

You can request a correction through the signed-in support path and state which account field is wrong. We may verify the request before changing it. If a payment reference or security record cannot be edited, we explain the reason and keep the account note clear.

Cookies can keep your session active and remember site choices on a mobile browser. Clearing cookies or site storage may sign you out and remove those choices. Your browser settings control this behaviour, while the Privacy Policy explains the purposes for each cookie category.

Yes, some access, correction or deletion requests depend on local law. Where local law permits, we assess your request through the account support route, verify ownership and explain any record that must remain for security, payment disputes or legal duties.

Related Pages

okta88 Indonesia La Liga Over Under FAQ Account information Access guide