Reference

kasih777 Privacy Policy for Your Account

kasih777 Privacy Policy sets out how we handle your account details, phone verification, DANA receipts, QRIS records and cookie choices.

Clear data categoriesWallet record contextCookie choicesRequest path
kasih777 kasih777 Privacy Policy for Your Account
PRIVACY CONTACTS

Privacy Requests Through Our Account Path

A clear contact path helps when your name, phone number or wallet record needs attention. Start from your signed-in account and use the support route connected to account help; if login is blocked, use the contact option shown on the kasih777 site. Include the account identifier and the specific request so we can check the correct record without asking you to send unnecessary payment details.

Team online

Access request

Ask us what personal data is linked to your account, including phone verification events, login records and payment references connected with DANA, OVO, GoPay or QRIS.

Correction request

Tell us which account detail needs changing and why. We may ask you to complete an account check before editing contact details or correcting a wallet status record.

Receipt concern

Send the payment reference, date and rail name when a QRIS, bank transfer or virtual account receipt looks incorrect. We use those details to locate the matching record.

SIX DATA CHECKS

Six Checks Behind Our Data Handling

Our privacy process follows the same account steps you see on the site: phone verification, login, wallet status checks and access to the lobby.

Account details

We use your submitted contact details and phone verification result to identify the correct account, support account access and reduce the chance of changing data for the wrong person.

Device signals

Login time, browser or mobile device details and security signals can be recorded when you access the account. These records help us check unusual entry attempts.

Cookies

Cookies may keep a session active, remember selected settings or help us understand which page opened before a support request. You can manage cookie behaviour through your browser.

Wallet records

DANA, OVO, GoPay and QRIS references are used to match payment status with the right account. We do not need you to send a wallet password for a receipt check.

Retention

We keep account, security and transaction records only for operational needs, dispute handling and applicable legal duties. When a record is no longer needed, our process addresses its removal.

Change requests

For a correction, access request or deletion question, contact us through the account support path with a focused description. We verify ownership before acting on private account data.

Privacy Policy Questions Before Account Access

These Privacy Policy answers address the searches we expect before you open an account or connect a wallet. You can check how records are created, how cookies work on mobile, what happens to payment references and how to contact us. If a question concerns eligibility or access, the answer depends on local law and the rules applicable to your location.

It covers account details, phone verification, login and device records, cookies, payment references, retention, security checks and the process for requesting access or corrections to your personal data.

Phone verification helps us connect an account to the correct contact detail and check ownership during support requests. The result can also be part of our account security record.

Yes. We may store transaction references, receipt details and status changes from DANA and QRIS so we can match a payment event to your account and investigate a disputed record.

Cookies may maintain your login session, remember settings and support page functions on a mobile browser. Browser controls let you restrict or remove cookies, although some account functions may change.

Yes. Use the account support path, identify the detail that is wrong and explain the requested correction. We may verify account ownership before changing contact or payment-related records.

We retain payment and account records for the time needed to operate the account, resolve disputes, protect security and meet applicable legal duties. The period can differ by record type.

Account access depends on local law. Where local law permits, we use the account steps and security checks described here; contact support if a login or verification record needs review.