Reference

fiftoto Privacy Policy For Your Account

fiftoto Privacy Policy explains what we collect when you open an account, verify your phone and use the lobby from an Indonesian mobile browser.

Account dataWallet recordsCookie choicesPhone verification
fiftoto fiftoto Privacy Policy For Your Account
HELP WITH PRIVACY

Get A Clear Answer About Your Data

A direct support route matters when a Privacy Policy question concerns your own account rather than a general page.

Account help path Open account help from the signed-in mobile browser and describe the Privacy Policy issue in your own words. We use the account contact detail to locate the right record, while you should keep passwords, wallet PINs and one-time codes out of the message.
Wallet status check For DANA, OVO, GoPay or QRIS questions, attach the payment reference and receipt time rather than private wallet credentials. We compare that reference with the account record and explain whether the status is pending, matched or needs another check.
Privacy request Ask support to access, correct or remove personal details through the same account route. We may request a phone verification step before discussing private records, so a third party cannot obtain account data by simply quoting your fiftoto login name.
DATA CONTROL POINTS

What This Policy Lets You Check

The Privacy Policy is written around actions you can take, not broad promises. You can ask which account details we hold, why a cookie appears on your mobile browser, how a phone…

Data we collect

We may collect the details you enter during account creation, your phone verification result, login timestamps, device and browser signals, support conversations and payment references. For a DANA or QRIS receipt, the record helps us connect a transaction status to the correct account without asking you to share a wallet PIN.

Cookie choices

Cookies and similar browser storage can keep an account session active, remember selected settings and help us identify unusual access. On a mobile browser, you can review or clear browser data through its privacy settings; clearing it may sign you out and require phone verification again.

Account security

Phone verification is part of the access path because it helps us distinguish your account from an unauthorised sign-in. We record the verification outcome and relevant security events, but you remain responsible for keeping your password, device and one-time codes away from other people.

Payment records

A wallet or bank record normally includes a reference, amount, timestamp and status rather than your private wallet PIN. We use those fields to reconcile DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity and to answer a receipt question through account support.

Retention choices

We keep personal details only for the period needed for the purpose described in the Privacy Policy, account security, dispute handling or a legal requirement. A request to remove data may not erase transaction or security records that must remain available for those reasons.

Change requests

If your phone number, contact detail or another account field is wrong, contact us through account help and state the exact correction. We may check your identity before changing it, then confirm the outcome through the contact route attached to your account.

Answers Before You Open An Account

These Privacy Policy answers focus on the checks you are most likely to make before opening an account from Indonesia. We keep the route practical: read the policy, use the account help path for a personal request and share only the reference needed for a DANA, OVO, GoPay, QRIS or bank transaction question. Access depends on local law.

The fiftoto Privacy Policy covers account creation details, phone verification, login and device signals, cookies, support messages and payment references. It explains why we use each category, how we protect account access, how long records may remain and how you can ask for access or correction.

Phone verification helps us confirm that the person entering an account is connected to the contact detail supplied during account creation. We record the result and related security event, not your one-time code for support messages. A verification step may also be needed before a private data request.

Yes. The Privacy Policy covers payment references, timestamps, amounts and status information connected with DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity. We use those fields to match a receipt with your account and investigate a cashier status without requesting your wallet PIN.

You can contact account help and identify the field that needs correction, such as a phone number or contact detail. We may request a phone verification step before making a change. After checking the request, we use the contact route attached to your account to explain the result.

Send a removal request through the account help path and specify which personal detail you want us to assess. We first confirm the request belongs to you. Some transaction, security or dispute records may remain when the Privacy Policy or applicable legal needs require continued retention.

Cookies can maintain a browser session, remember settings and help identify unusual access. You can clear them through the privacy controls in your mobile browser or desktop browser, but doing so may sign you out and trigger phone verification when you return to the account.

Use the signed-in account help route and describe the Privacy Policy question without including a password, wallet PIN or one-time code. For a payment concern, add the receipt reference and time. We can then locate the relevant record and explain the next step where local law permits.