Reference

Privacy Policy for petir jitu Accounts

petir jitu Privacy Policy sets out how we collect, use and protect details connected with your account, phone verification, mobile browser and wallet activity.

Account dataWallet recordsCookie choicesContact requests
petir jitu Privacy Policy for petir jitu Accounts
CONTACT ROUTES

Get Help With Privacy Requests

A clear contact route helps you handle a data question without repeating your account story. Start from the support contact shown inside your signed-in account, then state whether you need access, correction…

Account contact Use the support route displayed after sign-in for a Privacy Policy request. Tell us whether you need a copy of account details, a correction to your phone record or clarification about a wallet reference.
Wallet query If a DANA, OVO, GoPay or QRIS entry looks unfamiliar, send the transaction reference through the secure account contact path. We use the reference to locate the record without asking you to post private payment details in an open message.
Access check A phone verification step may be required before we disclose or change personal data. This protects the account when a request comes from a new mobile browser or a device that has not previously signed in.
Correction request For an incorrect name, phone detail or account record, describe the exact field and the requested change. We compare the request with the account record before applying an amendment or explaining why a record must remain.
DATA PRACTICE

How We Handle Your Account Data

We keep this Privacy Policy tied to actions you can recognise: opening an account, confirming a phone number, signing in, checking a wallet status or asking for support.

Collection

We collect details you provide during account opening and phone verification, together with sign-in and support records needed to operate the account. A wallet reference can identify a DANA, OVO, GoPay, QRIS, bank transfer or virtual account status.

Use of data

We use account and transaction records to provide access where local law permits, confirm a requested action, resolve a payment status question and detect activity that could place your account at risk. We do not use one request as permission for unrelated purposes.

Cookies

Cookies and similar device records can keep a sign-in path working, remember a selected setting and help us understand whether a page loads correctly. You can manage browser cookie controls, although turning them off may affect account access or saved preferences.

Account security

Phone verification helps us distinguish you from someone attempting access through another device. Keep your sign-in details private, use the secure account path for requests and tell us promptly if a device or account action does not look familiar.

Retention

We retain records for as long as needed for the purpose that created them, including account administration, payment reconciliation, security checks or a legal obligation that applies where local law permits. When a record is no longer needed, we remove or anonymise it through our internal process.

Your request

You can ask what personal data we hold, request a correction, ask about deletion or raise a concern about handling. Send the request through the signed-in support route; we may verify your phone before responding or changing the account record.

Privacy Policy Questions Answered

These questions focus on the parts of our Privacy Policy that matter when you open an account from Indonesia. We explain the account step, device path, wallet references and contact process in plain language, while keeping eligibility subject to local law. If your situation is not covered, use the secure support route connected with your account.

It covers personal details connected with account opening, phone verification, sign-in, cookies, support requests and wallet or transfer status. It also explains how we use, protect, retain and amend those records when you access the service where local law permits.

We use your phone number for the account verification step and to help distinguish your request from an unauthorised attempt. If you ask to access or change personal data, we may verify that phone detail before discussing the account.

Yes. The Privacy Policy covers references needed to identify a DANA or QRIS status, as well as OVO, GoPay, bank transfer and virtual account records. We use those references to reconcile an account action or answer a status question.

Sign in and use the support contact shown in your account area. State that you want access to your personal data and include the relevant account detail. We may complete a phone verification check before sending records or explaining any restriction.

Yes. Send a correction request through the secure account contact path and identify the field that is wrong, such as a phone detail or account name. We compare the request with existing records before applying the change or explaining the result.

We keep each record for the period needed for its stated purpose, such as account administration, payment reconciliation, security checks or an applicable legal duty. When retention is no longer needed, we remove or anonymise the record through our internal process.

They can. Cookies may support sign-in, remember a setting and show whether a page loads correctly on your mobile browser or desktop. You can adjust browser controls, but disabling cookies may interrupt the account path or remove saved preferences.