Reference

4runner Privacy Policy For Your Account

4runner Privacy Policy explains how we use details connected with your account, including phone verification, DANA or QRIS status, device signals and activity around titles such as Speed…

Clear data purposesCookie choicesAccount request pathIndonesia access wording
4runner 4runner Privacy Policy For Your Account
REQUEST HELP DIRECTLY

Privacy Support Near Your Cashier Path

A clear request route matters when a wallet status or sign-in record looks unfamiliar. Our support path is connected to account help, so you can explain a privacy concern without sending sensitive…

Account access request If you cannot reach your account after phone verification, contact us through the account help path and state that your request concerns the Privacy Policy. We may ask for matching account details before discussing records connected with DANA, OVO or another wallet.
Payment record question For a DANA, QRIS, GoPay, bank transfer or virtual account record, provide the transaction date and visible reference rather than a password. We compare the payment status with the account record and explain what data was used for that check.
Correction or removal When you believe an account detail is wrong or should be removed, send the request through support with the affected field named clearly. We verify ownership, assess legal and security needs, then confirm whether the requested change can be completed.
DATA HANDLING DETAIL

What We Keep Around Your Account

Privacy decisions are easier when the operating steps are visible. We use account details to connect your phone verification with your session, payment records to reconcile wallet or bank activity, and device…

Account identity

We use your phone number and verification result to connect you with the correct account session. If you request a change, we compare the request with existing account details before altering identity data, helping prevent an unrelated person from taking action on your account.

Payment matching

A wallet label such as DANA, OVO or GoPay, along with a QRIS or bank reference, may be used to match a payment status. We use the match for account records and support checks, not as a reason to request your wallet password.

Cookies and sessions

Cookies can keep your session active while you move from login to a lobby page on the same device. They may also support security checks. Clearing cookies can sign you out and remove saved choices, so you may need to verify the account again.

Device security

We may record device and connection signals linked to account access to identify unusual sign-in patterns. A new phone or browser can trigger an additional check. This process helps us protect account records without asking you to disclose your password.

Retention choices

We retain records for as long as their stated purpose, security review or legal requirement calls for. When a request concerns deletion, we check whether a payment, access or fraud record must remain before confirming what can be removed.

Request ownership

To request access, correction or clarification, use the support route tied to your account and describe the specific record. We may confirm your phone details before responding, keeping private account data away from an unverified requester.

Privacy Policy Questions About Your Account

These answers address the searches we hear most often about the 4runner Privacy Policy, from wallet records to cookies and account changes. If your situation involves a particular phone, browser, payment reference or access decision, include that context in your support request. We can then direct you to the relevant policy step.

The 4runner Privacy Policy covers account details, phone verification, payment references, cookies, device signals, site activity, retention and requests for access or correction. It also explains how these categories may support security and payment reconciliation when you use the site where local law permits.

We do not need your DANA, OVO, GoPay or QRIS password for a payment status check. We may use a visible reference, wallet label, amount and date to match the transaction with your account, and support will not ask you to disclose a password.

Phone verification links an account request with the correct account holder and helps protect access when a new device is used. The Privacy Policy describes this as an account-security step, not permission for us to request unrelated contacts or private phone content.

Yes. Send a correction request through the account support path and name the field that appears wrong, such as a phone detail or payment reference. We may verify ownership first, then confirm the change or explain why a record must remain unchanged.

Cookies can preserve a sign-in session and selected settings while you move through the site on a phone or desktop. If you clear them, the account may sign out and ask for phone verification again. Cookie controls do not erase every account record automatically.

The retention period depends on the purpose of the record, security checks and applicable legal requirements. A DANA, QRIS, bank transfer or virtual account reference may need to remain for reconciliation. Ask support about a specific date or record for a clearer response.

You can request access through the account help route and describe the categories you want reviewed, such as verification, cookies or payment status. We may confirm account ownership before responding, and access or eligibility depends on local law.