Reference

Privacy Policy for apk jkt8 Accounts

Our Privacy Policy explains how apk jkt8 handles your account details, phone verification, wallet records and device access before you open the lobby.

Clear data purposesWallet record contextAccount request pathMobile session clarity
apk jkt8 Privacy Policy for apk jkt8 Accounts
CONTACT ROUTES

Ask About Your Privacy Policy

A direct support request gives you a practical way to ask what account data we hold, why a wallet record appears or how to correct a phone number.

Data access request Ask us to identify the account details connected with your sign-in, phone verification and wallet activity. Include your registered contact detail so we can confirm ownership before discussing any record.
Correction request If your phone number or account detail is inaccurate, send a correction through the account support route. We may ask for a verification step before changing information linked with DANA, OVO or another wallet record.
Wallet privacy query For a DANA, QRIS, GoPay or bank transfer reference, tell us which transaction needs clarification and what you see on screen. We use the reference to locate the record without asking for your wallet password.
DATA PRACTICE

How We Handle Your Account Data

Privacy work is tied to the way your account actually operates, from the first phone check to a later request about a transaction record.

Account creation

When you open an account, we collect the details needed to create your profile and start the phone verification step. We use those details for account access and related support, not as a reason to request your wallet password.

Phone verification

The phone check helps us distinguish an account holder from an unapproved sign-in. If a verification attempt fails, support can ask for account identifiers, while sensitive authentication codes remain yours and should not be shared in a message.

Cookie choices

Cookies can keep your sign-in path and selected account settings available between pages. Your browser can clear or restrict them, although some account functions may then require another sign-in or may not display as intended.

Device sessions

A mobile browser session may create technical records such as device type, browser details and access time. We use these signals to help protect the account and investigate unusual access rather than to read unrelated content on your device.

Record retention

We keep account, verification and transaction records for the period needed for account operation, security checks and applicable local requirements. You can ask which record applies to your request and whether removal or restriction is available.

Security contact

If you suspect another person accessed your account, contact support through the account route and change your sign-in details. Do not send a DANA, OVO, GoPay or bank password; we only need enough detail to locate the account.

Privacy Policy Questions About apk jkt8

These answers focus on the questions you may have before opening an account or asking us to change a record. Each response refers to the Privacy Policy rather than the wider lobby, with practical examples covering phone checks, cookies, wallet references, mobile access and requests made where local law permits.

The Privacy Policy explains how we handle account details, phone verification, device session data, cookies, support requests and transaction references. It also describes retention, security handling and the way you can ask about, correct or restrict eligible data connected with your account.

Yes. When you use DANA or QRIS, we may receive a transaction reference and status needed to match the account request. The Privacy Policy explains why that record is used, how it is protected and how you can ask us to locate it.

Use the account support route and ask for a data access request. Include your registered phone detail or another account identifier so we can confirm ownership. We may request a further check before discussing records linked with your sign-in.

Cookies may keep a mobile sign-in path and account settings available between pages. Your browser controls can remove or restrict them. The policy explains that clearing cookies may require another sign-in or affect parts of the account path.

You can ask for a correction through support, explaining which detail is wrong and what it should show. We may verify account ownership before making a change, especially when the detail connects to phone verification or wallet records.

Retention depends on the purpose of the record, such as account operation, security checks or a transaction query, along with applicable local requirements. Ask support which category applies to your data and whether a lawful removal request is available.

Contact us through the support path displayed in your account and state that your question concerns the Privacy Policy. Tell us your region and account identifier. We will explain the applicable route where local law permits without asking for secret wallet credentials.