Reference

Privacy Policy for ikeh ikeh slot

Our Privacy Policy explains what data we collect when you open an ikeh ikeh slot account, access Jakarta Lucky Slots on mobile, or check a DANA wallet status.

Account dataWallet recordsDevice choicesCookie controls
ikeh ikeh slot Privacy Policy for ikeh ikeh slot
CONTACT ROUTES

Get Privacy Policy Help Without Guesswork

A clear contact path matters when a Privacy Policy question affects your account or wallet record. Start from the support route linked near your account and describe the request in plain English, including the phone number on the account and the relevant transaction reference when available. We use those details to locate the correct record without asking you to send a password, one-time code or full payment credential. If access or eligibility is discussed, our answer follows where local law permits.

Team online

Account request

Ask us to explain the personal data connected with your account, such as phone verification records, sign-in history or support messages. We may first confirm account ownership through the phone number already attached to your ikeh ikeh slot profile.

Wallet record

For a DANA, OVO, GoPay or QRIS question, include the payment reference and date rather than your wallet PIN. We can then check the account-side status and explain which transaction details the Privacy Policy covers.

Correction path

If your name, phone detail or account record needs correction, contact support through the account route and state the exact change. We assess the request against account security, retention duties and access requirements before updating anything.

DATA PRACTICE

What We Do With Privacy Policy Requests

We keep our Privacy Policy practical by connecting each data action to a visible account need. Phone verification helps us confirm account access, while device and sign-in signals help identify unusual sessions.

Collection

We collect details you provide during account creation, including contact information used for phone verification. We also receive technical signals from the browser or device, such as session details, so the account path can recognise an active sign-in.

Account security

A phone verification step helps separate an account owner from an unknown sign-in. Never send us your password or one-time code in a support message. We use the account route to confirm requests before discussing personal records.

Cookies

Cookies can remember session choices and help pages load in the expected order on a mobile browser. You can adjust cookie controls in your browser, although blocking required cookies may prevent the sign-in or Privacy Policy page from working fully.

Payment references

When you use QRIS, DANA or bank transfer, we need a reference, amount status and account match to reconcile the request. We do not ask for your wallet PIN, banking password or full card credentials through support.

Retention

We keep account, security and transaction records only while they support account operation, dispute handling, fraud checks or a legal duty. When a record is no longer needed for those purposes, our retention process marks it for removal or restricted storage.

Your request

You can ask what personal data we hold, request a correction, ask about use or raise a concern about deletion where local law permits. Include your account phone detail and a focused request so we can respond to the right record.

Privacy Policy Answers for Indonesian Accounts

These Privacy Policy answers address the account questions we expect before you open an ikeh ikeh slot profile or return to the lobby from a phone. Each answer describes the data path rather than making a general statement about the site. If your situation involves access, eligibility or a legal request, the outcome depends on local law and the account details we can verify.

The Privacy Policy covers data linked to your account and site use, including phone verification, sign-in and device signals, cookie choices, support messages and payment references. It explains why we use those records, how long we retain them and how you can contact us about a request.

We collect the contact details you submit for account creation and phone verification, plus technical session details from the browser or device. If you contact support about DANA or QRIS, we may also receive the transaction reference needed to locate the account-side record.

No. The Privacy Policy describes account-side payment references and status checks, not your private wallet credential. When you ask about DANA, OVO, GoPay or QRIS, send the reference and date only. Do not include a wallet PIN, banking password or one-time code.

Use the support route connected to your account and state whether you want access to the records we hold or a correction to a specific detail. Include the account phone number for verification, but do not send your password. We assess the request where local law permits.

We retain account, security and transaction records while they support account operation, dispute handling, fraud checks or a legal duty. The Privacy Policy does not treat every record alike; once a purpose ends, we review whether deletion or restricted storage is appropriate.

Required cookies can keep your session and page choices working as you move from phone verification to the lobby. Optional cookie controls can be changed in your browser. Blocking required cookies may interrupt sign-in or prevent the Privacy Policy page from loading correctly.

Yes. Send the question through the account support route with enough detail for us to identify the request, without sharing passwords or wallet credentials. Any answer about access or eligibility follows the Privacy Policy and depends on local law or where local law permits.