Reference

okeslot Privacy Policy for Your Account

Our Privacy Policy explains how okeslot handles the account details connected with DANA, OVO, GoPay and QRIS activity.

Account dataWallet recordsCookie choicesPolicy requests

Privacy Policy for DANA and QRIS Records

okeslot Service availability depends on jurisdiction. Users are responsible for checking local law before access.

This Privacy Policy covers details you provide during account creation, including contact information and phone verification data, as well as records created when you use DANA, OVO, GoPay, QRIS, bank transfer or a virtual account. We use these details to connect activity to the correct account,

1
check payment status, protect access and respond to a policy request. Browser, device and cookie signals may help us remember settings or detect unusual sign-in behaviour. If you open the lobby from Yogyakarta or another Indonesian location, local access and processing requirements still depend on local
2
law. We may update this page when our handling practices change, and the current version applies from its displayed date. Contact us through the account support route if you need clarification before opening an account.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

REQUEST A RESPONSE

Get Privacy Help Beside Your Account

A clear support path helps you ask about the Privacy Policy without searching through payment screens. Open the support route shown inside your account and include the email or phone detail linked to your profile. We use that step to identify the correct record, check wallet status when relevant and route your request to the right team.

Team online

Account questions

Ask how we use your registration details, phone verification record or sign-in data. Include the account contact detail you used so we can locate the correct Privacy Policy request.

Wallet records

For DANA, OVO, GoPay, QRIS or bank transfer records, tell us the payment rail and account date shown in your cashier history. Do not send a password or security code.

Correction requests

Use the account support route to request a correction, access copy or clarification. We may ask you to confirm account ownership before changing personal details or releasing account data.

HOW WE HANDLE DATA

From Mobile Cookies to Account Security

We keep the Privacy Policy practical by linking each data use to an account action you can recognise.

Data we receive

We may receive account details, phone verification results, sign-in records and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or a virtual account.

Cookies and browser signals

Cookies and device signals can remember selected settings, support session continuity and help identify unusual access. You can manage browser permissions, though some account functions may then need another check.

Account protection

Phone verification and sign-in checks help us connect requests to the right account. Never share your password or one-time security code through a message, payment note or support request.

Retention approach

We keep personal and payment records only for the period needed for account operation, security checks, dispute handling and legal duties. When records are no longer needed, we remove or de-identify them.

Access and changes

You can ask what personal data we hold or request a correction through the account support route. We may verify ownership before responding so another person cannot change your profile.

Policy contact

When you contact us about this Privacy Policy, include your account email or phone detail and a short description of the request. Avoid sending wallet passwords, card codes or full security credentials.

Privacy Policy Questions for okeslot

These answers address the Privacy Policy searches you may have before creating an account or checking a wallet record. If your request concerns a specific profile, use the support route inside your account and provide only the details needed to identify it.

The okeslot Privacy Policy covers account details, phone verification, sign-in activity, cookies, device signals, support messages and payment references linked to DANA, OVO, GoPay, QRIS, bank transfer or a virtual account.

Yes. The Privacy Policy explains how we use payment references and status records from DANA and QRIS, along with OVO, GoPay, bank transfer and virtual account activity, to connect transactions with your account.

Use the support route shown inside your account and ask for an access copy. Include the email or phone detail linked to your profile; we may verify account ownership before responding.

You can request a correction through account support. Tell us which profile detail is inaccurate and provide the linked account contact detail. We may complete an ownership check before making any change.

Cookies can keep a session connected, remember selected settings and help identify unusual sign-in behaviour when you move from a mobile browser into the lobby. Browser controls can manage permissions.

We retain personal and payment records for as long as needed for account operation, security, dispute handling and legal duties. After that period, records are removed or de-identified where appropriate.

Yes. Account access, data handling and any related request depend on local law. If you are in Indonesia, we apply the policy to the extent permitted for your location and account situation.

okeslot Privacy Policy for Your Account

Get Privacy Help Beside Your Account

Account questions

Wallet records

Correction requests

From Mobile Cookies to Account Security

Data we receive

Cookies and browser signals

Account protection

Retention approach

Access and changes

Policy contact

Privacy Policy Questions for okeslot

01 What does the okeslot Privacy Policy cover?

02 Does the Privacy Policy cover DANA and QRIS activity?

03 How can I request my data from okeslot?

04 Can I correct details covered by the Privacy Policy?

05 Why does okeslot use cookies on mobile browsers?

06 How long does okeslot keep personal data?

07 Does access under this Privacy Policy depend on local law?

Related Pages