Reference

Privacy Policy for Your perang jitu Account

Our Privacy Policy explains how perang jitu handles the account details, device data and wallet records connected with your access.

Clear data purposesWallet record controlsAccount access stepsCookie choices
perang jitu Privacy Policy for Your perang jitu Account
CONTACT ROUTES

Privacy Help Beside Your Account

A clear contact path helps when a Privacy Policy question is separate from a stalled login or wallet status.

Account data request Ask us to identify the personal data linked to your account, explain its purpose…
Wallet record question For a DANA, OVO, GoPay or QRIS record, share the reference and date without…
Access concern If your account opens differently on mobile or desktop, tell us the device path…
DATA HANDLING

What We Do With Your Account Details

We keep the Privacy Policy tied to actions you can recognise: creating an account, confirming your phone, checking a wallet reference and returning to the lobby from a…

Account identity

Your phone number, login details and verification result help us connect the right person with the right account.

Device signals

A mobile browser or desktop session can provide device and connection signals used to protect sign-in and identify unusual access.

Cookies

Cookies can remember a session, support account navigation and help us understand whether a policy page loads correctly.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity may leave reference and status data.

Retention timing

We retain account and transaction details for as long as needed for the stated account, support and record purposes, then…

Change requests

You can ask us to correct account data, explain a processing purpose or consider a removal request where local law…

Privacy Policy Answers for Indonesian Accounts

These Privacy Policy answers address the searches we hear most often before an account is opened or a wallet record is queried. They cover the data used during phone verification, mobile access, cookies, payment references and requests made through support. If your situation is not covered, send the account phone number and a short description through the signed-in contact route. We will use that context to locate the relevant record without asking for your password or wallet security code.

It covers data collected when you create an account, confirm your phone, sign in, browse from a device, use DANA or QRIS, and contact support. It explains purposes, cookies, retention, account security, request handling and the conditions that apply where local law permits.

The policy describes account identity details such as your phone number and login record, verification results, device and connection signals, activity needed for support, and transaction references. We use these details to connect requests with your account and check payment status.

We may retain payment references, status, date and account matching details for DANA, OVO, GoPay and QRIS. These records help answer receipt or wallet questions. We do not ask you to send a wallet password or one-time code through support.

Use the signed-in support route and state whether you want a data explanation, copy request or correction. Include the phone number linked to your account. We may verify ownership first, then respond according to the Privacy Policy and local requirements.

Cookies can maintain a session and help the mobile path return you to the account area after sign-in. Your browser controls can restrict them, but the account may ask for another login. The policy explains which cookie purposes apply and how to ask questions.

You can send a removal request through the signed-in support route. We assess which records can be removed, reduced or retained for account and transaction purposes. Any decision depends on local law, and we may verify your account before discussing the result.

Start with the support route shown in your signed-in account and describe the data issue, device path or payment reference. For a question about Semarang access or a QRIS record, add that context. We will direct the request to the relevant privacy contact.