Reference

krutoto Privacy Policy for Your Account

krutoto Privacy Policy explains what we collect when you create an account, verify your phone, sign in on mobile, or use DANA, OVO, GoPay and QRIS.

Account recordsDevice choicesWallet activityPrivacy requests
krutoto krutoto Privacy Policy for Your Account
REQUEST ROUTES

Privacy Help Beside Your Account

A clear contact route matters when a privacy question appears during account access or a wallet check.

Account access Tell us which sign-in or phone-verification step concerns you.
Wallet status For DANA, OVO, GoPay, QRIS or bank-transfer questions, include the payment reference and date.
Privacy request Ask for access, correction or removal through the support route linked to your account.
HANDLING DETAILS

Cookies, Devices, and Account Security

Privacy choices work best when the policy matches the way you actually use the service. We separate account identity, device signals, cookie settings and wallet references so a phone change or browser…

Data we collect

We may handle your account name, phone verification result, sign-in events, device or browser details, and payment references. We collect these details for account access, security checks and payment-status questions.

Cookie choices

Cookies and similar browser storage can remember session settings and help us identify unusual sign-ins. You can adjust browser controls, although changing them may require another account sign-in.

Device behaviour

A mobile browser can create a new session after its storage is cleared, while desktop access may retain separate session signals. We use these signals to review account security, not to read unrelated device content.

Account protection

Phone verification helps connect a privacy request to the correct account. Never send a wallet PIN or full banking credential; our checks should rely on account details and payment references instead.

Retention period

We keep account, security and transaction records for the period needed to operate services, resolve disputes or meet legal duties. When a record is no longer needed, we remove or anonymise it.

Change requests

You can ask what personal data we hold, request a correction, or ask about removal through support. We may limit a request where retaining a record is required by local law.

Privacy Policy Answers for krutoto

These Privacy Policy answers focus on the questions that arise before account access, after phone verification, or while checking a wallet record. They also explain how to contact us about stored data. If your question concerns a specific transaction, use the reference shown for DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

It covers account details, phone verification, device and browser signals, cookies, sign-in events, payment references and support requests connected with krutoto account services where local law permits.

We use phone verification to connect account access and privacy requests to the correct profile. It helps prevent one person from receiving another person’s account details during a support exchange.

Yes. The Privacy Policy covers references and status details connected with DANA, QRIS, OVO, GoPay, bank transfer and virtual account activity, while wallet credentials remain outside our requested support details.

Use the account support path and ask for a personal-data access request. Include your account identifier and the relevant sign-in step; we confirm ownership before describing or providing private records.

You can ask us to correct inaccurate account or contact details through support. We may request phone verification or another account check, and some transaction records cannot be altered when retention is legally required.

Retention depends on the purpose: security events, account records and payment references remain while needed for operation, dispute handling or legal duties, then we remove or anonymise them.

The same Privacy Policy applies, but a mobile browser may create fresh session data after cookies or storage are cleared. We handle those device signals for session security and account checks.