Reference

kudajitu Privacy Policy for Your Account

kudajitu Privacy Policy explains what we collect when you open an account, verify your phone, browse Live Baccarat or use DANA, OVO, GoPay and QRIS.

Account clarityWallet dataCookie choicesPolicy requests
kudajitu kudajitu Privacy Policy for Your Account
CONTACT THE POLICY TEAM

Ask About Privacy Through Your Account

A clear contact route matters when you want to ask what data is held or why a verification step appeared. Send a privacy request through the account support path and include the email or phone number linked to your account, not a wallet password. We use the details you provide to locate the right record, confirm ownership and respond to requests about access, correction, deletion or retention.

Team online

Account privacy request

Use the support route beside your account settings to ask for a copy of personal data or clarification about a phone verification record. We may confirm account ownership before responding.

Wallet status question

If a DANA, OVO, GoPay or QRIS reference looks unfamiliar, send the payment receipt and transaction reference through support. Remove wallet passwords and unrelated personal details before sending.

Security concern

For a suspected sign-in issue, contact support from the affected account path and change your password first. We use device and session details to investigate unusual access without requesting your wallet credentials.

HOW WE HANDLE DATA

Browse the Privacy Controls Behind Your Login

Privacy choices work best when each account step has a clear purpose. We separate sign-in protection, payment references, cookie settings and support records so a request can be directed to the relevant…

Account details

We use your phone number and account credentials to create access, complete phone verification and help recover a sign-in. Keep these details current so a privacy request can be matched to your account.

Payment references

For DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity, we retain references needed to match status, receipt checks and disputes. We do not need your wallet password for these checks.

Cookies and sessions

Cookies can keep your session active, remember settings and help detect abnormal sign-ins. Clearing browser cookies may sign you out or remove saved preferences, but it does not automatically erase account records.

Device security

Your phone or desktop browser may provide device, session and network signals used to protect the account. These signals help us examine unfamiliar access around login, verification and wallet activity.

Retention periods

We keep records only as long as needed for account security, payment disputes, support handling or legal duties. A deletion request may not remove records that must remain for those purposes.

Change requests

Where local law permits, request correction, access or deletion through support using your linked phone or email. We may ask for an account step to confirm identity before changing personal data.

Find Answers About Privacy Policy

These Privacy Policy answers focus on the searches we hear before account access: what we collect, how wallet references work, what cookies do and how to request a change. If your question concerns a particular phone verification or payment receipt, include that detail through the account support route.

The Privacy Policy covers account creation, phone verification, device and session signals, cookies, support records, payment references and requests to access, correct or delete personal data.

It describes contact details, sign-in records, verification data, device signals, cookie activity and payment references. We use these details for account access, security, status checks and support handling.

No. We use transaction references, receipts and status details for DANA, OVO, GoPay or QRIS checks. Do not send a wallet password through support or include it in a request.

Use the account support path and provide the phone number or email linked to your account. We may confirm ownership before sending a copy or explaining the records connected with you.

Where local law permits, you can request correction or deletion through support. Some security, dispute or legally required records may need to remain after a deletion request.

Cookies can maintain a browser session, remember settings and help identify unusual sign-ins. Clearing them may sign you out or remove preferences, while account records remain managed under the Privacy Policy.

Account access and certain data requests depend on local law. We explain the available route for your account and may limit a request where security, dispute handling or legal duties require retention.