Reference

petir388 Privacy Policy for Your Account

petir388 Privacy Policy explains how we handle the account details, phone verification, wallet records and device data connected with your access.

Account dataWallet recordsCookie choicesPolicy requests

Explore Our Lobby Read FAQ

What Our Privacy Policy Covers

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

Our Privacy Policy covers data you provide when opening an account, completing phone verification, signing in, contacting support or checking a cashier status. We may handle your account identifier, contact details, device and session signals, selected lobby activity, and records needed to match a wallet or

1
bank transaction. DANA, OVO, GoPay and QRIS appear as payment context when you request a deposit or status check; bank transfer and virtual account references may also be retained for reconciliation. We use this material to operate account access, protect sessions, answer requests and meet applicable
2
legal duties. Where local law permits, you can ask what data we hold, request a correction or ask about deletion limits. The policy applies to our website and its mobile browser sessions, and the current wording is available through the account and policy pages.

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

CONTACT ROUTES

Three Ways To Ask About Privacy

Privacy questions should reach the route that already has the relevant account context.

DATA PRACTICES

How We Handle Your Account Data

We treat the Privacy Policy as an operating process rather than a footer link. Account access, payment matching and security checks each create different records, and we use only the relevant details…

Collected account details

When you open an account, we use the details you submit and the phone verification step to identify the account. Sign-in events and device signals help us detect unusual access without asking for unnecessary wallet credentials.

Payment matching

A DANA, OVO, GoPay or QRIS reference helps us connect a cashier request with the correct account. Bank transfer and virtual account records support reconciliation when a receipt or status needs checking.

Cookie controls

Our website may place session cookies on desktop or mobile browsers for sign-in continuity, security checks and policy access. Browser controls let you remove or block them, subject to account functions that require an active session.

Account protection

We use phone verification, sign-in controls and account checks to reduce unauthorised access. We will not ask you to post a password or verification code in a support request, including one about Privacy Policy.

Retention approach

We retain account, support and transaction records only for operational, security or legal reasons described in the policy. Retention can differ by record type, so a deletion request may have specific limits.

Changes and requests

Use the account support route to ask for access, correction, deletion or clarification. Tell us which record concerns you, such as a phone detail, cookie setting or QRIS receipt, so we can respond accurately.

Privacy Policy Questions Answered

These Privacy Policy answers address the account actions you are most likely to take before opening or using access from Indonesia. If your question concerns a particular wallet record, device session or account detail, use the support path shown in your account and include only the details needed to locate it.

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

Phone verification helps connect you with the correct account and supports access protection. We may use the verification record when handling a sign-in issue or a Privacy Policy request, subject to local law.

Use the signed-in support path and ask for account data access. Include your registered contact detail and specify whether you need account, cookie, support or payment records so we can identify the request.

Yes. Send a correction request through account support and name the detail that needs changing, such as a phone number or contact field. We may verify ownership before applying an account change.

We retain the reference, status and related account context needed to match a DANA or QRIS request. A receipt check can use that reference, while sensitive wallet credentials should remain private.

The period depends on the record and the reason it is retained, including account operation, security, payment reconciliation or legal duties. The Privacy Policy explains applicable limits, and support can clarify a specific record.

You can ask about deletion through the account support route. We assess the request against operational, security and legal needs, so some transaction or account records may need to remain for a defined purpose.

petir388 Privacy Policy for Your Account

Three Ways To Ask About Privacy

How We Handle Your Account Data

Collected account details

Payment matching

Cookie controls

Account protection

Retention approach

Changes and requests

Privacy Policy Questions Answered

01 What does the petir388 Privacy Policy cover?

02 Why does petir388 need phone verification?

03 How can I request a copy of my account data?

04 Can I ask petir388 to correct my details?

05 How are DANA and QRIS records handled?

06 How long does petir388 keep personal data?

07 Where local law permits, can I request deletion?

Related Pages