Reference

infitoto Privacy Policy for Your Account

The infitoto Privacy Policy explains how we collect, use and protect details connected with your account, device and wallet activity.

Clear data purposesWallet record detailsAccount access controlsRequest changes
infitoto infitoto Privacy Policy for Your Account
CONTACT PATHS

Privacy Policy Help From Your Account

A clear contact route matters when a privacy question is linked to a login, receipt or wallet status.

Account support path Use the support area after login for a Privacy Policy question about your account record, phone verification or device access. Include the relevant date and account contact detail so we can separate your request from another account.
Wallet record request For DANA, OVO, GoPay or QRIS questions, mention the payment rail and receipt reference rather than sharing a PIN. We can use that reference to check how the wallet event appears in your account records.
Access clarification If you cannot reach the policy page or account area, tell us your device type, browser and country context. We will explain the available path without asking you to post private credentials in a message.
DATA PRACTICE

How infitoto Handles Policy Requests

We treat privacy questions as account matters, not as general lobby enquiries. Our process links a request to the account contact detail, checks whether the request concerns a payment reference or device…

Account data

We may hold your account contact details, phone verification status and selected account settings. These records help us identify the right account when you ask for access or correction under this Privacy Policy.

Payment references

A DANA, OVO, GoPay or QRIS transaction can create a reference, amount and status record linked to your account activity. We use those details to reconcile the event and respond to a specific wallet question.

Cookies

Cookies and similar browser storage can remember session state, language choices and security signals. You can review browser controls on your device, although removing necessary storage may interrupt login or return you to phone verification.

Device security

We may note device type, browser version, approximate access time and unusual login signals. These details help us investigate account access without treating your phone as permission to reveal account records to another person.

Retention

We keep account, payment and security records only for operational, dispute or legal needs connected with the service. When a record is no longer needed for those purposes, we remove it or reduce its link to you.

Policy changes

If we change this Privacy Policy, we will place the updated wording on this page and show the effective date. You should check the page before opening an account or continuing after a material change.

Privacy Policy Answers for infitoto

These Privacy Policy questions cover the account and payment situations we hear about most often. We have kept the answers practical: what to send, what may be recorded and where to start when you need a correction or access request. If your situation involves eligibility, access depends on local law.

It covers account details, phone verification, device and browser signals, cookies, support messages, security events and payment references linked to DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. It also explains retention, requests for changes and how policy updates appear.

Phone verification helps us connect account access with the contact detail you provided and helps protect records from an unrelated person. We record the verification status and related account event; we do not need your phone PIN or full wallet credentials for this step.

Yes. A DANA or QRIS action may create a payment reference, status and related account event. OVO, GoPay, bank transfer and virtual account activity can be handled in the same way. Send only the reference needed for a specific request, never a wallet PIN.

Use the account support path and identify the account contact detail, the field that appears incorrect and the reason for the requested change. We may ask for an account check before changing records, so one person cannot alter another person’s information.

We keep information for as long as it is needed for account operation, payment reconciliation, security checks, disputes or legal duties. After that period, we remove it or reduce its connection to you where practical. The exact period can depend on the record type.

You can request details about the account, device, support or payment records connected with you. Start from the support area, include the account contact detail and describe the record you want checked. We may limit disclosure where another person’s data or legal duties are involved.

Yes. Account access and eligibility depends on local law. Our Privacy Policy still explains how we handle records for a permitted account, but it does not change local requirements. If access is unavailable, contact support without sending passwords, wallet PINs or unrelated identity documents.