Reference

Privacy Policy for Your kiototo Account

kiototo Privacy Policy explains what we collect when you create an account, sign in from a phone, or check DANA, OVO, GoPay and QRIS payment status.

Account clarityWallet dataDevice controlsPolicy access
kiototo Privacy Policy for Your kiototo Account
CONTACT YOUR WAY

Where To Ask About Your Privacy Policy

A clear support path helps you act on the Privacy Policy without searching through unrelated pages. Start from the support link in your account area, especially when a wallet reference, login record or device entry needs clarification. Include the phone number on the account, the relevant date and the payment reference, but never send a wallet password or full security code. We can then locate the right record and explain the next step for your request.

Team online

Account request

Use the support path beside your account controls to ask what personal data is held, why it is used, or how to request a correction. We may ask you to complete the account verification step before discussing private records.

Wallet receipt

For DANA, OVO, GoPay, QRIS, bank transfer or virtual account questions, send the payment reference and date through account support. We use those details to check status without asking for your wallet password.

Device access

If a phone or browser entry looks unfamiliar, tell us through the account support path and change your account password. We can help review the sign-in record while keeping your security code private.

RECORDS AND CONTROL

How We Protect Account Records

Privacy at kiototo is handled through practical account controls rather than vague promises. We separate identity checks, wallet references and device signals so a support request can be matched to the correct…

Account data

We may store your phone number, verification result and account activity needed to provide access and resolve disputes. We do not ask you to place wallet passwords in support messages or ordinary account forms.

Payment references

DANA, OVO, GoPay and QRIS records are handled as payment references and status signals. Bank transfer and virtual account details help us match a receipt, rather than giving us access to your banking credentials.

Cookies

Cookies and similar device storage can keep a session open, remember security choices and help us detect unusual sign-ins. You can manage browser storage, though removing it may require another account verification step.

Account security

We use sign-in checks, phone verification and device signals to reduce unauthorised account access. If you change phones, review the account session and update your password before returning to the lobby.

Retention period

We keep personal and payment records for the period needed for account operation, dispute handling, security checks and legal duties. When a record no longer serves one of those purposes, we remove or anonymise it.

Your request

You can ask us to access, correct or explain personal data through the account support path. We verify the request first, then confirm what can be changed and whether a legal or security reason requires a record to remain.

Privacy Policy Questions About kiototo

These Privacy Policy answers address the account and wallet questions you are most likely to have before opening an account. We keep the wording practical: what we collect, how you request access, what happens on a new device and how payment references are handled. If your question is not listed, use the account support path and include only the details needed to locate your record.

It covers account details, phone verification, device signals, cookies, payment references and support requests connected with your account. It also explains retention, security checks and how to ask for access or correction. Account availability depends on local law.

Yes. The Privacy Policy explains how we use DANA and QRIS status, references and dates to match an account action. The same approach applies to OVO, GoPay, bank transfer and virtual account records, without requesting your wallet password.

Open the support path in your account area and ask for a data access request. Include the account phone number and the reason for your request. We first verify ownership, then explain which records can be provided and in what form.

You can ask us to correct inaccurate account details through account support. We may request phone verification or another ownership check before making a change. Payment references may remain unchanged when they are needed for reconciliation, security or dispute records.

A new phone or browser can create a device signal and may trigger an account verification step. We use that signal to protect access, not to request your wallet password. If the device is unfamiliar, contact support and change your password.

We retain records while they support account access, payment matching, security checks, dispute handling or legal duties. After that need ends, we remove or anonymise them where practical. A support request can ask why a particular record is still retained.

Use the account support path for questions about cookies, device entries, phone verification or sign-in security. Tell us the device type and approximate sign-in date, but leave out passwords and security codes. We will explain the relevant control or next step.