Reference

Privacy Policy for Your flokitoto Account

flokitoto’s Privacy Policy explains how we collect, use and protect the account, wallet and device details connected with your access.

Account clarityWallet data careCookie choicesDirect support
flokitoto Privacy Policy for Your flokitoto Account
CONTACT OPTIONS

Three Ways To Ask About Privacy

A clear contact path helps you act on this Privacy Policy without searching through unrelated pages. We keep privacy requests close to the same account route used for login and cashier questions, so a correction or access request can be matched to the right account. Please send enough detail for us to identify your record, but do not include a full wallet password, one-time code or complete payment credential.

Team online

Account support route

Use the support link shown after login to ask about account data, phone verification records or a correction. We may ask you to confirm an account detail before discussing private records, which helps us avoid sharing data with the wrong person.

Cashier status path

If your question concerns DANA, OVO, GoPay, QRIS, bank transfer or virtual account data, include the transaction reference and date through the cashier support path. We use that detail to locate the relevant payment record without requesting your wallet PIN.

Sign-in assistance

When a cookie, device session or phone check blocks access, start from the sign-in help path and describe the device you used. We can separate a security event from a simple browser issue before making any account change.

DATA CONTROL

How flokitoto Handles Personal Data

We handle this policy area through specific account and security steps rather than broad data collection.

Account details

We use the account details you provide to create access, respond to requests and keep the correct profile connected to your sessions. Phone verification is handled as an account-security step, and we do not ask you to send a one-time code through support messages.

Wallet references

Payment records can show a method such as DANA, OVO, GoPay, QRIS, bank transfer or virtual account, plus a reference and status. We use those fields to reconcile an account request and investigate a mismatch, not to collect your wallet password or PIN.

Cookie settings

Cookies can keep a signed-in session working, remember selected settings and help us detect unusual access. Your browser controls whether optional cookies remain active. If you clear necessary session cookies, you may need to sign in and complete the account check again.

Device security

A mobile browser and a desktop browser may create different session and security records. We compare signals such as sign-in time, browser details and failed attempts to protect the account. These checks do not give us access to files, contacts or unrelated apps on your device.

Retention choices

We keep personal records for the period needed to provide account support, resolve payment disputes, protect access or meet a legal requirement. When a record no longer serves one of those purposes, we aim to delete it or reduce its link to your account.

Changes and requests

You can ask for a copy, correction or clarification of personal data connected with your account. Send the request through support after login, include the relevant account detail and explain the change needed. We verify the requester before acting, especially where wallet or phone data is involved.

Privacy Policy Questions From Indonesia

These Privacy Policy answers focus on the account steps you are most likely to meet when using a mobile browser or desktop session from Indonesia. We explain the practical difference between account data, device records and payment references, along with the route for asking us to check or change a record. If your question is not covered, use the support path connected to your account.

The flokitoto Privacy Policy covers account details, phone verification, support messages, wallet references, cookies, device sessions and security events. It explains how we use those records for access, payment matching, account protection and legal needs, including activity connected with DANA, OVO, GoPay and QRIS.

Phone verification helps us connect an account request with the person completing it and reduces mistaken or unauthorised access. We may use the verification result when you sign in or ask for account changes. We will not ask you to disclose a one-time code in a support message.

Yes. The Privacy Policy covers payment references and status details linked to DANA, QRIS, OVO, GoPay, bank transfer and virtual account activity. We use those details to match an account or resolve a status question. We do not need your wallet PIN or full payment credential.

We use necessary cookies to maintain a session, support account access and remember certain settings. Optional cookies may support preference or security functions. You can manage them in your browser. Clearing necessary cookies can sign you out and may require another phone or account check.

You can request access to, clarification of or correction to personal data connected with your account. Use the support route after login and describe the record involved. We verify your identity before responding, and access to a request depends on local law and any applicable legal restrictions.

We retain records for the time needed to provide support, reconcile a payment reference, investigate security activity or meet a legal requirement. Retention can differ by record type. When the purpose ends, we aim to delete the record or reduce its connection to your account.

Yes. Where local law permits, you can ask what personal data we hold, why it is used, whether a correction is possible and how long it is retained. Send the request through account support, identify the relevant account detail and avoid including passwords, PINs or one-time codes.