Reference

Privacy Policy for Your okidr Account

Our Privacy Policy explains how okidr handles the details connected with your account, wallet activity, device access and support requests.

Account dataWallet recordsDevice signalsCookie choices
okidr Privacy Policy for Your okidr Account
HELP WITH PRIVACY

Get Privacy Help Through Your Account

A clear contact path matters when you want to ask what data we hold, correct an account detail or question a wallet record.

Account privacy request Send a request from the account support route when you want to ask about stored profile data, a phone verification record or a correction. We may ask you to confirm account ownership before discussing details, so another person cannot obtain your information through a simple message.
Wallet record question For a DANA, OVO, GoPay, QRIS, bank transfer or virtual account query, include the transaction reference and date. We check our matching record and explain what we retain. We do not need your wallet PIN, password or one-time code to investigate the status.
Cookie and device help If a device keeps an old session or cookie preference, contact us through the same support path with your browser or device type. We can explain the available steps for clearing local data, ending sessions or submitting a request about device information connected with access.
DATA CONTROLS

Clear Controls for Wallet and Device Data

We treat the Privacy Policy as an operating process, not a page kept apart from account work.

Account details

We may hold your phone number, verification result and account settings so we can connect a login with the correct profile. Check your account details before requesting a correction; a precise phone number and request date help us make the right change.

Wallet references

When you use DANA, OVO, GoPay or QRIS, our records can include a provider reference, amount status and time. For bank transfer or virtual account activity, we may retain the matching bank reference. Wallet passwords and PINs are not needed for our support checks.

Cookie settings

Cookies can keep a session active, remember a display choice or help us understand an access error. You can adjust browser cookie controls, although removing them may require another login. A cookie request should state the device and browser involved so we can respond clearly.

Device protection

We may record device type, browser details, login time and related signals to protect an account from unfamiliar access. If you see a session you do not recognise, end the session, change your account credential and contact support with the time shown.

Record retention

We keep different records for different periods rather than storing everything indefinitely. Account, wallet and support records may remain while needed for service, dispute review or legal duties. Ask us about a specific record and we will explain the available retention response.

Changing your data

You can request access, correction or deletion by using the account support route and confirming ownership. Include the data category, such as phone, cookie, device or wallet reference. We assess the request under applicable rules and explain any limit that depends on local law.

Privacy Policy Answers Before You Join

These Privacy Policy answers focus on the questions we expect you to ask before opening an account or returning to the lobby. They cover what we collect, why wallet references appear, how device details are used and how to request a change. If your question concerns a particular login, Lightning Roulette session, Fish Hunter entry or QRIS record, include that detail when contacting us so we can identify the relevant event.

The okidr Privacy Policy covers account details, phone verification, login and device signals, cookies, wallet references, support messages and retention. It explains why we handle each category, how to ask about your records and which requests may depend on local law.

We may collect your phone number, verification result, account settings, login times and device details connected with access. If you contact support about a QRIS status or a Lightning Roulette session, the message and related reference can also become part of the support record.

No. A DANA or OVO check may use a provider reference, status and time to match activity, but we do not need your wallet password or PIN for that check. The same approach applies to GoPay, QRIS, bank transfer and virtual account questions.

Use the signed-in account support route and ask for a copy of the data category you want checked. State whether you mean profile details, cookies, device signals, wallet references or support records. We may confirm account ownership before sharing information linked to your profile.

Yes, you can request a correction or deletion through the account support route. Include the specific record and reason, such as an incorrect phone detail or an outdated device entry. We review the request under applicable rules, and some retention may depend on local law.

Cookies can maintain a login session, remember a setting or help diagnose an access issue. You can change cookie controls in your browser, but clearing them may require another login. Tell us your device and browser if you want help with a cookie-related request.

The policy applies to the account and services available in Indonesia where local law permits. Access depends on local law, so availability can differ by location or service. If you are unsure about an account step, contact support before sending wallet or identity details.