Reference

Terms & Conditions For edm303 Access

edm303 Terms & Conditions explain how your account, lobby access and payment activity work from the first verification step.

Account rulesWallet checksPolicy accessSupport route
edm303 Terms & Conditions For edm303 Access
TERMS HELP DESK

Where To Ask About Policy Steps

A clear support path helps when a Terms & Conditions question affects your account or wallet status. We ask you to contact support from the account area and include the phone number connected to your profile, the relevant policy point and any payment reference. This lets us separate an access question from a receipt or verification question without asking you to repeat the full history. If your account cannot open, use the same support route from the sign-in screen and describe the device path you tried.

Team online

Account access

For a question about account eligibility or phone verification, contact our support desk through the account support path. Include your registered phone number and the exact message shown before access stopped, so we can match the request to the relevant Terms & Conditions clause.

Payment records

When a DANA, OVO, GoPay or QRIS receipt does not match your account status, send the payment reference through support. We use the reference, selected payment route and account details to check the record without asking you to share a wallet password or private security code.

Policy changes

To ask about a wording change or request clarification, quote the section heading and explain what you believe needs correction. We will respond through the contact details attached to your account, while any revised Terms & Conditions remain available on the policy page.

ACCOUNT SAFEGUARDS

What We Handle Under These Terms

Our Terms & Conditions describe the practical controls around account data, cookies, security and retention.

Data handling

We use your account details for account creation, phone verification, payment matching and support. A request about personal data should identify the registered phone number and the specific record involved, allowing us to check ownership before discussing or changing account information.

Cookie controls

Cookies may retain a sign-in preference or help us understand whether a policy page loads correctly. You can manage cookie settings in your browser, but switching them off may require you to repeat the account step or sign in again on your mobile device.

Account security

Keep your registered phone, sign-in details and verification messages private. We will not ask for a wallet password in a support reply. If you suspect another person accessed your account, contact support promptly and include the device path and time you noticed the issue.

Record retention

We retain account, payment and support records only as needed for security checks, dispute handling and the policy duties that apply to the service. A retention question should name the record type, such as a QRIS receipt or phone verification request, rather than sending sensitive credentials.

Change requests

You may ask us to correct account details or clarify how a clause affects your access. Send the request through the account support path with your registered phone number and a precise description. We may request an additional account check before applying a change.

Policy contact

For a Terms & Conditions question, quote the page heading and the sentence you need explained. Our support team can connect the question to account, payment or access records, including a virtual account or bank transfer reference, without requiring unrelated personal documents.

Terms & Conditions Questions For Indonesia

The answers below address the policy questions we hear before an account is opened or a payment is checked. They cover eligibility, account information, wallet records, cookies, policy changes and requests for access or correction. If your situation is unusual, quote the relevant Terms & Conditions wording when you contact us. We can then review the account step, payment reference or device message connected to your question.

They cover account opening, phone verification, permitted access, payment records, security, cookies, support requests, policy changes and account closure. They also explain why we may pause an account check. Read them before opening an account, because access depends on local law and your details must remain accurate.

Yes. Our account path uses phone verification before account access is enabled. Keep control of the registered number and never share a verification message with another person. If the step fails, contact support from the sign-in path with the device message you received.

The Terms & Conditions require payment activity to match the account details and route selected in your account. For DANA or QRIS, keep the receipt reference available. We may pause status confirmation when the reference, account identity or payment ownership cannot be matched.

You can request a correction through the account support path. Include your registered phone number, the field that is wrong and the requested correction. We may ask for an ownership check before changing it, and we will explain if a record must remain for security or dispute handling.

Cookies can retain a sign-in preference and help us check whether policy pages work on your device. Browser settings let you remove or restrict them. If you disable required cookies, you may need to sign in again or repeat an account step on mobile.

Access may be paused when phone verification, account details or payment ownership needs checking. We do not describe access as available everywhere: it depends on local law. If you believe a pause is incorrect, contact support with the exact message and account phone number.

We publish revised wording on the policy page and identify the changed terms there. Before continuing, read the updated section, especially where it concerns account access, payment records or data handling. If a sentence is unclear, quote it in a support request for clarification.