Reference

KERJITU Privacy Policy, Made Clear

KERJITU Privacy Policy shows what account, device and wallet data we collect, why we use it, and how you can request access or changes.

Account dataWallet recordsDevice controlsYour requests

Explore Our Lobby Read FAQ

How DANA and QRIS Data Is Used

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

When you add DANA, OVO, GoPay or QRIS through our cashier path, we record the payment reference, amount, status and account identifier needed to match the transaction. Bank transfer and virtual account records may carry a bank name such as BCA, BRI, Mandiri or BNI, plus

1
a reference used for reconciliation. We do not ask for wallet credentials inside ordinary support messages. We use these records to confirm deposits, investigate a stalled status and protect your account from unusual access. Data may be shared with payment providers or service partners only when
2
needed for these purposes, legal duties or a requested transaction. Our service and this Privacy Policy apply where local law permits and access depends on local law.

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

CONTACT PATHS

Three Ways to Ask About Your Data

A clear contact route helps you act on this Privacy Policy without sending sensitive wallet credentials into a chat. Use the account support path for identity and login records, the cashier-linked route for payment references, or the policy contact option for access, correction and deletion requests. If you are in Yogyakarta or elsewhere in Indonesia, the same request steps apply where local law permits.

Team online

Account privacy request

From your signed-in account, contact support about profile data, phone verification records or device access. We may ask you to confirm the account step before discussing private records.

Wallet record question

For DANA, OVO, GoPay, QRIS, bank transfer or virtual account data, include the payment reference and date. Never send a wallet PIN or password with your request.

Policy contact route

Use the Privacy Policy contact path when you want a copy, correction or removal request. We assess the request against identity checks, retention duties and local law.

SECURITY PRACTICE

Six Practical Data Handling Commitments

We apply this Privacy Policy to the account journey from phone verification through lobby access, including mobile sessions and wallet status checks.

Collected account data

We may collect your account identifier, phone verification result, login events, device details and support messages. These records help us provide access, detect account misuse and answer a data request.

Cookies on your device

Cookies and similar storage can keep a session active, remember selected settings and help us detect repeated login failures. You can manage browser controls, though some account steps may then require another login.

Account security checks

Before discussing private records or changing account data, we may compare your signed-in session, phone verification and recent account activity. This reduces the chance of a stranger receiving your details.

Payment matching records

For DANA, OVO, GoPay, QRIS and bank rails, we keep references that connect a payment status to your account. We do not need your wallet PIN to check a receipt or transaction state.

Retention and removal

We retain data only for the stated service purpose, account protection, dispute handling or legal duties. When retention is no longer needed, we remove or de-identify records where local law permits.

Changes and requests

You can ask us to access, correct or remove eligible data through the policy contact route. We record the request, verify your identity and explain any limit caused by legal or security requirements.

Privacy Policy Questions Before Account Access

These Privacy Policy answers cover the searches we hear before an account is opened or a wallet is connected. We keep the process specific: you can ask about records, cookies, payment references, phone verification and device sessions. If a request depends on location or eligibility, access depends on local law and we explain the applicable step.

It covers account, phone verification, device, cookie, support and payment-reference data connected with your account. It also explains our purposes, retention approach, security checks and routes for data requests.

We use a DANA, OVO, GoPay or QRIS reference to match a payment with your account, show its status and investigate a failed or delayed record. We do not need your wallet PIN.

Yes. Use the policy contact path and identify the account you control. We verify the request through the signed-in session or phone step, then provide eligible records where local law permits.

Send a correction request through account support or the policy contact route. Tell us which field is wrong, such as a phone detail, and complete the identity check before we change the record.

Yes, cookies or similar storage can maintain a session, remember settings and flag repeated login failures on your phone or browser. Blocking them may require another login during account access.

We may share necessary records with payment or service partners handling a requested transaction, account protection or a legal duty. We limit the shared data to the stated purpose and payment reference.

Use the Privacy Policy contact route with your account identifier and the records you want removed. We check identity first and explain any data that must remain for security, disputes or legal duties.

KERJITU Privacy Policy, Made Clear

Three Ways to Ask About Your Data

Account privacy request

Wallet record question

Policy contact route

Six Practical Data Handling Commitments

Collected account data

Cookies on your device

Account security checks

Payment matching records

Retention and removal

Changes and requests

Privacy Policy Questions Before Account Access

01 What does the KERJITU Privacy Policy cover?

02 Why does KERJITU need DANA or QRIS payment data?

03 Can I request a copy of my KERJITU data?

04 How can I correct account data under this Privacy Policy?

05 Does KERJITU use cookies on mobile devices?

06 Who receives my payment or account data?

07 How do I ask KERJITU to remove my data?

Related Pages