Reference

rukantogel Legal: Know Your Account Terms

At rukantogel, our Legal page explains the terms behind account access, wallet records and policy requests before you open an account.

Account termsData handlingPolicy contact
rukantogel rukantogel Legal: Know Your Account Terms
POLICY CONTACT

Where Legal Questions Meet Account Help

A clear contact route matters when a Legal clause affects your account or payment record. We keep policy questions separate from game-room requests so the right details reach the right team. Use the support form beside the account and cashier paths, include your registered contact and a short description, and avoid sending wallet passwords or one-time codes. We can then explain the relevant policy step.

Team online

Policy request form

Send a Legal question through the on-site support form with your registered contact and the clause you need explained; we use that reference to keep the reply tied to your account.

Account access query

If a policy check pauses account entry, tell us whether you are using a mobile browser or desktop and include the displayed message, without sharing your password or verification code.

Payment record query

For DANA, OVO, GoPay, QRIS, bank transfer or virtual account questions, attach the transaction reference rather than wallet credentials so we can trace the policy request safely.

DATA PRACTICE

How Legal Controls Data and Access

Legal handling is practical: we connect account records to the request that created them, limit internal access to the work being performed, and keep a route for correction.

Account records

We use the account details you submit to identify your profile, confirm a policy request and match payment references from DANA, OVO, GoPay, QRIS or bank rails.

Cookie choices

Cookies may support sign-in continuity and policy-page settings in your browser. Our Legal wording explains their role, so you can clear browser data and ask how a setting affects access.

Security checks

Before changing account access or payment records, we may ask for a registered contact or verification step. Never send a password or one-time code in a support request.

Record retention

We retain selected account and transaction records when needed for account history, dispute handling or a lawful request. The applicable Legal wording explains why a record remains stored.

Correction request

If your name, contact detail or payment reference is incorrect, use the policy contact path and describe the specific field. We can assess the correction without asking for unrelated data.

Access decisions

Account eligibility and policy access depend on local law. If a restriction applies, we explain the relevant route where local law permits instead of asking you to bypass the check.

Legal Answers Before You Open an Account

These Legal answers address the questions we expect before an account is opened: local access, personal data, cookies, payment references and policy changes. Read them with the full terms, then use the support path if your situation involves a specific account or transaction.

It covers account access, policy wording, personal data, cookies, security checks, retention and payment references. It also explains how to contact us when a term or account decision needs clarification.

Yes. Account eligibility and access depend on local law. We apply the relevant restriction where local law permits and ask you to read the terms before opening or using an account.

We use payment references to connect an account request with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. Do not send wallet passwords, PINs or one-time codes.

Yes. Send a correction request through the support form from your registered contact, identify the inaccurate field, and explain the requested change. We assess it under the applicable Legal process.

Cookies can support sign-in continuity and saved page settings in your browser. The Legal wording describes their purpose so you can manage browser data with a clearer understanding of the effect.

Selected records may remain when needed for account history, payment tracing, dispute handling or a lawful request. The relevant Legal wording explains the reason for retention and the applicable process.

Use the on-site support form beside the account path, include your registered contact and the displayed decision or clause, and leave out passwords and one-time codes so we can review the request safely.