Reference

Privacy Policy For Your kargoto Account

kargoto Privacy Policy explains what we collect when you open an account, use DANA or QRIS, and move between the lobby and your wallet.

Account clarityWallet recordsCookie choicesSupport access
kargoto Privacy Policy For Your kargoto Account
HELP WITH PRIVACY

Get Clear Answers About Your Records

Questions about our Privacy Policy should have a direct answer, especially when a wallet reference or login event looks unfamiliar.

Account privacy desk Use the signed-in support path for questions about data access, phone verification or a…
Wallet record help If a DANA, OVO, GoPay or QRIS reference appears incorrectly, send the payment date…
Security request route A sign-in alert, changed phone number or unfamiliar device should be reported through the…
DATA HANDLING DETAILS

What We Do With Information You Share

Privacy is part of the account flow, not a separate message shown after a wallet action. We limit collection to details needed for account access, payment matching, security, support and legal duties.

Account creation

We collect the details needed to create and maintain your account, then use the verified phone path to confirm that access belongs to you. If a field is incorrect, contact us through signed-in support so we can assess the correction without exposing the account to another person.

Payment matching

A wallet or bank reference helps us connect a deposit or withdrawal status with the correct account. For DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity, we keep the operational reference needed for reconciliation and support rather than collecting unrelated wallet content.

Cookie controls

We use necessary cookies for sign-in, session continuity and security checks. Your browser can restrict cookies, but doing so may interrupt account access or require another verification step. We explain any optional cookie choice where it appears and do not treat a blocked optional cookie as a payment instruction.

Security checks

We watch for unusual sign-in patterns, device changes and repeated verification failures to protect your account. These checks can pause access while we confirm ownership. If a warning does not match your activity, contact support from the account path and include the time shown on the alert.

Retention periods

We retain account, security and transaction records for as long as they are needed to operate the account, resolve disputes, protect against misuse or meet a legal duty. When a record no longer has a valid purpose, we remove it or separate it from direct account identification.

Change requests

You can ask us to access, correct or clarify personal data held under this Privacy Policy. Send the request through signed-in support, describe the record and provide its date or reference. We verify the requester first, then explain the available action and any legal reason for a restriction.

Privacy Policy Answers For Indonesian Accounts

These Privacy Policy answers cover the account questions we hear most often from people checking kargoto before opening access. They explain the practical records connected with login, cookies, local wallets and support requests. If your situation is different, use the secure contact route and mention the relevant account step or payment reference. Access remains where local law permits.

The kargoto Privacy Policy covers account details, phone verification, sign-in activity, device and security records, cookies, payment references and support requests. It explains why we use each category, how we protect it, how long records may remain and how you can ask for access or correction.

We use your phone number for the account verification step before access and for security checks when sign-in behaviour changes. It also helps support locate the correct account. Send phone details only through the signed-in account route, where local law permits and where we request verification.

Yes. The Privacy Policy covers the transaction references and status details connected with DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity. We use those records to match a wallet action, resolve a receipt question and protect the account, not to read unrelated wallet content.

We use necessary cookies to maintain your signed-in session, support security checks and keep account pages connected while you browse on a phone or desktop. Your browser can restrict optional cookies. Blocking necessary cookies may interrupt access or require another phone verification step.

Use the signed-in support route and ask for data access or correction under the Privacy Policy. State which record concerns you, such as a phone detail, device event or wallet reference. We verify ownership first, then explain the available action and any restriction required by local law.

We keep account, security and payment records while they support account operation, dispute handling, misuse prevention or a legal duty. The period differs by record type and applicable rules. Once the purpose ends, we remove the record or separate it from direct account identification where permitted.

Contact our account privacy desk through the secure support path shown after sign-in. The team is available daily from 09:00 to 23:00 Jakarta time. Include a date, account step or payment reference, but do not place identity documents or wallet credentials in an open message.