Reference

pecah388 Privacy Policy For Your Account

pecah388 Privacy Policy explains how we collect, use and protect the details connected with your account, device and wallet activity.

Account clarityWallet recordsMobile securityPolicy access
pecah388 pecah388 Privacy Policy For Your Account
CONTACT OUR TEAM

Privacy Questions Reach The Right Desk

A clear contact route matters when you want to ask about your Privacy Policy rights or correct an account detail. Our support path connects policy questions with the account and wallet context needed to answer them, without asking you to post sensitive credentials in an open message. Include your registered phone number in masked form, the date of the issue and the relevant receipt reference so we can locate the right record. Access remains where local law permits.

Team online

Account desk

Use the account support channel for questions about phone verification, login records, device access or a request to correct your registered details. We may ask for an account step that confirms ownership, but we will not ask for your wallet PIN or full payment password.

Wallet checks

For DANA, OVO, GoPay, QRIS, bank transfer or virtual account records, send the payment date and reference shown on your receipt. Our team can compare the status with the account record and explain what personal data was used for that check.

Policy requests

Ask support to access, correct or clarify personal data held under your account. State the request plainly and use the phone or email connected with your account. We may verify ownership before responding, especially when the request concerns login history or wallet records.

DATA HANDLING DETAILS

Six Practical Privacy Safeguards

We keep this policy practical by connecting each data use with an account action you can recognise.

Account records

When you create an account, we record the details needed to identify that account and complete phone verification. This can include your contact details, verification result and account settings. We use the information for access, support and security checks rather than unrelated messages.

Device signals

A phone, tablet or desktop session can produce technical signals such as browser type, operating system, approximate network details and sign-in time. These signals help us review unusual access and keep your account path consistent when you move from mobile browsing to desktop.

Cookies explained

Cookies can remember a session, preserve basic preferences and show us whether a page loads correctly. They may also help us understand navigation between the Privacy Policy and account pages. You can manage cookies through your browser settings, although some account functions may then work differently.

Payment references

We handle transaction references, amount status and route details needed to match DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. We do not need your wallet PIN to check a receipt. Keep your payment credentials inside the wallet or banking service.

Retention choices

We retain account, security and transaction records for as long as needed for the purpose described in this policy, account support and applicable legal duties. When a record is no longer required, we aim to remove it or separate it from direct account identifiers.

Your requests

You can ask what personal data we hold, request a correction, ask about processing or raise a concern through support. We may confirm your identity before sharing or changing records. That step protects your account from a request made by someone else.

Privacy Policy Questions From Indonesia

These Privacy Policy answers cover the account actions you are most likely to take before opening or using an account. They explain why we need certain details, how wallet references are handled, what happens on a mobile device and how to contact us about access or correction. If your question involves eligibility, access depends on local law. For a record-specific answer, contact support using the account path linked to your details.

The pecah388 Privacy Policy covers personal data connected with account creation, phone verification, sign-in, device use, support contact, cookies and payment status checks. It explains why we use each category, how long records may remain and how you can ask for access or correction where local law permits.

Phone verification helps connect an account request with the person controlling the registered contact. We use the result for account access, ownership checks and support requests. If you ask us to change account details or provide a data copy, we may repeat an ownership check.

Yes. The Privacy Policy covers the transaction references and status details needed to match DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity with your account. We use those details for reconciliation and support, while your wallet PIN stays with the payment provider.

We may receive technical details such as device type, browser, operating system, approximate network information and sign-in time. These signals help us protect account access and investigate unusual sessions. They also help explain why a mobile page may behave differently from the desktop lobby.

Contact our account support route with the registered phone or email, a clear description of the incorrect detail and any useful account step. We may verify ownership before changing the record. This process helps prevent another person from altering your profile or access history.

We keep each category for the period needed to provide account access, answer support requests, protect against misuse and meet applicable legal duties. Retention can differ for account details, security logs and payment references. When a record is no longer needed, we aim to remove or separate it.

Use the support path connected with your account and state whether you want access, correction, processing details or clarification about a specific record. Include a date or receipt reference when relevant, but never send a wallet PIN. We will explain the next ownership check and response path.