Reference

pisangbet Privacy Policy for Your Account Data

Our Privacy Policy explains how pisangbet handles the data connected with your account, DANA, OVO, GoPay and QRIS activity.

Account dataWallet recordsCookie choicesSecurity checks
pisangbet pisangbet Privacy Policy for Your Account Data
HELP WITH YOUR DATA

Three Ways To Ask About Privacy

A clear support route matters when a name, phone number or wallet reference does not look right. Sign in and use the account support path for a request linked to your profile; include the relevant receipt or date so we can locate the record. If you are in Semarang or elsewhere in Indonesia, the same account route applies on mobile and desktop.

Team online

Account request

Send a privacy request from your signed-in account and tell us whether you want a data copy, correction or removal request. We may ask for a phone verification step before discussing account details.

Wallet record

For DANA, OVO, GoPay or QRIS questions, include the payment reference and approximate time. We use those details to separate your receipt from another account without exposing unrelated records.

Access trouble

If you cannot sign in, use the account access support path and describe the device, browser and last successful login. Do not send a password or full wallet PIN in your message.

OUR DATA PRACTICE

Six Privacy Steps Behind Your Account

Privacy is handled through ordinary account actions rather than hidden settings. We separate sign-in controls from payment references, limit internal access to data needed for a task, and…

Collection

We collect details you submit for account creation, phone verification and support, plus device and sign-in signals needed to protect…

Payment matching

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references are used to identify the related account action.

Cookie control

Cookies can keep a session active, remember selected settings and show whether a page works correctly.

Account security

Phone verification, sign-in records and device signals help us check unusual access.

Retention

We keep account, payment and support records for operational, security or legal needs.

Change requests

Ask us to correct, copy or delete eligible data through the signed-in support path.

Privacy Policy Answers For Account Holders

These Privacy Policy answers cover the questions that usually arise before account access or after a wallet action. We keep each response tied to a practical step, from phone verification and cookies to a request for a data copy. Where a right or restriction varies by location, the result depends on local law.

It covers account details, phone verification, sign-in and device records, cookies, support messages, payment references and how we handle requests to copy, correct or remove eligible data.

Phone verification helps connect an account to the correct contact route and supports access checks. We may use the result when a sign-in or privacy request needs additional account confirmation.

Yes. The Privacy Policy covers DANA, OVO, GoPay and QRIS references, as well as bank transfer and virtual account records, when those details are connected with your account activity.

Sign in, open the account support path and ask for a data copy. Include the phone number linked to your account; we verify ownership before releasing any profile or payment-related record.

Yes, you can request a correction through the signed-in support path. Tell us which field is wrong and provide the accurate detail; we may ask for a verification step before changing it.

Cookies can remember your session and selected settings, and help us check page performance on mobile or desktop. Browser controls can remove them, but some account actions may ask you to sign in again.

You can request removal of eligible data, but some account, payment or support records may need to remain for security or legal reasons. The outcome depends on local law and the record type.