Reference

Open idcash Privacy Policy With Clarity

Our Privacy Policy explains what we collect when you create an idcash account, verify your phone, use DANA or QRIS, and move between the lobby and cashier on…

Account detailsWallet recordsDevice choicesContact routes
Explore Our Lobby Read FAQ
idcash Open idcash Privacy Policy With Clarity
CONTACT PATHS

Switch From Policy Questions To Support

A clear contact path matters when you want to ask about a Privacy Policy record rather than a lobby feature. Start from account help so we can match your request with the correct phone verification and sign-in record. If your question concerns a wallet reference, open the cashier status view and include the DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference shown there. We use the support route displayed in your account for follow-up.

Team online

Account help

Use the account help route when you want to ask what phone, sign-in or verification records we hold. Include the email or phone detail attached to your account, but never send a password or one-time code. We use the matching step to protect your request.

Wallet status

For a privacy question about a payment record, open the cashier status view and share the visible reference, date and rail name. DANA, OVO, GoPay and QRIS requests can then be separated from bank transfer or virtual account records before we respond.

Policy request

Ask for a copy, correction or removal through the support channel shown after account access. Tell us which record you mean, such as a device session or payment reference, so we can verify your identity without asking you to disclose private login credentials.

DATA PRACTICES

Browse idcash Data Handling In Practice

We separate the records needed to operate account access from the records used to keep a session secure.

Collection

We collect account details you enter, phone verification results, payment references and technical events such as browser type, device path and sign-in time. We use these details to provide the requested account service, investigate access issues and connect a cashier status question with the right record.

Cookies

Cookies and similar browser storage can remember a session, preserve a selected lobby page and help us identify repeated sign-in attempts. You can manage browser storage through your device settings, although switching it off may require another login before you reach Blackjack or League of Legends.

Account security

Phone verification is an account step before access, and we record security events around that check. We do not ask for your password or one-time code in a support message. If a sign-in looks unusual, we may request account details already associated with you before discussing a record.

Payment records

A DANA, OVO, GoPay or QRIS reference can show that a wallet request reached the cashier flow; a bank transfer or virtual account may create a separate reference. We retain the minimum payment detail needed to match status questions, security checks and account history.

Retention

We keep account, payment, support and security records only for the period needed for the purpose described in this Privacy Policy, account protection and applicable legal duties. Different records can have different retention periods, so a deletion request may not remove every entry immediately.

Your request

You may ask us to access, correct or delete personal details, or ask why a record is held. Send the request through account help with enough detail to locate it. We may verify ownership first, then explain any record that must remain for security or legal reasons.

Ask About Your Privacy Policy Rights

These Privacy Policy answers focus on the questions you may have before opening an account or checking a wallet record. We explain the account step, device behaviour, payment references and contact route in plain English for Indonesian access where local law permits. If your situation is unusual, use the policy request path rather than sending private credentials in chat.

It covers account details, phone verification, sign-in events, cookies, device data, payment references and support messages. It applies when you open an account, use DANA, OVO, GoPay, QRIS, bank transfer or virtual account, and browse available rooms where local law permits.

Phone verification helps us confirm that an account request belongs to you and helps protect later sign-ins. We record the verification result and related security event, but support will not ask you to reveal your password or one-time code.

Yes. The Privacy Policy covers payment references connected with DANA and QRIS, along with OVO, GoPay, bank transfer and virtual account activity. These references help us answer cashier status questions without requiring the full contents of your personal wallet.

We may record browser type, device path, session time, approximate technical settings and sign-in events. This helps restore your account flow and identify unusual access. A mobile browser and a desktop browser can therefore create separate session records under the same account.

Yes. Use the support route shown in account help and describe the record you want checked, such as a phone detail, device session or payment reference. We may verify account ownership first, then provide a copy or correct details that are inaccurate.

Send a deletion request through account help and identify the records concerned. We assess the request under the Privacy Policy and applicable duties. Some security, payment or legal records may need to remain for a stated period, and we will explain that outcome.

The policy is available for you to read, but account eligibility and processing can depend on local law. Where local law permits, you can open an account, complete phone verification and ask about your records through the support path shown in your account.

Related Pages

idcash Indonesia FAQ League of Legends idcash Casino Register