Reference

katakwin Privacy Policy For Indonesia Wallet Access

Your katakwin Privacy Policy explains how we handle account details, phone verification, device signals and wallet records connected with DANA, OVO, GoPay and QRIS.

Account dataWallet recordsCookie choicesRequest support
katakwin katakwin Privacy Policy For Indonesia Wallet Access
PRIVACY HELP PATH

Find Privacy Policy Help Near Wallet Support

A clear contact path helps when you want to ask what data we hold or why a wallet record appears in your account. Start from the support link after signing in, include the phone number linked to your account, and describe whether your question concerns DANA, QRIS, a browser session or a verification step. We use those details to locate the correct record without asking you to send a password.

Team online

Account support link

Use the support link inside your signed-in account for a Privacy Policy question. Include your registered phone number and request type so we can match the inquiry to the correct account record.

Wallet record query

For DANA, OVO, GoPay or QRIS questions, mention the payment rail and reference shown in your account. We can then check the relevant wallet record without requesting your secret sign-in details.

Browser access query

If a privacy request begins on an Android or iPhone browser, tell us the device path and sign-in time. This helps us separate your account session from an unfamiliar access attempt.

DATA HANDLING PRACTICE

What Our Privacy Process Does With Your Data

We connect each privacy process to a specific account action rather than treating all records alike.

Account data

We use your account details to create and maintain access, confirm the phone verification step and respond to requests tied to the correct account. We do not need your password for a privacy question.

Cookie controls

Cookies can preserve a necessary sign-in session and selected site settings on your browser. You can manage browser cookie controls, although removing necessary cookies may interrupt the privacy request path.

Wallet references

A DANA, OVO, GoPay or QRIS reference helps us connect a payment status to the right account. We use the reference for checking and reconciliation, not as a substitute for your private credentials.

Account security

Phone verification, sign-in activity and device signals support checks for unusual access. If a session looks unfamiliar, contact us through the account support link and avoid sharing passwords or one-time codes.

Retention choices

We keep personal and transaction records only as needed for account operation, security checks, dispute handling and applicable legal duties. You can ask us to explain the category and reason for retained records.

Change requests

To request correction, access or another permitted change, use the signed-in support path and identify the account phone number. We may ask for verification before changing records connected with your account.

Privacy Policy Answers For katakwin Accounts

These Privacy Policy answers address the account, wallet and device questions we hear most often from Indonesian customers. Each response points you toward the same practical route: sign in, open support, identify the relevant record and send only the details needed to handle your request. Where access is discussed, it depends on local law.

It covers account details, phone verification, sign-in activity, device signals, cookies, support messages and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account use.

Sign in to your account, open the support link and ask for a copy or explanation of your records. Include the account phone number and the specific data category so we can locate it.

Yes. The Privacy Policy explains why we may retain a payment rail, reference, status and related account details when checking DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

You can send a correction request through the signed-in support path. State which account detail is wrong and provide the phone number linked to the account; we may verify your identity first.

Cookies can keep a necessary browser session and selected settings available while you move through an account request. Your browser controls can remove them, but some privacy steps may then need repeating.

Retention depends on the record and the reason it is needed, including account security, payment checks, dispute handling and legal duties. Use support to ask which category applies and why it remains.

Account access and eligibility depend on local law and are available where local law permits. The Privacy Policy request route remains the account support link, subject to the checks required for your record.