Reference

totonavi Privacy Policy For Your Account

Our Privacy Policy shows how we collect, use, protect and retain details connected with your totonavi account, including login records, device signals and wallet activity.

Clear data purposesWallet activity contextPhone verification detailsIndonesia access wording

Explore Our Lobby Read FAQ

Know How Wallet Data Is Used

totonavi Service availability depends on jurisdiction. Users are responsible for checking local law before access.

This Privacy Policy applies to personal details we receive when you create an account, verify your phone, sign in, contact support, or request a wallet transaction. We use those details to provide account access, check payment status, investigate unusual activity, and respond to requests about your

1
records. Payment references may show the rail selected, such as DANA, OVO, GoPay, QRIS, bank transfer or virtual account, without giving us access to unrelated wallet content. We may also record device type, browser events, session times and pages opened so we can protect login activity
2
and diagnose account errors. Where access or eligibility is discussed, it depends on local law. We keep this policy available so you can check the current wording before opening an account or connecting a local wallet.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

POLICY SUPPORT

Get Policy Help Near Account Access

A clear support path helps when you need to ask about a record, wallet reference or phone verification entry.

Account data request Ask us which personal details are connected with your account and why they are used. Include your account identifier through the available support route, rather than sending a wallet PIN.

Wallet record question For DANA, OVO, GoPay or QRIS references, share the transaction date and displayed status. We can check the recorded payment reference while keeping your wallet password and private balance details out of the request.

Access concern If phone verification or a mobile login creates a privacy concern, tell us the device path and account step involved. We use that context to locate the relevant security record.

DATA PRACTICE

Keep Your Login And Cookies Clear

Our handling approach separates account access needs from payment references and basic device signals.

Account data

We may handle your contact details, phone verification result, login events and account actions to provide access and respond to account requests. We do not need unrelated wallet content to manage your totonavi profile.

Cookies and sessions

Cookies and similar session signals can remember sign-in state, protect the account path and help us understand technical errors. Your mobile browser may create a new session when stored data is cleared.

Payment references

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account entry can be retained as a transaction reference. We use the record to match status, not to request your wallet PIN.

Account security

Phone verification, login timing, device type and unusual session signals can support account protection. If a check appears before access, it helps us compare the request with your existing account record.

Retention approach

We retain personal details only for the period needed for the stated account, security, payment-record or support purpose, plus any period required where local law permits or requires retention.

Change request

To ask for correction, access or deletion of eligible details, contact us through the account support path with the specific record involved. We may verify account ownership before changing private data.

Find Privacy Policy Answers Quickly

These Privacy Policy questions address the account steps you are most likely to check before using the Indonesia lobby. We keep each answer tied to actual records, including phone verification, mobile sessions and local wallet references, while access depends on local law.

It covers personal details linked to your account, phone verification, login sessions, device signals, cookies, support requests and payment references connected with DANA, OVO, GoPay, QRIS or bank transfer.

Phone verification helps connect an account request with the correct account record and supports login security. We may retain the verification result and related access event, rather than unrelated phone content.

Yes. The Privacy Policy includes mobile browser sessions, cookie signals, device type and account actions taken from your phone. Clearing browser data may end a session and require another account check.

We may store a payment reference, selected rail, date and displayed status so support can match an account transaction. We do not need your DANA or QRIS PIN to handle that record.

You can ask about access or correction through the account support path. Tell us which record you mean, such as a phone entry or login event, and we may verify account ownership first.

Retention depends on the purpose, such as account access, security, payment matching or support, and on applicable local requirements. The Privacy Policy does not promise one fixed period for every record.

Access and eligibility depends on local law. If you can open the account path, complete required verification and reach the available lobby, the Privacy Policy applies to the related account activity.

totonavi Privacy Policy For Your Account

Get Policy Help Near Account Access

Keep Your Login And Cookies Clear

Account data

Cookies and sessions

Payment references

Account security

Retention approach

Change request

Find Privacy Policy Answers Quickly

01 What does the totonavi Privacy Policy cover?

02 Why does totonavi ask for phone verification?

03 Does the Privacy Policy cover mobile browser access?

04 How are DANA and QRIS details handled?

05 Can I request a copy or correction of my data?

06 How long does totonavi keep account records?

07 Can I use totonavi from Indonesia under this policy?

Related Pages