Reference

Legal terms for your kupu 178 account

DANA, QRIS, account verification and the lobby path are covered by clear policy terms, so you can understand each step before opening an account.

Local-law accessClear account termsWallet record clarityDirect policy support
kupu 178 Legal terms for your kupu 178 account
CONTACT ROUTES

Contact routes for Legal questions

A clear contact route matters when a Legal question affects your account or wallet record. We keep policy help close to the account area, so you can refer to the relevant login step, payment reference or verification prompt rather than explain the whole case again. Where local law permits, our support path can help you understand access wording, request a data correction or ask why a policy check is pending. Use the route that matches the issue below.

Team online

Account policy desk

For access depends on local law questions, open the account support path and include your registered phone detail. We can point you to the policy clause connected with login, location checks or eligibility before you continue to the lobby.

Wallet record help

If a DANA, OVO, GoPay or QRIS reference does not match your account, send the payment date and reference through support. We use those details to locate the relevant record without asking you to repeat unrelated account history.

Policy change request

To ask for a correction, access copy or policy clarification, use the contact route shown after login. State the requested change clearly and attach only the account details needed to identify the record under discussion.

CONTROL DETAILS

How our Legal controls work

Legal protection depends on practical account controls, not broad promises. We connect policy handling to the steps you can see: phone verification before account access, wallet reference checks, device login behaviour and…

Data handling

We use account details to operate access checks, connect wallet records and respond to Legal requests. Phone verification is completed before account access, helping us relate a policy request to the correct account without relying on an unverified message.

Cookies and sessions

Cookies and session records can keep your chosen device path working between login screens. They may also help us identify an interrupted account session. Your browser settings control some cookie behaviour, while policy rules explain which records support account security.

Account security

A clear phone verification step helps protect access before you reach titles such as JetX Mobile Play. If a login looks unusual or a device changes, security checks may require account confirmation before wallet or lobby access continues.

Record retention

We retain account, verification and payment references for the period needed to operate the service, address disputes and meet applicable legal duties. A request about a particular record should include its account step or transaction reference so we can locate it.

Who to contact

Our account support path is the first contact for Legal matters involving access, data or wallet records. Include your registered phone detail, the policy concern and any DANA, QRIS or bank reference that helps us identify the relevant event.

Requesting changes

You can ask us to correct an inaccurate account detail, explain a policy decision or provide the record connected with your request. We may confirm account ownership first, then respond using the contact route available inside your signed-in account.

Legal answers before you open an account

These Legal answers cover the questions that usually arise before account creation or when a wallet check interrupts access. We keep the wording tied to real account steps, including phone verification, payment references and mobile sessions. If your case depends on a local rule, the applicable position depends on local law and should be checked through the account support route.

Legal access means your ability to open and use an account is assessed under the rules that apply to your location. On kupu 178, access depends on local law. A phone verification step may appear before you reach the lobby or use a wallet route.

We use account data for phone verification, access checks, wallet record matching and responses to Legal requests. The policy also explains cookies, session records and retention. When you ask about a record, we may confirm account ownership before discussing its contents.

Yes. Use the support path inside your account and describe the detail you believe is inaccurate. Include the related login step, verification event or payment reference where possible. We may request confirmation before changing a record connected with your account.

A DANA or QRIS reference can be checked to connect the payment event with the correct account and policy record. Similar checks may apply to OVO, GoPay, bank transfer or virtual account activity. The purpose is record accuracy and account protection.

It can. Where local law permits, account and lobby access can follow the normal policy path. If a local rule affects eligibility or a service category such as Live Baccarat Gold or Liga 1 Mix Parlay, that rule takes priority over general access wording.

Sign in and use the account support route, then include your registered phone detail and a short description of the Legal issue. Add a wallet reference if the matter concerns DANA, OVO, GoPay, QRIS or a bank transfer record.

Yes. Send a request through the account support route and specify whether you want cookie handling, session records or retention explained. We may verify the account first, then provide the policy wording relevant to your device path and stored record.