Reference

Terms & Conditions For Your gendis66 Account

gendis66 Terms & Conditions explain how you open, use and protect your account across our Indonesia lobby.

Clear account stepsLocal wallet rulesPolicy accessSupport path
gendis66 Terms & Conditions For Your gendis66 Account
HELP WITH TERMS

Where To Ask About Account Rules

Questions about Terms & Conditions should reach us through the account support route rather than an informal message elsewhere.

Account desk Use the support link beside your account area when a clause affects login, phone…
Wallet status For DANA, OVO, GoPay or QRIS questions, send the payment reference and displayed status…
Policy request If you need a clause explained, ask directly for the relevant section and we…
ACCOUNT SAFEGUARDS

How We Apply These Terms

The policy works alongside practical account controls rather than replacing them. We use the details attached to your account to match phone verification, payment references and security events…

Data handling

We handle account details, phone verification records and payment references for account operation, security checks and support responses.

Cookie use

Cookies may keep your session, language choice and access settings working between pages.

Account security

You are responsible for keeping login details private and contacting us when access looks unusual.

Record retention

We retain account and transaction records for the period needed to operate the account, resolve disputes, meet local requirements and…

Policy changes

When wording changes, we place the updated Terms & Conditions where you can access them and may request that you…

Correction requests

You can ask us to correct account details, clarify a policy decision or explain how a clause affected a payment…

Terms & Conditions Questions For Indonesia

These Terms & Conditions answers address the account questions we hear most often before access begins. We keep the wording practical: what you accept, how we check ownership, what happens to data and where to ask for a correction. If your situation is not covered, contact support with the account detail or payment reference connected to the question.

You can open the Terms & Conditions page from the site policy area before creating an account. Read the current version together with any displayed account or payment notice. If a clause is unclear, contact support daily from 08:00 to 23:00 WIB for an explanation.

Yes. The same Terms & Conditions apply when you use a mobile browser, tablet or desktop. A mobile session may request another login if cookies are blocked or the session expires. Your account remains subject to phone verification and the same access rules.

You provide accurate registration details and complete phone verification before account access. You also agree to protect your login details and use one account for yourself. We may request an ownership check before changing information or processing a related account instruction.

The terms require you to follow the payment instructions and keep the correct receipt or reference. A wallet status may remain pending while the payment rail responds. We can check the account record, but the displayed result also depends on the wallet provider or bank process.

Yes. Send a correction request through the registered support route and describe the field that needs attention. We first confirm account ownership, then assess the request against the applicable Terms & Conditions and local requirements. Do not send a password or private security code.

We publish revised wording in the policy area and identify when the change takes effect where needed. You should read the new text before continuing account access. Where local law permits, continued use after that point follows the revised Terms & Conditions.

Access may be paused or restricted when account details cannot be verified, security activity needs checking or a rule in the Terms & Conditions is not followed. Eligibility depends on local law. Contact support with the displayed message so we can explain the next account step.