Reference

Terms & Conditions for Your erek erek 41 Account

Clear Terms & Conditions set out how your erek erek 41 account, wallet activity and lobby access work before you open an account.

Account access rulesWallet and payment termsData and cookie handlingContact and change requests
erek erek 41 Terms & Conditions for Your erek erek 41 Account
POLICY HELP ROUTES

Get Help With Account Terms

A clear contact path helps when a Terms & Conditions question affects your account or wallet status. We ask you to contact support from the account path where possible, so our team can match the request with the correct profile and transaction record. Include the relevant date, payment rail and action you were taking; never send a password or full security code. Our support route can explain a clause, identify a missing verification step or record a request to change your details.

Team online

Account access question

Use the account support path when phone verification, a sign-in step or a device change appears to conflict with these Terms & Conditions. Tell us which step stopped you and whether you are using a mobile browser or computer, so we can check the correct access record.

Wallet status request

For a DANA, OVO, GoPay or QRIS status question, send the payment reference and the rail shown in your account. We use those details to compare the receipt with the wallet record and explain whether the Terms & Conditions require another verification step.

Policy change request

If a clause seems unclear or your personal details need correction, contact our support team with the section name and the change you seek. We will confirm the request path, ask for suitable account checks and tell you how the decision is recorded.

HOW WE APPLY TERMS

Data, Cookies and Account Safeguards

Our Terms & Conditions describe not only access to the lobby but also how we handle the account behind it.

Account details

We use your submitted account details to connect phone verification, access decisions and payment references. These Terms & Conditions require accurate details because a mismatch can pause an account check. If your phone number changes, contact support before attempting another access step.

Payment records

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference may be retained to reconcile a transaction and answer a policy dispute. We do not ask you to place a password or full security code in a payment message sent to support.

Cookies

Cookies can preserve the session route between account access and the lobby, including when you return from a payment page. These Terms & Conditions let you manage browser cookie settings, although switching them off may interrupt the account path or require another verification step.

Account security

You must keep login details private and sign out on a shared device. If an unfamiliar access event appears, contact support through the account path and stop further wallet activity until we complete the checks described in these Terms & Conditions.

Record retention

We retain account, transaction and support records for the period needed to operate the service, resolve disputes and meet legal duties. The retention period can differ by record type. You may ask support which category applies to a specific request without sending unnecessary personal details.

Change requests

To request correction, access or removal of personal details, name the account field and explain the change. We may verify ownership before acting. Our support team will record the request, explain any legal reason for keeping a record and confirm the next step under these Terms & Conditions.

Terms & Conditions Questions Answered

These answers focus on the account decisions that usually matter before access: what you accept, how payment records are checked, when local rules apply and how to ask for a correction. Read the full Terms & Conditions before opening an account, then use the support path if a clause does not match the account step shown to you.

They cover account creation, phone verification, permitted access, device sessions, payment references, data handling, cookies, account security, policy changes and closure requests. They also explain how we handle questions about DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity.

Yes. Account access and eligibility depends on local law, and you may use the service only where local law permits. You are responsible for checking the rules that apply where you are located. We may restrict an access step when a legal or verification condition is not met.

Phone verification connects the account to a contact detail you control and helps us identify the correct record when a wallet or device question arises. Under these Terms & Conditions, an incomplete check can pause access until the requested account detail is confirmed.

The terms require you to follow the payment route displayed in your account and keep the transaction reference. For DANA, QRIS, OVO or GoPay, we compare the reference with the account record. A mismatch may require support review before the transaction status changes.

Yes. Contact support through the account path, identify the field that needs correction and explain why it is inaccurate. We may verify ownership before changing it. These Terms & Conditions allow us to retain a record when legal, security or dispute duties require it.

A new mobile browser or computer may trigger another sign-in or phone verification step because the session no longer matches the prior device path. The Terms & Conditions require you to protect the account and contact support if the new access was not initiated by you.

Use the support route named on the account page and mention the section title, clause and question. We can explain the operational meaning, record a wording concern and tell you when a revised version applies. Continued account use after an effective change means you accept it.