Reference

Privacy Policy for Your pay33 Account

Your account details, phone verification and wallet records are handled under the pay33 Privacy Policy, so you can understand what we collect before opening the lobby.

Account dataWallet recordsCookie choicesContact path
pay33 Privacy Policy for Your pay33 Account
PRIVACY HELP PATH

Where to Ask About Privacy Policy

A clear support route helps when a privacy request and an account issue arrive together. Open the account support path and tell us whether your question concerns phone verification, a device record…

Account support path Use the support link beside your account area and describe the Privacy Policy request in your own words. Include the affected email or phone detail, but never send your password or a full wallet security code.
Payment record check For a DANA, OVO, GoPay or QRIS question, share the payment date, reference and displayed status. We use those limited details to locate the record while avoiding a request for unnecessary wallet credentials.
Access correction request If your name, phone detail or device record needs correction, ask through account support after signing in. We may request phone verification before changing information linked to your pay33 account.
HANDLING YOUR RECORDS

How pay33 Handles Account Data

Privacy work is part of each account step, from the first phone verification to a later request about a wallet receipt.

Account collection

When you open an account, we collect the details needed to create access and complete phone verification. Sign-in events and requested account actions may be recorded so we can investigate an access problem without asking you to repeat every step.

Cookie controls

Our browser path may use cookies or similar signals for sign-in continuity, security and remembered choices. You can review browser controls, although turning them off may require another verification step when you return to the lobby.

Wallet separation

DANA, OVO, GoPay and QRIS references identify a payment event rather than your wallet password. We limit payment details used for matching, and support may ask for a receipt reference before discussing status.

Account security

Phone verification helps connect account access to the contact detail you provided. Device and sign-in signals can be reviewed when activity looks unusual, while password and security-code requests remain outside ordinary support messages.

Retention period

We keep records only for the period needed for account access, payment tracing, security checks, dispute handling or applicable legal duties. When a record is no longer needed, our process removes it or separates it from direct account identifiers.

Changes and requests

You can ask what personal data we hold, request a correction, or ask how a record is used through account support. We may confirm your identity first, and any request outcome depends on local law and the record concerned.

Privacy Policy Questions for Indonesia

These answers address the Privacy Policy searches we hear most often before an account is opened or a wallet record is checked. They focus on account access, payment references, device information and requests to pay33, with the same local-law wording used throughout this page.

It covers account details, phone verification, sign-in and device records, cookies, support messages, payment references and retention. It also explains how we handle DANA, OVO, GoPay, QRIS, bank transfer and virtual account records connected with your account.

Phone verification helps us create the correct account link and respond to access requests from the right person. We may use the verification event as a security record, especially when a new device or unusual sign-in needs checking.

No. Payment references such as DANA or QRIS receipt details help us match a transaction status to your account, but your wallet password and security code should not be sent to support. We ask for limited reference details instead.

Yes, contact us through the account support path and identify the record you believe is wrong. We may ask you to sign in or complete phone verification before making a change, and the result depends on local law and the record type.

We retain records for the period needed for access, payment tracing, security checks, dispute handling or applicable legal duties. The period can differ by record, so support can explain the reason for retention without exposing another account's details.

Send a request through account support with the email or phone detail linked to your account. We will confirm identity before responding, describe which records can be supplied, and handle the request where local law permits.

Yes, it covers the mobile browser path as well as desktop access. Device signals, cookies and sign-in records may differ by browser settings, while the same account, phone verification and wallet-reference rules apply where local law permits.