Reference

Open the jak99 Privacy Policy

The jak99 Privacy Policy explains how we handle your account details, device signals and payment records when you use our lobby.

Account dataWallet recordsDevice controlsContact steps
jak99 Open the jak99 Privacy Policy
CONTACT ROUTES

Choose a Privacy Policy contact path

A clear contact route helps you ask about the Privacy Policy without sending sensitive details through an unsuitable channel. Start from the support link in your account area and describe the record, device or wallet event you want us to check. Include the relevant account identifier and payment reference, but never send your password or full wallet credentials. The current support hours and available contact route are shown beside that link, so you can use the channel available for your Indonesia account.

Team online

Account request

Use the account support path when you want to ask what personal details we hold, correct a phone number, or clarify the reason for a verification record. We will use the account details you provide to locate the request and may ask for an account step before discussing protected data.

Wallet record

For a DANA, OVO, GoPay or QRIS receipt question, send the transaction reference shown in your cashier history. We can compare that reference with the account record and explain what data was used to confirm wallet status, without asking you to share a password or wallet PIN.

Device concern

If a new phone, browser or login alert looks unfamiliar, contact us from the account support route and mention the access time and device type. We can review the security event, guide the next account step and record your concern under the Privacy Policy process.

DATA PRACTICE

Explore how we handle your records

The Privacy Policy is supported by practical controls around account entry, wallet checks and device activity.

Account details

We receive details you enter during account creation and phone verification, then use them to provide account access and respond to account requests. If a detail changes, ask us through the support route rather than opening a second account, so the correction stays linked to the right record.

Wallet activity

Payment records can include a rail name, reference, amount status and time connected with DANA, OVO, GoPay, QRIS, bank transfer or a virtual account. We use these fields to match receipts and status checks; wallet passwords and PINs are not needed for this policy request.

Cookies and signals

Cookies and device signals may remember session choices, identify a browser and help us investigate repeated access attempts. Your browser settings can control some cookies, although changing them may affect login continuity or the way a QRIS payment page returns to your account.

Account security

Phone verification is part of the account access step, and security records can show a login time, browser type or device change. Keep your password private and contact support if the account opens from a device you do not recognise, so we can assess the event.

Retention period

We keep personal and transaction records only for as long as needed for account operation, security checks, dispute handling or a legal request. The exact period can depend on the record type. Ask support to explain the retention basis for a particular account or wallet reference.

Change requests

You can ask us to correct, access or clarify personal data through the account support route. Describe the requested change and provide the account identifier. We may verify that you control the account before disclosing or changing protected details, which helps prevent another person from making the request.

Find answers about Privacy Policy

These Privacy Policy questions reflect the account and wallet situations you are most likely to search for before using jak99. Each answer stays focused on personal data, access records and the route for asking us to check or change information. Where access is discussed, it depends on local law.

It covers details you submit for an account, phone verification records, device and browser signals, cookies, security events and transaction references. It also explains how we use those records for account access, DANA, OVO, GoPay or QRIS status checks, support requests and required retention.

Phone verification helps connect an account request with the person seeking access and helps us investigate unusual login activity. We may use the verification record when handling a correction or data request. Keep your phone details current and contact support if the number is no longer yours.

We may keep the payment rail, transaction reference, time and status linked to your account when you use DANA, OVO, GoPay, QRIS, bank transfer or a virtual account. These details help match a receipt or explain a pending status; we do not need your wallet PIN.

Yes. Use the account support route and state which detail is inaccurate, such as a phone number or account label. Include the relevant account identifier, then complete any control check we request. We will assess the correction under the Privacy Policy and explain if a record must remain.

Send an access request through the support link shown inside your account area. Tell us which category you want checked, such as login records, device signals or wallet references. We may confirm account control before sharing protected data, and the available route depends on local law.

Retention depends on the type of record and why we need it. Account, security and payment references may remain for account operation, dispute handling, fraud checks or a legal request. Ask support about a specific record, and we will explain the applicable basis and any available request.

You can manage some cookies through your browser settings. Cookies may support session continuity, device recognition and a return from a QRIS payment page, so blocking them can affect login or account navigation. Contact support if you want help understanding a cookie-related setting or signal.