Reference

Legal clarity before your account starts

cahayaslot puts its Legal access terms, data practices and account contact route in one place before you enter the lobby.

Policy accessData rightsPhone verificationIndonesia terms
cahayaslot Legal clarity before your account starts
POLICY HELP ROUTES

Get a clear answer when policy stalls

A policy question should not leave you guessing about your account, wallet status or access path.

Account policy request Use the support link inside your signed-in account for access questions, phone verification concerns…
Wallet status clarification If a DANA, OVO, GoPay or QRIS status affects a policy question, send the…
Data change request Ask us to correct or update account information through the same account support route.
DATA HANDLING DETAILS

See how our Legal process protects records

Legal clarity also means knowing what happens after you send a request. We use account details to verify the correct record, keep policy communications tied to the relevant request and limit changes…

Account data

We handle the information attached to your account, including your registered phone number and verification details, for access checks and support requests. Keep these details accurate so we can distinguish your request from another account using a similar wallet reference.

Cookie controls

Cookies can support sign-in continuity and remember browser-level settings. You can manage cookie permissions in your browser, but restricting them may interrupt the account path or require you to verify again before reaching policy and wallet pages.

Account security

We keep policy requests behind the signed-in account path and may ask for phone verification before discussing records. Never send a password in support messages; use the account contact route so the request can be associated with your own account.

Record retention

We retain records needed to administer account access, resolve wallet references and demonstrate how a policy request was handled. Retention can depend on the request type and local requirements, so ask support which record category applies to you.

Policy changes

When a Legal condition changes, we place the current wording in the relevant account or policy area. Check that page before continuing, particularly if you access from Surabaya or another location where local law may differ.

Who to contact

Our account support route is the right contact for data access, correction, deletion questions or an explanation of an eligibility check. State the request plainly, include your registered phone number and follow any verification step we return.

Your cahayaslot Legal questions answered

These answers cover the Legal points most often checked before an account is opened. We keep the wording practical: where access depends on local law, what data is connected to your account, how a correction request starts and which route should receive a policy question.

Access depends on local law. Before opening an account, check that use is permitted in your location and read the current policy wording. Where local law permits, our account path begins with accurate registration details and a phone verification step.

The Legal page explains jurisdiction-dependent access, account conditions, data handling, cookie choices, security checks, record retention and contact routes. It also names DANA, OVO, GoPay and QRIS as wallet context without treating every rail as available to every account.

Phone verification helps us connect a policy request to the correct account and reduce mistaken access changes. We may request it before discussing account records, changing registered details or completing an access check where local law permits.

Use the support link inside your signed-in account, state which field is incorrect and provide your registered phone number. We may ask for verification before changing the record, then use the account route to confirm how the request was handled.

Yes. Send a data request through the account support route and identify the account with your registered phone number. We may verify ownership first, then explain the relevant record category, its purpose and any retention condition that applies.

Start with the account support path and include the exact policy wording, status message or access concern. This lets us route the matter to the team handling account records and jurisdiction checks instead of treating it as a general lobby question.

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference can help us identify a payment-status question, but it does not replace account verification. We assess access separately and apply the wording that depends on local law.