Reference

penidabet Privacy Policy For Your Account

penidabet explains how we collect, use and protect the details connected with your account, including phone verification and wallet activity.

Clear data purposesWallet record controlsDirect privacy contact
penidabet penidabet Privacy Policy For Your Account
PRIVACY HELP DESK

Where To Ask About Your Privacy Policy

A direct support request gives you a practical route when an account record, cookie setting or wallet reference needs clarification. Tell us the account phone number, the affected page and the request you want handled; do not send a password or full payment credential. We use the same privacy path whether you browse from a phone or desktop.

Team online

Account contact

Use the account support chat to ask about personal data held for your profile, phone verification records or a correction request. We may ask for account details to confirm that the request comes from you.

Wallet record query

For DANA, OVO, GoPay or QRIS references, include the transaction date and visible reference only. We can trace the matching account record without asking you to share a wallet password or security code.

Access concern

If a privacy page or account control does not load on your mobile browser, tell us the device path and browser behaviour. We will direct the request to the relevant account support route.

DATA HANDLING PRACTICE

What We Do With Your Account Details

We keep this Privacy Policy practical by separating account needs from optional site functions. Phone verification helps us connect you with the correct account, while device and cookie records help us maintain…

Account collection

When you open an account, we collect the details needed to create and protect it, including contact information and phone verification results. We use those records to identify your account during support and access checks.

Payment matching

A DANA, QRIS, OVO or GoPay reference may be stored beside an account transaction record. Bank transfer and virtual account references can serve the same matching purpose when a status needs checking.

Cookies and devices

Cookies and device signals can remember session choices and help identify unusual access. You can manage browser cookie controls, although changing them may affect sign-in continuity or privacy settings on the site.

Account security

We use phone verification and account checks before discussing sensitive records. Keep your password and wallet security codes private; our support route does not need those secrets to process a privacy request.

Retention period

We retain personal and transaction records for the time needed to provide account access, resolve disputes, protect the service or meet a legal record duty. The period can differ by record type and local requirement.

Change requests

Ask us to correct inaccurate details, explain a stored record or assess a removal request through account support. Include the request clearly, and we may verify your identity before making a change.

Privacy Policy Answers For Indonesian Accounts

These Privacy Policy answers address the account questions we expect before you open an account or contact us about stored data. They cover collection, wallet references, device access, cookies, retention and the identity check used for account requests. If your situation is not listed, send the specific question through support.

It covers account details, phone verification, device and cookie data, transaction references, support requests, security checks and retention. It explains why we use each category and how you can ask about your records.

We use your phone number to create and identify the account, complete phone verification and respond to account requests. Keep the number current so we can confirm ownership before discussing personal data.

Yes. The policy includes transaction references connected with DANA, QRIS, OVO, GoPay, bank transfer and virtual account activity. We use these references to match status, investigate disputes and maintain account records.

Contact account support with the account phone number, the record you believe is inaccurate and the correction requested. We may verify ownership first, then confirm whether the change can be applied.

Cookies can retain session choices and help us recognise unusual access on your browser. You can change browser cookie controls, but blocking them may interrupt sign-in continuity or certain privacy settings.

We keep each record for the period needed for account access, security, dispute handling or a legal record duty. Retention can differ between verification, transaction and support records under local requirements.

You can submit a removal request through account support. We assess the request against account security, unresolved transactions and any legal retention duty, then explain which records can be removed or retained.