Reference

inatoto Privacy Policy Explained Clearly

inatoto Privacy Policy shows how we handle your account details, phone verification, DANA and QRIS records, cookies, and support requests in one clear place.

Account dataWallet recordsCookie choicesSecurity steps
inatoto inatoto Privacy Policy Explained Clearly
PRIVACY HELP

Where To Ask About Privacy

A clear support route helps when a privacy request and a wallet receipt meet. Use the account support path linked near your cashier area, describe the request, and include the relevant transaction reference without sending a wallet password. We use the same route for access questions, correction requests, cookie concerns, and account-data queries.

Team online

Account support path

Open the support route from your signed-in account near the cashier area. Tell us whether you need access, correction, deletion, or a privacy explanation, and we will match the request to your account.

Payment receipt check

For DANA, OVO, GoPay, QRIS, bank transfer, or virtual account records, include the payment reference and status shown on your receipt. Never send a wallet password or full security code with your request.

Mobile browser request

If a privacy page behaves differently on your phone, note the device and browser path used before contacting us. This helps us separate a cookie setting from an account access issue without asking for unnecessary data.

ACCOUNT DATA CARE

Security Around Your Account Data

We keep this policy practical by tying each data use to an account action: opening access, confirming a phone, matching a wallet status, or answering a request.

Data we collect

We may handle your account contact details, phone verification result, sign-in events, device signals, payment references, and support messages. Each category supports access, account protection, payment matching, or a specific request you send us.

Cookie handling

Cookies can retain a page setting and help flag unusual sign-in behaviour. On a mobile browser, you can review browser cookie controls, although changing them may affect how your account session or policy pages appear.

Account security

Phone verification is completed before account access, and sign-in activity may be checked when a device or session looks unusual. Keep your password and wallet credentials private; our support route does not require them.

Payment matching

DANA, OVO, GoPay and QRIS references, plus bank transfer or virtual account status, help us connect a receipt to the correct account. We use the reference and result rather than requesting your wallet password.

Retention approach

We retain account, payment, and support records for the period needed to provide access, resolve disputes, protect the service, or meet legal duties. The applicable period can depend on the record and local law.

Change requests

Ask us to correct account data or discuss removal through the signed-in support path. Include the account contact detail that lets us verify the request, and we will explain any limit required by local law.

Privacy Policy Questions Answered

These answers focus on the Privacy Policy questions you may have before opening an account or sending a payment. We keep the route specific so you know what to provide, what we use, and when local law affects a request.

It covers account details, phone verification, sign-in and device signals, cookies, payment references, support messages, retention, and requests to access, correct, or remove data where local law permits.

Phone verification helps confirm account access and protect a session from unusual sign-in activity. We record the verification result for that purpose, rather than asking you to share wallet credentials.

Yes. We may keep the DANA or QRIS transaction reference and status needed to match a receipt, answer a payment query, and protect the account. The same approach applies to OVO and GoPay.

You can ask through the signed-in account support path. State that your request concerns the Privacy Policy, provide the account contact detail needed for verification, and we will explain the available response and any legal limit.

Send a correction request through account support and identify the exact detail that needs updating. We may verify your account first, then explain the change process or any restriction that depends on local law.

We keep payment references and status for the period needed to match transactions, handle receipt questions, protect accounts, resolve disputes, or meet legal duties. The period can vary by record and local law.

Yes. The policy applies when you access account pages from a phone or desktop browser. Cookie settings and device signals may affect a session, so include your device path when reporting a privacy issue.