Reference

Privacy Policy For Your enakcuan Account

Our Privacy Policy explains what we collect when you open an enakcuan account, enter the lobby, or check DANA and QRIS status.

Account dataCookie choicesPayment recordsAccess requests
enakcuan Privacy Policy For Your enakcuan Account
CONTACT YOUR WAY

Privacy Questions Reach Our Support Desk

A clear contact route helps you act on the Privacy Policy instead of searching through account screens.

Live chat Use live chat from the account support area between 09:00 and 22:00 Western Indonesia Time. Tell us whether your Privacy Policy request concerns registration, a mobile browser session, or a DANA, OVO, GoPay, or QRIS record so we can route it clearly.
Email request Email us from the address attached to your account when you need a Privacy Policy copy, data correction, or access explanation. Add your account identifier and the date of the relevant request; remove passwords, wallet PINs, identity images, and complete card or bank details.
Status check If a privacy request follows a pending bank transfer or virtual account entry, share the transaction reference rather than sensitive credentials. We can check the account trail, confirm what was recorded, and explain the next step while keeping your payment details limited to the support case.
DATA CONTROL DETAILS

What Our Privacy Policy Covers

We keep this Privacy Policy close to the account path because data choices often arise during a practical step: verification, a wallet check, or a device change.

Registration details

When you create an account, we collect the details needed to establish and protect that account, including contact data and verification responses. We use them to confirm that an access request belongs to you and to send replies about a Privacy Policy request, not to publish a profile in the lobby.

Device and session logs

Your browser or mobile device can send technical signals such as session time, operating environment, and security events. These logs help us identify repeated failed sign-ins or an unfamiliar device path. They are reviewed for account protection and support troubleshooting, including when a mobile lobby session stops unexpectedly.

Wallet references

DANA, OVO, GoPay, QRIS, bank transfer, and virtual account activity can create reference data linked to your account request. We use the reference, status, amount, and timing needed to reconcile a record. We do not ask you to place a wallet PIN or password in a support message.

Cookies and browser choices

Cookies can keep a session active and remember limited preferences, which reduces repeated account steps on a phone. Your browser settings can remove or restrict them, although some account functions may then require another sign-in. Our Privacy Policy treats cookie identifiers as technical records, not as public account content.

Account security

We use sign-in checks, session controls, and verification before discussing account-specific data. If you move from a mobile browser to desktop, we may ask for an additional account step before changing details. Keep your password and verification code private; support will not need either one to explain this policy.

Retention and requests

We keep different records for different periods according to their operational, security, dispute, and legal purpose. You can ask what remains connected to your account, request a correction, or ask whether deletion is available. Send the request through live chat or email, and we will explain any limit that depends on local law.

Privacy Policy Answers For Indonesia

These Privacy Policy answers address the account questions we hear most often from people using an Indonesian phone, browser, or wallet. They explain the practical route for checking stored data, changing account details, and asking about cookies or retention. If your case involves a specific DANA, QRIS, bank transfer, or virtual account reference, contact us with the reference and keep secret credentials out of the message.

The enakcuan Privacy Policy covers registration details, verification responses, device and session logs, cookie identifiers, support messages, and payment references. It explains why we use each category, how we protect account access, how retention works, and how you can ask for access or correction through live chat or email.

Send a request through live chat or email from the contact details connected with your account. State that you are requesting access under the Privacy Policy, add your account identifier and relevant date, and complete any reasonable identity check. Do not include your password, verification code, or wallet PIN.

We may store payment references and status details needed to match DANA, OVO, GoPay, or QRIS activity with your account request. The record can include timing and transaction reference details. We use it for reconciliation, security, and support, and we do not need your wallet PIN for a status check.

Yes, ask support to correct inaccurate account information through live chat or email. Use the contact address or phone connected with your account, describe the field that needs correction, and provide the relevant account step. We may verify the request before changing data, particularly after a device change.

The Privacy Policy treats cookies as technical records that can maintain a sign-in session or remember limited browser preferences. You can remove or restrict them in your mobile browser settings. After that change, you may need to sign in again, and some account steps may not function as intended.

Retention depends on the purpose of each record, including account security, payment reconciliation, dispute handling, operational needs, and legal requirements. We do not use one public period for every data type. Ask support what applies to your record, and we will explain any restriction that depends on local law.

You can ask whether deletion is available by contacting live chat or email with your account identifier. We assess the request against active account needs, security records, payment reconciliation, disputes, and legal duties. Where local law permits, we remove or limit eligible data and explain any records we must retain.