Reference

Privacy Policy For Your kas77 Account

kas77 Privacy Policy explains what account, device and wallet details we use, why we use them, and how you can ask about them before opening an account.

Account dataDevice choicesWallet privacyContact route
kas77 Privacy Policy For Your kas77 Account
CONTACT ROUTES

Ask About Privacy Through Account Support

A direct support path helps you raise a Privacy Policy question without posting account details in a public channel. Use the support chat linked to your account area and tell us whether your request concerns phone verification, a device sign-in, a wallet reference or a data correction. We may ask for account details to locate the right record, but never ask you to disclose a wallet password. From Jakarta or Surabaya, the same account route applies where local law permits.

Team online

Privacy request

Use the account support chat to ask what personal data we hold, why a field appears in your account, or how to request a correction. Include your registered phone number only through the secure account path so we can match your request without exposing it in an open message.

Wallet record

If a DANA, OVO, GoPay or QRIS reference appears incorrectly, send the receipt reference through support beside the cashier path. We compare the account event with the payment record and explain what can be corrected, while keeping your wallet PIN and login password out of the request.

Access concern

For an unfamiliar login or a phone verification issue, contact support before sharing a screenshot containing private codes. We can check the account event, ask you to complete the required account step, and explain whether the requested access is available where local law permits.

DATA PRACTICE

What We Do With Account And Device Data

Privacy Policy choices matter most when you know what happens behind each account step.

Account details

We use your registered phone number and account identifiers to complete phone verification, recover access and connect support messages to…

Device signals

A mobile or desktop sign-in can create device and browser records such as session details, operating environment and security events.

Cookies

Session cookies help keep your account connected as you move between account help, wallet status and the lobby.

Payment references

For DANA, OVO, GoPay, QRIS, bank transfer and virtual account requests, we retain transaction references and status details needed to…

Security handling

We use account events, phone verification and access records to investigate suspicious sign-ins or a stalled wallet status.

Retention and changes

We keep personal data for the period needed to provide the requested account service, answer a support matter or meet…

Privacy Policy Answers For kas77 Accounts

These Privacy Policy answers address the searches we hear most often before account access. They cover account data, cookies, phone verification, payment references, device records and requests for changes. If your situation is not listed, use the secure support chat attached to your account and describe the specific record or access event.

It covers data connected with your account, phone verification, sign-in device, session cookies, support messages and payment references. We use those details for account access, security, payment matching and required legal duties. Access remains subject to local law and applies where local law permits.

We use your phone number to create and identify your account, complete the phone verification step and help recover access. It can also help support locate the correct record when you ask about a login or wallet status. Do not send verification codes in public messages.

Yes. The Privacy Policy covers transaction references and status details linked to DANA, OVO, GoPay, QRIS, bank transfer and virtual account requests. We use these records to match an account event or receipt question, not to request your wallet password or PIN.

Session cookies help keep you signed in while you move between account help, wallet status and the lobby. Your browser settings let you clear or block them. After that change, the current session may end and you may need to complete phone verification when accessing your account again.

You can request a correction through the secure account support chat. Tell us which field is wrong and provide the account detail needed to locate it. We may confirm phone verification before changing anything, and we will explain if a record must remain for legal or payment reconciliation reasons.

We retain account, security, support and payment-reference data for as long as needed for the stated service, an unresolved request or applicable legal duties. The period can differ by record type. Ask support for the reason a particular record remains and whether a change request is available.

Use the support chat connected to your account area and label your message as a Privacy Policy request. You can ask about device access, cookies, phone verification, payment references or data changes. Share private details only through that secure route, and access is subject to local law.