Reference

Privacy Policy for Your kuda55 Account

Our kuda55 Privacy Policy explains what we collect when you open an account, sign in from a mobile browser, or connect DANA, OVO, GoPay and QRIS.

Account dataWallet recordsCookie choicesYour requests
kuda55 Privacy Policy for Your kuda55 Account
CONTACT ROUTES

Three Ways To Ask About Your Data

A clear contact route helps when you want to question a record, request a correction or understand a cookie choice.

Account help Use the account-help route when you cannot sign in or complete the phone verification step. We may ask for account details already held on your profile, but you should not send a password, one-time code or full payment credential in a message.
Wallet query For a data question linked to DANA, OVO, GoPay or QRIS, include the payment rail and reference shown in your account. This lets us separate a wallet status record from unrelated browser activity before replying to your request.
Policy request Ask through the policy contact route if you want a copy of data linked to your account, a correction, a deletion request or an explanation of retention. We may need to verify account ownership before making a change.
SECURITY PRACTICE

Six Controls Around Your Account Data

Privacy depends on practical account controls, not only a page of legal wording. We separate sign-in records from wallet references, limit internal access to data needed for a support or security task…

Collection

We collect account details, phone verification results, sign-in events, device and browser signals, support messages, and payment references. For a QRIS or wallet query, we use the transaction details needed to identify the affected record rather than requesting unrelated personal data.

Cookies

Cookies and similar browser storage can keep your session, language choice and security state working as you move from login to account pages. You can manage browser permissions, although changing them may interrupt sign-in or remove saved preferences on your device.

Account security

Phone verification is part of the account access path, and sign-in activity can be checked when a security question reaches support. Keep your password and one-time codes private; our support route does not need you to publish them in a request.

Retention

We keep account, payment and support records only for the period needed for the stated service, security checks, dispute handling and legal duties. Retention can differ by record type, so a wallet reference may not follow the same timetable as a cookie.

Your changes

You can ask us to correct inaccurate account details or question a record through the policy contact route. We may confirm your identity first, and some records may need to remain when a legal, security or transaction duty applies.

Third-party handling

Payment providers may process details needed to complete DANA, OVO, GoPay, QRIS, bank transfer or virtual account requests. Their own privacy terms can also apply, while we remain responsible for explaining the account data we hold around that payment event.

Privacy Policy Questions Before Account Access

These Privacy Policy answers focus on the questions you may have before opening a kuda55 account from Indonesia. They cover the phone step, mobile browsing, wallet records, cookies, correction requests and local access wording. Read them with the full policy above, then use the account or policy contact route when your situation needs a direct check.

It covers account details, phone verification, sign-in activity, device and browser signals, cookies, support messages and payment references. It also explains why we use those records, how retention works, and how you can request access, correction or deletion where local law permits.

Yes. The Privacy Policy covers the account-side records created when you request or check a DANA, OVO, GoPay or QRIS payment. These can include a reference, status, amount and time, while the payment provider may apply its own privacy terms.

Phone verification helps connect account access to the correct profile and supports security checks when sign-in activity looks unusual. We record the verification result and related account event, but you should keep the code private and never place it in a support message.

Yes. You can open the Privacy Policy from a mobile browser and manage your account through the same browser session. Device and browser signals may be recorded for security and session continuity; changing cookie permissions can interrupt login or remove saved settings.

Use the policy contact route linked from account help and state whether you want a copy, correction or deletion request. Include the account detail needed to locate your profile, not your password or one-time code. We may verify ownership before responding.

Retention depends on the record and its purpose. Payment and support records may be kept for security, dispute handling and legal duties, while cookie data can follow a different period. The policy contact route can explain the relevant category for your request.

The policy explains our data handling, while account access and eligibility depends on local law. If you are in Indonesia, check the current access wording and contact route before opening an account. We cannot use this page to replace rules that apply in your location.