Reference

kiratoto Privacy Policy For Indonesian Accounts

The kiratoto Privacy Policy explains how we handle your account, phone verification, device details and wallet references when you access our service.

Clear data purposesWallet record contextPhone verification detailsRequest path included
kiratoto kiratoto Privacy Policy For Indonesian Accounts
PRIVACY HELP PATH

Get Policy Help Beside Your Cashier

A clear contact route matters when a privacy request meets a login or wallet question.

Account access Ask through the account help path when phone verification blocks access.
Wallet status For DANA, OVO, GoPay or QRIS questions, include the payment reference and status shown…
Data request Request a copy, correction or removal assessment through our privacy contact route.
DATA CONTROL PRACTICES

Account Security Alongside Wallet Records

We handle this policy area through identifiable account steps rather than vague promises.

Data we receive

We may receive your phone number, verification result, device or browser markers, login events and payment references.

Cookie choices

Cookies and similar browser storage can remember session settings and help keep an account session working.

Account protection

Phone verification is checked before account access, and we may compare device or login signals when a request looks unusual.

Payment matching

A wallet or bank reference is used to match the cashier event you ask about.

Retention choices

We retain records for the period needed to operate the account, resolve payment questions and meet applicable legal duties.

Request changes

To correct account data or ask what we hold, contact the privacy route from your account help area.

Privacy Policy Answers For Your Account

These Privacy Policy answers focus on the records you are most likely to ask about before opening or using an Indonesian account. They cover phone checks, mobile access, cookies, local wallets, retention and the request path, so you can act without guessing which detail to send.

It covers account details, phone verification, device and browser markers, cookies, login events and payment references linked with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

We use your phone number for account identification and the verification step before access. It also helps us confirm ownership when you ask to see, correct or remove account data.

Yes. The policy covers device, browser and session details created when you use the mobile path or desktop access. These markers help investigate unusual logins and keep the right account session connected.

We use the visible transaction reference, status and timestamp to match a cashier event and answer receipt questions. We do not ask for your DANA, OVO, GoPay or QRIS wallet password.

Yes. Use the privacy contact route in your account help area and identify the record that needs correction. We confirm account ownership through the registered phone before discussing or changing it.

We keep records for the time needed to operate access, resolve payment questions and meet applicable legal duties. A removal request is assessed against those purposes and where local law permits.

Start from the account help path and select the privacy request route. Include your account phone and, when relevant, a payment reference; never include your password or a wallet security code.