Reference

Privacy Policy for Your erek2 Account

erek2 Privacy Policy explains how we collect, use and protect the details connected with your account, wallet status and lobby access.

Account dataWallet recordsCookie choicesContact requests
erek2 Privacy Policy for Your erek2 Account
CONTACT THE DESK

Privacy Questions Through Your Account Path

A clear contact path matters when a Privacy Policy question concerns your name, phone number, device record or payment reference.

Account contact Use the support contact shown after account access and identify the phone or email attached to your erek2 profile. We use those details to locate the correct record before discussing a Privacy Policy request, while keeping wallet PINs and full payment passwords out of the conversation.
Payment query For a DANA, OVO, GoPay or QRIS data question, share the transaction date, amount shown in your account and the payment reference visible in the cashier history. We use that limited trail to check status without asking you to disclose a wallet PIN or banking password.
Access concern If your phone verification or Mobile Login Indonesia session looks unfamiliar, contact us through the account support path and mention the device and sign-in time shown to you. We can review the access record, ask for account details, and help protect the session where local law permits.
DATA HANDLING

Six Privacy Controls We Keep Visible

We handle Privacy Policy requests through identifiable account records rather than broad, unverified messages.

Account details

We use your submitted account details to create the profile, complete phone verification and respond to a Privacy Policy request. We do not need your wallet PIN for these steps. Keep your contact detail current so an access or correction request can be matched to the right account.

Session security

Sign-in time, browser details and device signals help us spot an unusual account session, including a return from a new phone. These records support access checks around Mobile Login Indonesia and may be reviewed when you report a session you do not recognise.

Cookies

Cookies can keep your sign-in flow and page choices consistent between the account area and lobby. Your browser settings can remove or restrict them. If you change those settings, we may ask you to verify your account again before showing wallet or profile details.

Payment trails

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference lets us connect a cashier event with your account history. We use the reference for status checks and disputes, not as a substitute for your private wallet credential or banking password.

Retention requests

We keep account, access and payment records for the period needed for service records, security checks, disputes or legal duties. You can ask us whether a record can be corrected or removed; the result can depend on an active account matter or a legal retention requirement.

Policy changes

When our Privacy Policy changes, we place the revised wording on this policy page and identify the updated date where applicable. Check it before opening an account or changing your payment details. Your continued account use after a permitted update is handled under the wording then displayed.

Privacy Policy Questions About erek2

These Privacy Policy answers focus on the account and payment questions you are most likely to have before opening an erek2 account. We explain the practical path for data access, correction, cookies, device records and wallet references. If your question concerns eligibility or access in Indonesia, that outcome depends on local law. For a record-specific request, use the support contact available from your account area and include enough detail for us to identify the relevant record.

The erek2 Privacy Policy covers account details, phone verification, sign-in and device records, cookies, support messages, game activity and payment references. It explains how we use those records for account operation, security, status checks and legal duties, with access depending on local law.

These rails create payment references that can appear in your account history. We use a DANA, OVO, GoPay or QRIS reference to check a cashier status or dispute, but we do not ask for your wallet PIN. Bank transfer and virtual account references follow the same account-matching purpose.

Yes. Send a correction request through the account support contact, using the phone or email attached to your profile and explaining which detail is wrong. We may ask for an account check before changing it, so another person cannot alter your record.

Use the support contact shown in your account area and ask for a data access request. Include your account phone or email and the date range you need. We verify the request first, then explain which records can be supplied where local law permits.

Yes. Cookies can support sign-in continuity and page preferences when you use Mobile Login Indonesia on a phone or browser. You can restrict them through browser settings, but we may require another phone verification step and some account pages may not work as expected.

We retain records for the time needed to operate the account, check payment status, resolve disputes, protect sessions or meet legal duties. A request to remove data is assessed against those needs. We can explain the applicable reason through the account support path.

Yes. Ask us about account-linked activity such as an entry to Aviator Mobile Play, Fishing War Mobile Play or Serie A Match Bet. We use the account details and date you provide to locate the record, while access or deletion remains subject to local law.