Reference

jagoanjitu Privacy Policy for Your Account

Our Privacy Policy explains how jagoanjitu handles account details, phone verification, device signals and wallet references when you use the Indonesia lobby.

Account dataDevice choicesWallet referencesYour requests

Explore Our Lobby Read FAQ

How DANA and QRIS Data Is Used

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

This Privacy Policy covers data collected when you create an account, confirm your phone, sign in, contact support or select a payment route. We may receive the account name, contact details, verification results, device identifiers, approximate connection details and transaction references needed to match a request

1
with your account. For DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity, we use payment status and reference fields rather than storing wallet passwords or card credentials. BCA, BRI, Mandiri and BNI references may appear when a bank route is selected. We use this
2
data to prevent mistaken account actions, investigate status questions and meet applicable requests. Access and eligibility depend on local law; where local law permits, you may ask us to explain, correct or remove eligible data.

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

CONTACT ROUTES

Get Privacy Help Beside Cashier Access

A privacy question should not require you to search through unrelated pages. We provide a direct route from account access and the cashier area so you can identify the relevant login, wallet…

Account access Use the account support route linked near login when you need a copy request, correction request or explanation of data connected with your phone verification.

Wallet status When DANA, OVO, GoPay or QRIS status appears unusual, contact support from the cashier path and include the transaction reference so we can locate the event.

Device concern If a phone or browser appears in your access history unexpectedly, tell us through account support, sign out of active sessions and change your account password.

SECURITY PRACTICE

Account Security Across Mobile Login

We keep this policy practical by connecting each data use to an account action. Mobile access can create device and session records, while phone verification helps us distinguish your sign-in from an…

Data collected

We may handle your contact details, phone verification result, sign-in events, device markers, support messages and payment references needed to operate your account and investigate a reported issue.

Cookie choices

Cookies and similar storage can remember session preferences and help protect account access. You can adjust browser controls, although removing them may affect sign-in continuity or policy request handling.

Phone verification

Before protected account access, we use the phone verification step to connect a request with the correct account. Verification codes should stay private and must not be shared with support.

Wallet records

For QRIS, DANA, OVO, GoPay and bank routes, we keep references such as amount status, route and time so a cashier question can be checked without wallet credentials.

Retention period

Account and support records remain available only as long as needed for service operation, security checks, disputes or applicable legal duties. We remove or de-identify records when those needs end.

Change request

Ask us to access, correct or delete eligible data through account support. Describe the request clearly, and we may verify account ownership before changing or disclosing records.

Privacy Policy Questions About jagoanjitu

These answers address the privacy searches we hear most often before account access. They explain what happens around mobile login, phone verification, cookies, payment references and requests for changes, while local access remains subject to applicable rules.

It covers account details, phone verification, device and session records, cookies, support messages and payment references connected with DANA, OVO, GoPay, QRIS or bank routes.

Phone verification helps us connect protected account actions with the correct account and identify unusual access. We do not ask you to disclose verification codes to support.

No. We use route and transaction references, status and timing to investigate cashier questions. Wallet passwords, PINs and one-time codes should remain with you and your payment provider.

Cookies can preserve a session and selected preferences while helping protect sign-in. Browser controls can limit them, but removing required cookies may interrupt account access or policy request handling.

Yes, where local law permits. Contact account support with a clear access or correction request. We may verify ownership before providing records or changing details linked to your account.

We retain records for operational needs, security checks, disputes or applicable legal duties. When those needs end, we remove or de-identify the relevant data where permitted.

You may submit a deletion request through account support. We assess it under applicable rules, and some records may remain when needed for security, dispute handling or legal duties.

jagoanjitu Privacy Policy for Your Account

Get Privacy Help Beside Cashier Access

Account Security Across Mobile Login

Data collected

Cookie choices

Phone verification

Wallet records

Retention period

Change request

Privacy Policy Questions About jagoanjitu

01 What does the jagoanjitu Privacy Policy cover?

02 Why does jagoanjitu need phone verification?

03 Does the Privacy Policy store my DANA or QRIS password?

04 How do cookies affect my jagoanjitu account?

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

06 How long does jagoanjitu keep account data?

07 Can I ask for deletion under this Privacy Policy?

Related Pages