Reference

Privacy Policy for Your petir 388 Account

Our Privacy Policy explains how we collect, use and protect the details connected with your petir 388 account.

Account dataWallet recordsCookie choicesSecurity steps
petir 388 Privacy Policy for Your petir 388 Account
CONTACT ROUTES

Privacy Policy Help Through Your Account

A clear contact path helps you ask about the Privacy Policy without repeating your account history.

Policy questions Send a message through the account support route when you want to understand what data we hold, why a phone check was requested or how the Privacy Policy applies to your access. We use the account details you provide to locate the correct record and reply to the same request.
Data change request Ask us to correct an inaccurate name, phone detail or account reference through support. We may request a matching account step before changing personal data, especially when the request concerns wallet records or access history. This check helps prevent another person from altering your account details.
Payment record query If a DANA, OVO, GoPay, QRIS, bank transfer or virtual account entry looks unfamiliar, include the date and reference shown in your account. We use that information to trace the payment record and explain what was stored, while keeping your PIN and password out of the request.
DATA PRACTICES

What We Do With Account Data

We keep this Privacy Policy practical by linking each data use to an account action you can recognise.

Collection

We collect details you enter during account opening, phone verification and support contact. We can also receive device type, browser signals and access times when you use the mobile web path. Payment references from DANA, QRIS and bank transfer help us identify a transaction without storing your wallet PIN.

Use of data

Account data lets us provide sign-in, confirm a requested account step, respond to a policy question and investigate a payment status. We may use access signals to identify unusual activity around titles such as Speed Blackjack Live or Nusantara Treasure Reels without using game activity as a reason to collect unrelated personal details.

Cookies

Cookies can keep your sign-in state, remember selected page settings and help us understand technical errors on a mobile browser. You can remove or block cookies through your browser controls, but some account functions may ask you to sign in again or may not work as expected after that change.

Account security

We use phone verification and access signals to reduce the risk of account changes by another person. Keep your password and wallet PIN private, and contact support through your account if a sign-in or payment reference seems unfamiliar. We do not need your PIN to inspect a DANA or QRIS record.

Retention

We retain account, support and payment records for the period needed to operate the service, investigate security events or meet a legal duty. Retention can differ by record type and local requirement. When a record is no longer needed, we remove it or keep it in a form that does not directly identify you where local law permits.

Your request

You can contact us to ask what personal data is held, request a correction, ask about deletion or seek an explanation of a Privacy Policy decision. We may confirm your account through the registered phone detail before acting. Include a clear request and account reference, but never include your password or wallet PIN.

Privacy Policy Questions About petir 388

These Privacy Policy answers address the account and payment questions you may search before opening access. We keep the wording tied to actual account steps, local wallet references and your request options. Where a legal condition affects access, it depends on local law, and we will use the contact route available inside your account for follow-up.

The Privacy Policy covers account details, phone verification, device and access signals, support messages, cookies and payment references. It explains how we use those records for account access, security, service handling and legal duties. It also describes how you can request a copy, correction or removal where local law permits.

We use your phone detail for account identification and a verification step before access or sensitive account changes. It can also help us connect a support request with the correct account. We do not need your wallet PIN, and you should not include that secret in a Privacy Policy request.

Yes. The Privacy Policy covers payment references connected with DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity. We use those references to match a payment status with your account and investigate a query. Wallet PINs and passwords should remain private and are not needed for this check.

Send a clear correction request through the support route inside your account. State which detail is inaccurate and include the relevant account reference. We may confirm your registered phone detail before changing it, particularly when the request concerns access history or a payment record covered by the Privacy Policy.

We keep personal data while it is needed for account operation, security review, support handling or a legal duty. The period can differ for account, payment and message records. When the reason ends, we remove or anonymise the record where local law permits, subject to any continuing legal requirement.

You can block or remove cookies through the controls in your mobile or computer browser. Cookies may keep sign-in continuity and page settings, so removing them can require another account sign-in or affect some account functions. The Privacy Policy explains why these technical records support account access.

Use the support contact route shown after signing in and identify your request as a Privacy Policy matter. You can ask about held data, correction, deletion or a use explanation. Include your account reference and registered contact detail when appropriate, but leave out your password and wallet PIN.