Reference

Open the petir jitu Privacy Policy

Your account, wallet and device choices receive a clear explanation in the petir jitu Privacy Policy.

Account dataWallet recordsDevice choicesCookie controls

Browse how account data is handled

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

Our Privacy Policy applies when you create an account, complete phone verification, sign in from a mobile browser, or contact us about wallet status. We may record account identifiers, verification details, device signals, access times and transaction references needed to maintain account access and answer payment

1
questions. DANA, OVO, GoPay, QRIS, bank transfer and virtual account references can appear in our records when you choose those rails, while the payment provider may hold its own records under its terms. We use these details to process requests, detect unusual access and keep policy
2
records accurate. Where local law permits, you can ask what we hold, request a correction or ask about deletion. Some records may remain when needed for security, dispute handling or a legal request.

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

CONTACT OUR TEAM

Reach support about Privacy Policy questions

A clear contact path helps when you need to ask about the Privacy Policy rather than a wallet transaction itself. Use the account support route and include your registered phone number, the subject of your request and the data action you want us to consider. We may ask for account checks before discussing private records.

Team online

Account support route

Send a Privacy Policy request through the account support path. We use your registered phone number to match the request before discussing account or device records.

Wallet status context

If your question concerns DANA, OVO, GoPay or QRIS data, include the payment rail and reference shown in your account so we can separate wallet records correctly.

Receipt and access checks

For a privacy request linked to a receipt, login or verification step, share the date and reference without sending your password or full wallet credentials.

DATA CONTROL

Explore six Privacy Policy safeguards

We keep the Privacy Policy practical by connecting each promise to an account action you can recognise.

Data we receive

We may receive your account name, registered phone number, verification result, device signals and support messages. Payment references from DANA or bank transfer help us identify a transaction without replacing the provider’s own records.

Cookie choices

Cookies and similar browser storage can remember access preferences, help protect a login and support page performance. You can adjust browser controls, though some account functions may then require another verification step.

Account protection

Phone verification, sign-in checks and device signals help us identify unusual account access. Never send a password or one-time code in a Privacy Policy request or support message.

Retention approach

We keep records only as long as needed for the stated account, support, security or dispute purpose, unless a longer period is required by local law or a valid legal request.

Correction requests

You can ask us to correct inaccurate account details or clarify how a QRIS, GoPay or virtual account reference appears in our records. We may verify ownership before making a change.

Access and eligibility

Where local law permits, you can ask for access, deletion or a copy of relevant personal data. Access to the service itself depends on local law and account checks.

Browse Privacy Policy answers for your account

These Privacy Policy answers address the account actions Indonesian customers most often need to understand before opening an account. We keep the wording tied to phone verification, mobile access, payment references and requests for personal data.

It covers account details, phone verification, device signals, cookies, support messages and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

Phone verification helps connect an account request to the correct account holder and helps protect sign-in access. We may use the result when handling a Privacy Policy access or correction request.

Yes, it explains how our records may include DANA or QRIS references used to identify an account transaction. The payment provider may separately retain its own records under its terms.

Use the account support route and state that you are making a Privacy Policy data request. Include your registered phone number and request type; we may verify account ownership first.

Where local law permits, you can request correction or deletion of relevant personal data. Some records may remain for security, dispute handling or a legal request, and we will explain the reason.

We may record device and browser signals that help protect account access and identify unusual sign-ins. Cookie controls can be changed in your browser, although some functions may request verification again.

Yes. Access and eligibility depend on local law. Our Privacy Policy still explains your data choices, and where local law permits, you can ask about access, correction or deletion.

Open the petir jitu Privacy Policy

Reach support about Privacy Policy questions

Account support route

Wallet status context

Receipt and access checks

Explore six Privacy Policy safeguards

Data we receive

Cookie choices

Account protection

Retention approach

Correction requests

Access and eligibility

Browse Privacy Policy answers for your account

01 What does the petir jitu Privacy Policy cover?

02 Why does petir jitu ask for phone verification?

03 Does the Privacy Policy cover DANA and QRIS records?

04 How can I request my data from petir jitu?

05 Can I ask for a correction or deletion?

06 How does the Privacy Policy treat mobile devices?

07 Does access to petir jitu depend on local law?

Related Pages