Reference

kudamas11 Privacy Policy And Your Account

The kudamas11 Privacy Policy explains how we handle the details you provide when opening an account, signing in, using DANA or QRIS, and contacting support.

Account detailsWallet recordsCookie choicesAccess requests
kudamas11 kudamas11 Privacy Policy And Your Account
PRIVACY CONTACTS

Get Help With A Privacy Request

A clear contact path helps when your account details or wallet record needs attention. Contact our support team through the support route shown on the kudamas11 site and include the account detail connected to your request, without sending a full password or wallet PIN. We can explain a data entry, help you locate a privacy choice and direct a correction request to the right account process. If your question concerns DANA, OVO, GoPay or QRIS, include the transaction reference so we can check the status without asking for unnecessary data.

Team online

Account access

If you cannot sign in, contact support through the site path and describe the device step where access stops. We may ask for a limited account check before discussing private account details.

Wallet record

For a DANA, OVO, GoPay or QRIS record, send the reference and date through the support path. We use those details to locate the entry while keeping your wallet credentials private.

Data request

Ask us to correct, access or clarify personal data through support. We will confirm the account owner before making a change, and access depends on local law and the request type.

DATA HANDLING

What We Do With Your Privacy Choices

Privacy controls work best when they match real account activity. We separate sign-in protection from lobby preferences, record wallet references rather than wallet PINs, and use cookie settings…

Account security

We use sign-in activity and account verification details to identify unusual access.

Wallet details

A payment record can include a rail name, reference and status for DANA, OVO, GoPay, QRIS, bank transfer or virtual…

Cookies

Cookies can remember a session, language choice or security setting on your browser.

Mobile sessions

When you move from phone login to the lobby, we may record device and session signals for security and fault…

Retention

We keep personal and transaction records for the period needed for account operation, security checks or legal duties.

Policy changes

If this Privacy Policy changes in a way that affects your choices, we will place the updated wording on the…

Privacy Policy Answers For kudamas11

These Privacy Policy answers address the account questions you are most likely to ask before opening access or checking a wallet record. We keep the answers practical: what we collect, why we use it, how cookies behave and how you can ask for a copy or correction. For any request involving account ownership, we may need a verification step before releasing or changing data. Access remains subject to local law.

It covers account details, phone verification, sign-in activity, device signals, cookie choices, support messages and payment references. It explains why we use each category, how long we retain it and how you can request access or correction where local law permits.

We use phone verification to confirm account access and reduce the risk of someone entering with another person’s details. The check is tied to the account step, not to a request for your password or wallet PIN, and depends on local law.

Yes. The Privacy Policy covers references and status linked to DANA and QRIS, as well as OVO, GoPay, bank transfer and virtual account activity. We use those records to match an account action and investigate a stalled wallet status.

A mobile session may create records such as device type, browser details, session time and security events. We use them to keep sign-in working, investigate unusual access and diagnose a transition from phone login to the lobby without collecting your wallet PIN.

Use the support path on the kudamas11 site and state whether you want access, correction or clarification. Include the relevant account detail, but do not send your password. We confirm account ownership first, then handle the request where local law permits.

We retain data while it serves account operation, security checks, transaction matching or a legal duty. After that purpose ends, we remove or anonymise it through our retention process. The exact period can depend on the record type and local law.

Yes. Contact support with the browser or device you used and ask which cookie choice you want clarified. Browser controls can remove optional cookies, while removing necessary cookies may interrupt sign-in, phone verification or an active account session.