Reference

tuanpencet Privacy Policy For Your Account

The tuanpencet Privacy Policy explains what we collect when you create an account, sign in from a phone or desktop, use DANA or QRIS, and contact our support…

Account recordsWallet privacyCookie choicesAccess requests
tuanpencet tuanpencet Privacy Policy For Your Account
HELP WITH PRIVACY

Get Policy Help Through Your Account

Privacy questions should be easy to route, so we connect each request to the account details you already use.

Account access If you cannot reach your account, use the account help path and identify the…
Wallet records For a DANA, OVO, GoPay or QRIS question, include the relevant payment reference and…
Policy requests Ask us to access, correct or remove eligible personal details through the same support…
DATA HANDLING DETAILS

How We Protect Your Privacy Choices

We keep this policy practical by separating account operation from unrelated browsing activity.

Data we receive

We receive details you provide during account creation and support contact, along with sign-in time, device type, IP address and…

Cookies on devices

Cookies can keep a login session, remember a language or help us identify a broken page.

Account security

A clear phone verification step may appear before account access or a sensitive change.

Retention periods

We keep account, payment and support records for as long as they serve account operation, dispute handling or legal duties.

Changes to details

If your phone, email or account detail changes, contact us through the account help path rather than opening a second…

Who receives requests

Our privacy contact route is handled by the support team responsible for account and wallet questions.

Privacy Policy Answers For tuanpencet

These Privacy Policy answers cover the questions you may ask before creating an account or when checking an existing record. We explain the practical path for account data, cookies, wallet references, device details and correction requests. If your situation is not listed, use the account help path with the detail connected to your account. Access depends on local law, including whether a request can be completed for your location.

It covers personal details you provide, account access records, device and session signals, cookie use, payment references and support messages. The policy explains how we use these details for account operation, security, dispute handling and legal needs, with access where local law permits.

Yes. When you use DANA, OVO, GoPay or QRIS, we keep the payment reference and status needed to match your account request. We do not need your wallet password or unrelated wallet history to check a payment record.

A phone or desktop can provide device type, operating system, IP address and session events. We use those signals to maintain login security, investigate an account problem and recognise unusual access. They help protect your account path and are not a request for unrelated phone content.

You can ask for access to eligible personal data through the account help path. Include the phone or email connected to your account. We may verify your identity before disclosure, and the response may be limited where local law protects another person or requires continued retention.

Send a correction request through the account help path and describe the phone, email or other detail that needs changing. We compare the request with your account record before editing it, then keep a limited change history when needed for security or dispute handling.

Retention depends on why the record exists. Account, payment and support details may remain while needed for operation, dispute handling or legal duties. When that need ends, we remove or de-identify the data where local law permits rather than keeping it without a purpose.

You may request deletion of eligible personal data through the account help path. We first verify the account connection and check whether a payment, dispute or legal duty requires retention. If deletion is allowed, we remove or de-identify the relevant record and explain any exception.