Reference

pawabet Privacy Policy for wallet access

Our Privacy Policy explains what we collect when you open a pawabet account, connect DANA, OVO, GoPay or QRIS, and move from login into the lobby.

Account dataWallet recordsCookie choicesContact route
Browse Our Lobby Read FAQ
pawabet pawabet Privacy Policy for wallet access
HELP WITH PRIVACY

Get a clear route for policy requests

A policy question should not leave you guessing, so we keep privacy requests tied to the account path you already use. From the support area, tell us whether you need access to your records, a correction, a deletion request or an explanation of a cookie choice. Include the account email or phone detail used at registration, but never send a password or verification code. Our team can also check a DANA, OVO, GoPay or QRIS receipt when a privacy request is linked to payment history.

Team online

Account support

Use the support route inside your account to ask about the Privacy Policy, request a copy of personal records or explain why a detail needs correction. We may ask for an account step that confirms it is you before discussing private account data.

Wallet records

When your request concerns DANA, OVO, GoPay or QRIS activity, attach the payment receipt reference rather than wallet credentials. We use that reference to locate the relevant account event and avoid exposing unrelated transaction details.

Access questions

If a policy page or account setting does not open on your phone, tell us the device path, browser and page name. We can separate a cookie setting issue from an account verification issue without asking you to share your password.

OUR DATA PRACTICE

What you can expect from our handling

We treat the Privacy Policy as an operating process, not a label placed beside the account form.

Account creation

When you open an account, we collect the details needed for the account path and clear phone verification before account access. We use those details to identify your account, send account messages and connect activity to the correct wallet record.

Payment references

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account event can create a receipt reference, amount status and time record. We use that trail to match the cashier event without requesting your wallet PIN or banking password.

Cookie controls

Cookies can remember a login state, preserve a language or region choice and help us understand whether a page loads correctly. You can clear or restrict them through your browser, although some account settings may then need to be selected again.

Device security

We may record device and browser signals around login, verification and unusual account activity. These signals help us protect the session and investigate access concerns; they are not a request for your device password or private wallet credentials.

Retention period

We keep personal records for the period needed to provide the requested account service, resolve a payment question or meet a legal requirement. When a record is no longer needed, we remove it or reduce its link to your account where practical.

Changes and contact

You can ask us to correct account details, explain a processing purpose or consider deletion where local law permits. Send the request through account support with enough detail to locate your record, and we will use the stated contact path to respond.

Privacy Policy answers before you open

These Privacy Policy answers address the searches we hear before an account is opened: what we collect, why payment records appear, how cookies behave and how a request reaches our team. Each answer stays focused on pawabet account handling, including the phone verification step and the wallet references shown for DANA, OVO, GoPay and QRIS.

It covers account details, phone verification, device and browser signals, cookies, payment references, support messages and policy requests. It explains why each category may be used, how records are retained and how you can ask for access, correction or deletion where local law permits.

We collect the payment reference, status and related account event so we can match a DANA or QRIS transaction, check a receipt and resolve a wallet question. We do not need your wallet PIN, banking password or full private sign-in credentials for that process.

Yes. The Privacy Policy covers OVO and GoPay status details in the same way as other supported wallet records. We use the reference to connect an account event with its payment result, investigate an unmatched receipt and keep the request limited to the relevant account.

You can send a data access request through the account support route. Include the registration email or phone detail and describe the records you need, such as account details, cookie choices or a payment reference. We may complete an account check before releasing private records.

Use support inside your account and identify the field that needs correction, such as a contact detail or account preference. We may ask for the phone verification step or another account check, then update the record when the request is confirmed and permitted.

Send a deletion request through the same support path and explain which account records you want removed. We assess the request against active account needs and legal retention duties. Where local law permits, records no longer required are removed or separated from direct account identification.

Start with account support and name the page, browser and device involved. We can explain a cookie setting, login session record or device security signal without asking for a password. You can also adjust cookies in your browser, though some account preferences may reset.

Related Pages

pawabet Indonesia About Us Account information FAQ Live Roulette Salon