Reference

Privacy Policy For Your oke jp Account

Our Privacy Policy explains how oke jp handles the details you provide when you open an account, verify your phone, enter the lobby, or connect DANA, OVO, GoPay…

Clear data purposesWallet record clarityAccount access controlsCookie choices
oke jp Privacy Policy For Your oke jp Account
DIRECT HELP ROUTES

Get Privacy Help Beside Your Account

A clear contact path matters when you want to ask what a record means or change an account detail.

Account data request Ask us to confirm the personal details held for your account. Include your registered phone number and the account step concerned, such as phone verification or sign-in history, so we can check the right record.
Wallet record query For a DANA, OVO, GoPay or QRIS question, share the payment reference and date through the account support route. We use those details to distinguish a pending cashier record from an unrelated wallet event.
Privacy correction path If your contact detail or profile record needs correction, tell us what appears wrong and what should replace it. We may request a phone verification step before changing information tied to account access.
DATA CONTROL DETAILS

What Your Privacy Choices Cover

Privacy controls work best when each step has a clear purpose. We separate account security records from cookie preferences, keep payment references tied to the correct cashier action and limit account changes…

Account security

We use phone verification, sign-in records and device signals to reduce unauthorised account access. Never send us your password or a complete wallet PIN. If a device changes, we may ask you to confirm the account before sharing details.

Cookie settings

Cookies can remember your session, language choice and security state on a mobile browser or desktop device. You can adjust browser permissions, although blocking essential cookies may prevent the account area from keeping you signed in.

Payment references

A DANA, OVO, GoPay, QRIS, bank-transfer or virtual-account reference helps us match a cashier event with the correct profile. We do not need your wallet PIN to investigate a status or identify a recorded transaction.

Retention period

We keep account, security and transaction records for the time needed to operate the service, resolve disputes and meet applicable legal duties. When a retention reason ends, we remove, anonymise or restrict the relevant record where permitted.

Request a copy

You can ask what personal data we hold by using the support path inside your account. State your registered phone number and the type of copy requested; we may verify your identity before releasing account-linked details.

Request a change

To correct or delete a detail, describe the exact field and explain why it is inaccurate or no longer needed. We will assess the request against account security, transaction records and any retention duty that still applies.

Privacy Policy Answers Before Account Access

These Privacy Policy answers address the searches we hear before an Indonesian account is opened or a wallet is connected. We explain what we collect, why a phone check may appear, how cookies behave on mobile and where to send a request. If your question concerns a specific record, use the account support route with its date and reference rather than sharing a password or wallet PIN.

It covers account details, phone verification, sign-in and device records, cookies, payment references, retention and privacy requests. It applies to the information created when you access the service, use the lobby or connect DANA, OVO, GoPay, QRIS, bank transfer or a virtual account.

Phone verification helps connect the right person to the right account before access or a sensitive account change. It also gives us a practical way to check an access request. We do not ask you to disclose your password or wallet PIN.

We may keep a payment reference, amount, status, timestamp and related account link for DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. These details help match a cashier event and resolve a status question without storing your wallet PIN.

Yes. Use the support route inside your account and identify the registered phone number plus the records you want to access. We may complete an identity check before sending account-linked data, and the response depends on local law and applicable retention duties.

Send a correction request through the account support path, naming the field that is wrong and the replacement detail. We may ask you to complete phone verification before changing information connected to sign-in, wallet status or account recovery.

Cookies can keep your session, language choice and security state available as you move from login to the lobby. Your browser controls them. If you block essential cookies, sign-in or account navigation may not remain active on that device.

You can submit a deletion request through the support route and explain which data it concerns. We assess it against security, transaction records and legal retention duties. Where local law permits, data no longer needed is removed, anonymised or restricted.