Reference

Privacy Policy For Your km 789 Account

km 789 Privacy Policy explains how we collect, use and protect the details connected with your account, wallet status and lobby access.

Account clarityWallet dataCookie choicesSecurity requests
km 789 Privacy Policy For Your km 789 Account
CONTACT THE POLICY TEAM

Three Routes For Privacy Questions

A clear contact path helps you resolve a privacy question without explaining your entire account history.

Policy contact route Use the privacy contact option connected to your account area when you want to ask what data we hold, why it is used or how long it remains. Include your registered phone number only through the secure form, and we will use the account path to identify the request.
Wallet reference check For a question about DANA, OVO, GoPay or QRIS records, send the transaction reference, date and status shown in your cashier history. We use those fields to find the relevant record without asking you to reveal a wallet password or payment access code.
Access correction request If your name, phone detail or account record needs correction, tell us which field is inaccurate and provide the account step where you noticed it. We may confirm ownership through the verified phone route before changing personal details or disclosing account information.
SIX DATA SAFEGUARDS

What We Do With Account Details

Privacy work follows the account journey rather than a vague promise about data. We collect what is needed for access, wallet reconciliation, security checks and support, then restrict internal use to those…

Account records

We use your account details to provide login access, confirm the phone step and connect your account with the relevant lobby session. The record can include contact information, access timestamps and verification status, while payment credentials remain with the payment route rather than being treated as your password.

Cookies and settings

Cookies can keep a selected language, maintain a session and help us see whether a page such as Live Roulette Turbo loads correctly. You can manage cookie choices through your browser settings. Turning some cookies off may affect remembered access or page functions, but it does not erase an account record by itself.

Payment matching

A DANA, OVO, GoPay or QRIS reference lets us match a cashier action with the correct account and status. Bank transfer and virtual account records support the same check. We use the smallest practical set of transaction fields and do not ask you to provide a wallet PIN for this purpose.

Account security

We use phone verification, session checks and unusual-access signals to reduce the chance that another person enters your account. If a login or wallet status stalls, contact us through the account help route near the cashier. Never share a password or verification code in a support message.

Retention questions

Some records remain while they are needed for account administration, payment reconciliation, security work or a legal request that depends on local law. Retention can differ by record type. Ask through the policy route for the category involved, and we will explain the applicable period or reason for keeping it.

Change and deletion

You can ask us to correct personal details, explain our use of a record or consider deletion where applicable. A request may require phone verification so we do not change or disclose data to the wrong person. If access is discussed, we apply the rule where local law permits.

Privacy Policy Answers For km 789

These Privacy Policy answers address the account and payment questions you are most likely to have before opening an account. We keep each answer tied to an actual data path, from phone verification and cookies to DANA, OVO, GoPay, QRIS, bank transfer and virtual account references. If your situation is not covered, use the policy contact route and avoid sending passwords, wallet PINs or verification codes.

The km 789 Privacy Policy covers account details, phone verification, login and device signals, cookies, support messages and payment references. It explains how we use those records for access, security, reconciliation and support. It also describes how to ask for correction, retention details or another privacy decision.

No. The Privacy Policy describes our use of transaction references and status details from DANA or QRIS, not your wallet password or PIN. We use the reference, date and amount to match an account action. Send those limited fields through the secure contact route if a status needs checking.

We use phone verification to confirm that the person requesting account access or a data change controls the registered contact route. We retain the verification result rather than asking support to record your code. If you need to correct the phone detail, request that change through the policy contact path.

Yes. Under the Privacy Policy, you can identify the account field that is wrong and explain where you saw the error. We may complete an ownership check through your verified phone route before making a change. Do not include a password, wallet PIN or one-time verification code in the request.

Retention depends on the record and its purpose. Account access, payment reconciliation, security and legal requirements can each require a different period. The Privacy Policy does not treat every record alike. Ask us to identify the category, and we will explain the applicable retention reason where local law permits.

You can manage cookies through your browser controls and, where offered, the site preference setting. Some cookies support login continuity, saved choices or page operation, while others help us understand whether pages work. Removing them may require a fresh login, but it does not automatically delete your account data.

Use the privacy contact option beside the cashier or account help route, select the relevant subject and provide a short description. For DANA, OVO, GoPay or QRIS questions, add the visible reference and date. We may verify your phone before discussing personal data or changing an account record.