Reference

Open flokitoto Privacy Policy for Your Account

Your account details, device path and wallet records are explained clearly in the flokitoto Privacy Policy, so you can understand what we collect before opening access to Live…

Clear data purposesWallet activity contextAccount access choicesCookie controls
flokitoto Open flokitoto Privacy Policy for Your Account
CONTACT PATHS

Contact Us About Privacy Policy

A clear contact route helps you raise a privacy question without repeating your whole account history. Start from the account support path when a login detail, phone verification record or wallet status needs attention. Include the relevant payment rail and receipt reference, but never send a password or full security code. We use the details you provide only to locate and answer the policy request.

Team online

Account access

Ask about a phone verification record or login detail through the account support path. We may request account identifiers so we can match your request without asking for your password.

Wallet records

For DANA, OVO, GoPay, QRIS, bank transfer or virtual account questions, share the receipt reference and payment date. We can check the linked record while keeping your security code private.

Policy requests

Use the available contact route to ask what data is held, request a correction or ask how retention applies. We may verify account ownership before discussing personal records.

DATA PRACTICES

See How We Handle Account Data

Privacy work follows the same account steps you see on the site: login, phone verification, wallet selection and a request for help.

Account details

We use the name, contact details and verification data you submit to create and protect your account. These records help us identify the correct account when you ask for a privacy change.

Device activity

Login time, browser details and device signals can help us spot unusual access. We connect these signals to account protection rather than treating them as a public profile.

Cookies

Cookies can remember session choices and help the account path work across pages. Your browser settings may limit them, although some login or preference functions may then need to be repeated.

Payment records

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference lets us trace a payment status. We do not need your wallet password or security code to check that reference.

Retention

We keep personal records for as long as the stated account, security, dispute or legal purpose requires. When a record is no longer needed, our process removes or de-identifies it.

Change requests

You can ask us to correct account data, explain a processing purpose or discuss deletion where applicable. We first confirm account ownership, then assess the request under local law.

Ask About flokitoto Privacy Policy

These answers address the privacy searches we expect before you open an account. They cover account creation, wallet checks, device use, cookies, retention and requests for access or correction. If your situation is different, use the contact path above and include only the details needed to locate your record.

The flokitoto Privacy Policy covers account details, phone verification, device activity, cookies, wallet references and support requests connected with your access, where local law permits.

We use phone verification to connect access with the correct account and reduce mistaken or unauthorised login activity. The Privacy Policy explains its purpose and how long related records may remain.

Yes. The Privacy Policy covers references connected with DANA, OVO, GoPay, QRIS, bank transfer and virtual account steps, including status checks and receipt matching.

You can request a correction through the stated contact route. We may verify account ownership first, then review the request and apply the result where local law permits.

Cookies can keep your session and selected preferences available between pages. Browser controls can restrict them, but the Privacy Policy explains that some login steps may need repeating.

Retention depends on the account, security, payment dispute or legal purpose involved. We remove or de-identify records when that purpose ends, subject to a lawful retention requirement.

Use the account support path and request a copy or explanation of data linked to your account. Provide a receipt reference only when relevant, and never include a password or security code.