Reference

erek erek 02 Privacy Policy For Your Account

erek erek 02 Privacy Policy explains what we collect when you create an account, verify your phone, browse titles such as Auto Roulette Live or Pontianak Lucky Slots…

Account dataWallet detailsCookie choicesPolicy requests
erek erek 02 erek erek 02 Privacy Policy For Your Account
CONTACT ROUTES

Where Privacy Questions Reach Our Team

A clear contact route helps you resolve a Privacy Policy question without sending sensitive wallet details into a game chat.

Account data request Open the support path after signing in and state whether you want to view…
Wallet data question For DANA, OVO, GoPay, QRIS, bank transfer or virtual account records, include the payment…
Cookie preference help If a cookie choice does not remain saved on your mobile browser, contact us…
DATA PRACTICE

Six Privacy Checks Behind Your Account

Privacy work is tied to practical account events rather than broad promises.

Account details

We collect the account details needed for sign-in and phone verification, then connect them with your account activity.

Payment references

A DANA, OVO, GoPay or QRIS payment can leave a reference, amount and status needed to match your receipt.

Cookies and devices

Cookies can keep a policy choice or signed-in setting available on your browser.

Account security

We use phone verification and sign-in signals to check account access.

Retention periods

We keep account, security and payment references only for as long as needed for the stated account, support or legal…

Change requests

To request a correction or deletion, sign in, open the support route and describe the exact field or record.

Privacy Policy Answers For Indonesian Accounts

These Privacy Policy answers address the account and wallet questions you may search before opening access. We keep the wording practical: what we collect, why a device record appears, how to request a change and what happens when you use Indonesian payment rails. If your question is not covered, use the signed-in support route and include only the account details needed to identify your request.

The erek erek 02 Privacy Policy covers account details, phone verification, device and session records, cookies, support messages and payment references. It explains why we use each category when you sign in, browse titles, select DANA or QRIS, and request help with your account.

We use your phone number for the account verification step and to connect a privacy request with the correct account. It is not your DANA, OVO or GoPay password. If the number changes, contact support after signing in so the account record can be checked.

Yes. This Privacy Policy covers the payment reference, status and related account event for QRIS, DANA, OVO and GoPay. Bank transfer and virtual account references are handled for the same matching purpose. We do not ask you to provide a wallet PIN through support.

Sign in, open the account support route and name the data you want to view or correct. Include the verified phone or email attached to your account. We may confirm account ownership before responding, and a request record may remain for service and legal needs.

Cookies can remember a policy choice and help maintain a browser session. On mobile, clearing site cookies may sign you out and require phone verification again. Your browser settings control many cookie choices, while support can explain the related device record if a setting behaves unexpectedly.

We retain account, security, support and payment references for as long as needed for their stated purpose and applicable obligations. When retention is no longer needed, we remove the record or separate it from direct identifiers where that process is available.

You can submit a deletion request through the signed-in support path and identify the account record involved. We first check ownership and then assess which data can be removed. Some request, security or payment records may need to remain for a valid legal purpose.