Reference

kartutoto Privacy Policy For Your Account

kartutoto Privacy Policy explains how we handle the account details, DANA and QRIS status, device signals and cookie choices connected with your access.

Account dataWallet statusDevice accessCookie choices
kartutoto kartutoto Privacy Policy For Your Account
HELP WITH REQUESTS

Account Help For Privacy Requests

A clear support route helps when you want to ask about the Privacy Policy, correct an account detail or check how a wallet reference is connected to your record.

Policy questions Send your Privacy Policy question through account help and state the exact data point you want explained, such as a cookie, device event or phone verification record.
Correction requests Ask us to correct an account detail by identifying the linked phone or email. We may verify account access before changing personal data or confirming its stored value.
Wallet references For DANA, OVO, GoPay or QRIS receipt questions, provide the reference shown in your account. We use it to check status without requesting your wallet password.
SIX DATA CONTROLS

Six Controls For Account Data

We keep privacy work practical: account access is checked before a personal-data request is completed, and operational records are separated from details that are not needed for the request.

Data handling

We use account, device and transaction references for stated access, security and support purposes. We do not ask for a DANA, OVO, GoPay or QRIS wallet password.

Cookies

Cookies can remember account-flow settings and help us understand a failed login path. Your browser controls whether cookies remain, while some account functions may need them.

Account security

Phone verification before account access helps connect a request to the right account. Sign-in and device events can be retained to investigate unusual access.

Retention

We retain records for the period needed for the stated purpose, account support, security checks or applicable legal duties. You can ask which retention reason applies.

Change requests

You can request correction of inaccurate personal details or ask how a record is used. We may confirm your linked phone or email before making a change.

Request contact

Use the account help path for privacy questions, access requests and deletion enquiries. Include a specific record or event so our support team can respond accurately.

Privacy Policy Questions For Your Account

These Privacy Policy answers focus on the account actions you are most likely to search for before opening access. They explain what we collect, why wallet and device records appear, how to request changes and what to include when contacting account help. Where local law permits, the same request path applies on mobile and desktop.

It covers account details, phone verification, login events, device signals, cookies, support messages and payment references linked to DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

Phone verification connects account access and privacy requests to the correct record. It helps reduce mistaken disclosures when you ask about a login event, device record or wallet reference.

Yes. We may handle payment references and status details needed to match DANA or QRIS activity with your account. We do not need your wallet password to check a receipt.

Use the account help path, identify the linked phone or email and name the detail to correct. We may verify account access before changing or confirming personal data.

Cookies can retain account-flow settings, while device and browser records can help investigate access events. Your browser manages cookie storage, and the policy states the related purpose and retention.

Retention depends on the record's purpose, support needs, security checks and applicable legal duties. Ask account help which reason applies to a particular login, payment or verification record.

Yes, where local law permits. Contact account help with your linked phone or email and describe the requested data. We may verify access before disclosing account-specific details.