Reference

erek erek 37 Privacy Policy

Our Privacy Policy explains how we collect, use and protect the details connected with your erek erek 37 account, including phone verification, wallet status and activity across titles…

Account dataWallet recordsCookie choicesAccess requests
erek erek 37 erek erek 37 Privacy Policy
HELP PATHS

Check Privacy Requests Beside Account Help

A clear contact route matters when a privacy request involves an account or wallet reference. From your account help area, tell us whether you need a copy, correction or explanation of data linked with your phone verification. Include the email or phone detail used at account opening, but do not send a password or full wallet credentials. We can then connect the request with the correct record and explain the next step.

Team online

Account privacy request

Use the account help path for a copy, correction or deletion question. We ask for the phone or email attached to your account so we can check identity before discussing personal data, while keeping passwords and wallet PINs out of the request.

Wallet record check

If a DANA, OVO, GoPay or QRIS reference appears incorrectly, send the payment date, amount reference and account contact detail through account help. We use those particulars to locate the relevant record without requesting your private wallet password.

Access and eligibility

For questions about whether the service may be accessed from your location, we explain the applicable account route and policy wording. Availability depends on local law, so you should check the rule that applies to you before opening or continuing an account.

DATA PRACTICE

Browse How We Handle Your Data

We keep privacy handling tied to ordinary account operations rather than collecting details without a purpose.

Collection purpose

We collect contact and verification details to create your account, confirm account control and respond to requests. Activity records may include a selected title such as La Liga Over Under or Fishing War Fast Round when that detail is needed to explain an account event.

Payment matching

DANA, OVO, GoPay and QRIS references are used to match a wallet action with your account and check a receipt or status question. Bank transfer and virtual account references can serve the same purpose when you choose those routes.

Cookie controls

Cookies can remember a browser session and help us understand whether an account page opened correctly. You can manage browser cookie settings on your phone or computer, though changing them may affect sign-in continuity and the way policy pages load.

Account protection

Phone verification, sign-in records and device signals help us identify unusual access. We do not ask for your password, wallet PIN or one-time code through an unsolicited message, and you should close any request that asks for those details.

Retention choices

We retain personal and transaction records only for the operational, security and legal purposes described in this policy. When a record is no longer needed for those purposes, our handling follows the deletion or anonymisation approach stated on this page.

Request changes

You may ask us to correct account details, explain a data use or provide a copy of relevant records. Send the request through account help with your verified contact detail; we may ask for an additional account step before releasing private data.

Find Answers About Privacy Policy

These answers address the searches we most often expect before an Indonesian account holder opens an account or checks a wallet record. Each response points back to the Privacy Policy and the practical account step connected with the request. If your case involves a payment reference or unusual sign-in, include only the details needed to identify the record.

It covers account creation, phone verification, sign-in and device records, cookies, lobby activity, payment references and contact requests. It also explains retention, security handling and how you can ask for access or correction of data linked with your account.

We use your phone detail to support account creation, confirm account control and help identify a privacy request. If a sign-in or wallet question reaches account help, the verified phone detail helps us avoid discussing private records with the wrong person.

Yes. The Privacy Policy covers references connected with DANA, OVO, GoPay and QRIS, including receipt or status details used to match a wallet event with your account. It also covers bank transfer and virtual account references when those routes are used.

Use the account help route and state that you want a copy of data covered by the Privacy Policy. Include the phone or email attached to your account, then complete any identity check we request before private records are released.

Yes. You can request a correction when your contact detail, verification record or another account field is inaccurate. Send the request through account help, identify the field that needs changing and provide the correct detail without sharing your password or wallet PIN.

Cookies can keep a browser session active and help us see whether an account page or policy page loads correctly. You can change cookie controls in your mobile or desktop browser, but some sign-in continuity or page functions may change afterward.

Access and eligibility depend on local law. Where local law permits, you can use the account route described on our site, complete phone verification and read this Privacy Policy before continuing. If your location or status changes, check the applicable local rule again.