Reference

kuda jitu Privacy Policy For Your Account

The kuda jitu Privacy Policy explains how we handle your account details, wallet records, device signals, and support messages.

Account clarityWallet recordsMobile privacy
kuda jitu kuda jitu Privacy Policy For Your Account
PRIVACY HELP PATH

Where To Ask About Your Personal Data

A clear contact route matters when a privacy question is tied to a login or wallet record.

Account menu Start from the support link inside your signed-in account. Include your account phone number and the subject of the Privacy Policy request so we can identify the correct record.
Wallet status If a DANA, OVO, GoPay, or QRIS reference appears incorrect, send the payment date and reference shown to you. We use those details to trace the related account data.
Policy request For access, correction, or deletion questions, state which request you are making. We may ask for an account step or verification detail before releasing or changing personal data.
HANDLING YOUR DATA

Mobile Cookies, Security, And Retention

Privacy controls should be understandable whether you open kuda jitu in a mobile browser or on desktop.

Account data

We handle your phone number, verification state, account activity, and support messages to provide access and answer requests. We do not treat unrelated personal details as required account data.

Cookie choices

Cookies can remember a signed-in session, language setting, or security signal on your device. Your browser controls can clear them, though clearing login cookies may require another account sign-in.

Security checks

Before we discuss sensitive account data or change a phone-linked record, we may compare your signed-in session with verification details. This helps prevent an unauthorised privacy request.

Payment records

DANA, OVO, GoPay, QRIS, bank transfer, and virtual account references help us reconcile account activity. We retain the minimum transaction context needed for checks and applicable duties.

Retention period

We keep personal data only while it supports account service, security checks, dispute handling, or a legal duty. The Privacy Policy explains when records can be removed or placed beyond active use.

Change requests

You can ask us to access, correct, or delete eligible data through the account support route. Tell us the record concerned, and we will assess the request under local law.

Privacy Policy Answers For Indonesian Accounts

These Privacy Policy answers focus on the questions you may have before opening an account or checking an existing record. They cover mobile access, local wallets, cookies, retention, and requests made through the account support path. If a situation is not covered here, use the policy link and support route shown in your account.

It covers account details, phone verification, device and cookie signals, payment references, support messages, retention, and requests to access or correct data. It also explains when deletion may be available.

DANA and QRIS references help us connect a payment status with the correct account. We use the reference, date, and related account details to reconcile records or answer a wallet question.

Our Privacy Policy covers browser type, device signals, login time, and cookies used for session and security functions. You can clear cookies through browser settings, but login may be required again.

Open the support link from your signed-in account menu and request access to your personal data. Include the account phone number and request details; verification may be needed before release.

Yes, send a correction request through the account support route and identify the phone or wallet record concerned. We may compare verification details before making a change where local law permits.

We retain data while it is needed for account access, security, payment reconciliation, support handling, or a legal duty. The Privacy Policy sets out how records leave active use afterward.

Yes. Some access, correction, or deletion rights depend on local law. Our Privacy Policy describes the request path, the checks we may perform, and how we respond to an eligible request.