Reference

erek erek 20 Privacy Policy Explained

The erek erek 20 Privacy Policy tells you what account, phone, device and wallet details we collect, why we use them and how you can ask about them.

Account dataDevice choicesWallet recordsContact requests
erek erek 20 erek erek 20 Privacy Policy Explained
CONTACT YOUR DESK

Where To Ask About Privacy Policy

A clear contact path matters when a phone number, wallet reference or device record needs attention.

Account help Use the account help route when your Privacy Policy question concerns phone verification, login…
Wallet status For a privacy question linked to DANA, OVO, GoPay or QRIS, include the payment…
Access request If you want to ask for a copy, correction or removal of account data…
SIX DATA CONTROLS

Six Privacy Checks For Your Account

The Privacy Policy is designed around the moments when data is most useful and most sensitive: account creation, phone verification, wallet activity, device access, support contact and account closure.

Account collection

When you open an account, we collect the details needed to create your profile and confirm the phone step before access. The Privacy Policy explains why contact and verification details are connected to your account, rather than treated as anonymous lobby activity.

Device signals

Your mobile browser or desktop session can produce device and login signals used to detect unusual access. These signals help us protect the account path from the login screen to the lobby; they are handled as security data under the Privacy Policy.

Cookies

Cookies can remember a session choice, support account security and help us understand whether a page loads correctly. You can manage cookie settings in your browser, although changing them may affect login continuity or the way policy pages display.

Payment references

A wallet receipt, bank transfer reference or virtual account number helps us match a payment status to the correct account. We use those references for reconciliation and support, while the Privacy Policy sets boundaries around their purpose and storage.

Retention choices

We retain records only for the period needed for account operation, security, support and applicable legal duties. When a record is no longer needed for those purposes, our retention process allows it to be deleted or separated from active account handling.

Policy requests

You can contact us to ask what personal data we hold, request a correction or ask about deletion where local law permits. We may request identity checks before responding, and we explain any limit when a record must remain for security or legal reasons.

Privacy Policy Questions You May Have

These Privacy Policy answers address the practical searches we expect before you open an account or connect an Indonesian wallet. They cover the data linked to a phone verification step, the records created by DANA or QRIS, browser cookies, account access and requests sent through our support route. If your situation is not listed, contact us from the account help path with the smallest useful amount of personal detail.

It covers how we handle account details, phone verification, device signals, cookies, wallet references, support messages and retention. It also explains how you can ask for access, correction or deletion of your data, subject to identity checks and local requirements.

We may collect contact and account details, the result of the phone verification step, login activity and device signals. The Privacy Policy explains how these records support account access and security without requiring you to send a password to support.

Yes. A DANA or QRIS transaction can create a receipt, reference or status record that we use to match the request with your account. The same approach can apply to OVO, GoPay, bank transfer and virtual account activity.

Send a clear request through the support contact shown on erekerek20.club, naming the account detail you want copied or corrected. We may verify your identity first, then explain the available action and any restriction required by local law.

Yes. Cookies may keep a session active, support login security or help us identify page-loading problems on a mobile browser. Your browser controls these settings, but disabling them can interrupt the path from account access to the lobby.

We keep account, security, support and payment-reference records for as long as they serve those purposes or are required by applicable legal duties. When retention is no longer needed, the record can be deleted or separated from active use.

Yes. Use the support contact on our domain and explain that you cannot access the account, without sharing your password. Include a safe account identifier or payment reference when available so we can check the request while protecting the account.