Reference

Privacy Policy For Your okta88 Account

The okta88 Privacy Policy explains what we collect when you open an account, sign in from a phone, or connect DANA, OVO, GoPay and QRIS.

Account access recordsWallet activity detailsCookie choicesChange requests
okta88 Privacy Policy For Your okta88 Account
PRIVACY HELP ROUTE

Privacy Help Near Your Cashier Path

A clear contact path matters when a privacy request is connected to a wallet record or a login check. We direct you to the support route inside your account so we can match your request with the right account record without asking you to post personal details publicly. Include the subject of your request, the account phone number, and the relevant payment reference when available. We can then explain the next step for access, correction, deletion or a question about your stored data.

Team online

Account support

Use the support route shown after account access when you need to ask about a Privacy Policy request. We can connect your message to the correct account record and check whether the request concerns login details, a cookie choice, or a DANA, OVO, GoPay or QRIS reference.

Cashier record check

If your question concerns a payment receipt or wallet status, include the transaction reference rather than sending wallet passwords or security codes. Our support team uses the reference to locate the relevant record, explain its retention purpose, and separate payment verification from unrelated account details.

Change request

Ask us to correct account data through the same account support path. We may request a clear phone verification step before changing details, because a privacy request must come from the person connected with the account and not from an unverified message.

DATA CONTROL POINTS

Account Security From Login To Lobby

We handle privacy as an account process, not as a message hidden away from your daily activity.

Data collected

We may collect your account phone number, verification result, sign-in time, device or browser details, selected wallet route and support messages. These details help us connect a request to the correct account and investigate an access event without relying on a public name alone.

Cookie choices

Cookies can keep an active session connected while you move from login to the lobby on a mobile browser. We describe the cookie categories in the Privacy Policy, and you can manage browser permissions when you prefer not to retain a particular session marker.

Account security

Phone verification helps us check that an account change or access request comes from the account holder. Do not send a password, one-time code or wallet credential through support. If a sign-in looks unfamiliar, use the account support route before changing payment details.

Payment records

A DANA, OVO, GoPay or QRIS record may be kept with its reference, status and time so we can reconcile a cashier request. Bank transfer and virtual account details are handled for the same narrow purpose when BCA, BRI, Mandiri or BNI is used.

Retention periods

We retain different records for different operational and legal needs rather than keeping every detail indefinitely. The Privacy Policy describes the factors we use, including account status, unresolved payment checks, security events and requests that require a documented response.

Your requests

You can ask what account data we hold, request a correction, ask about deletion or raise a question about processing through account support. We may verify your phone before responding, and some records may remain when retention is needed for a documented transaction or local-law requirement.

Privacy Policy Questions For Indonesia Accounts

These Privacy Policy answers cover the practical questions we expect when you are deciding whether to open an account or connect a local wallet. They explain what we collect, how you can request a change, what happens on a mobile device, and where to send a question. If your situation is not listed, use the support route inside your account and include only the details needed to locate the record.

The okta88 Privacy Policy covers account details, phone verification, sign-in and device records, cookies, support messages, and payment references. It explains why we use each category, how retention works, and how you can ask for access, correction, deletion or clarification where local law permits.

We use phone verification to connect an account access request or data-change request with the person who opened the account. It helps reduce mistaken changes and suspicious access. We will not ask you to send a one-time code or wallet password through a support message.

Yes. The Privacy Policy covers payment references created when you use DANA, OVO, GoPay or QRIS. We may retain the route, reference, amount, status and time needed to match a cashier request. We do not need your private wallet password for that check.

When you sign in from a mobile browser, we may record device or browser details, session events and security signals connected with that access. This helps us investigate unusual login activity and keep a session consistent. The policy explains the relevant cookie choices and retention factors.

Use the support route inside your account and describe the field you want corrected. Include your account phone number and, if relevant, a payment reference. We may complete a phone verification step before changing the record so that another person cannot alter your account details.

You can send a deletion request through account support, and we will assess which records can be removed. Some payment, security or dispute records may need to remain for a documented period. Our response will explain the result and any retention reason where local law permits.

Send the question through the support route shown in your account rather than posting personal details in a public channel. Tell us whether it concerns cookies, login records, wallet status, retention or a correction. We can then direct the request to the relevant privacy process.