Reference

pawpaw4d Privacy Policy for Your Account

The pawpaw4d Privacy Policy explains how we collect, use, protect and retain details connected with your account, wallet activity and device access.

Clear data purposesWallet records explainedPhone access controlsIndonesia privacy contact
pawpaw4d pawpaw4d Privacy Policy for Your Account
CONTACT ROUTES

Privacy Help Near Your Account Path

A direct support route helps you resolve privacy questions without repeating your account story across unrelated channels. When you contact us, include the phone number or account identifier linked to your request, but do not send a password, wallet PIN or full payment credential. We can help you understand a data record, check a wallet reference or explain the next step for a correction request. Access for customers in Surabaya and elsewhere in Indonesia depends on local law.

Team online

Account access

If phone verification blocks your account, contact support with your registered phone number and device type. We use those details to locate the relevant access record, explain what we can disclose and avoid asking you to share your password or wallet PIN.

Wallet records

For a DANA, OVO, GoPay or QRIS privacy question, provide the date, amount reference and payment route rather than a full credential. We can connect the request to the account ledger and clarify whether the record is pending, matched or retained.

Data requests

Send a correction, access or deletion request through our account support channel. We may ask you to complete phone verification before discussing personal data, so we disclose account details only to the person who can show control of the account.

DATA CONTROLS

Six Ways We Handle Privacy

Privacy controls work best when you know what happens at each account stage. We separate account identification from payment references, use device signals for security checks and keep cookie choices tied to…

Collection points

We collect information when you create an account, verify a phone number, sign in, request support or use the cashier. This can include contact details, account events, device signals and payment references needed to match DANA, QRIS or bank activity.

Cookie choices

Cookies and similar storage help keep a signed-in session, remember selected settings and identify technical errors. We use them for the functions described in this policy, and you can adjust browser controls, although some account access steps may then need to run again.

Account security

Phone verification, sign-in events and device information help us detect access that does not fit your account pattern. If a security check pauses access to Live Dealer Lobby or Fishing God, support can explain the required account step without requesting your secret credentials.

Payment separation

We keep payment references connected to the account activity they explain, while avoiding unnecessary storage of wallet secrets. DANA, OVO, GoPay, QRIS, virtual account and bank transfer entries may show route, time and status so we can reconcile a request.

Retention timing

We retain personal data only for the period needed for account operation, security investigation, support history or legal duties. Retention can differ by record type, so a payment reference may remain after a device session ends. Ask support for the reason behind a record.

Changes and contact

You may ask us to access, correct or remove personal data by contacting support through the account path. Include the request type and registered phone number; we verify control first, then explain the result, any limits and the next available step.

Privacy Policy Answers for Indonesia

These Privacy Policy answers focus on the questions we expect you to ask before opening an account or sending a data request. They cover phone verification, payment references, cookies, device access, retention and corrections. If your situation is not listed, contact support with the smallest amount of personal detail needed to identify the request.

It covers personal details and account events collected when you open an account, verify your phone, sign in, use DANA or QRIS, contact support or request account changes. It also explains cookies, device signals, payment references, retention and the ways you can ask about your data.

Phone verification helps us confirm control of an account before we disclose account details or process a sensitive change. It also helps identify unusual sign-in activity. We will not ask you to provide a password, wallet PIN or full payment credential during this step.

Yes. The Privacy Policy covers payment references linked to DANA, OVO, GoPay and QRIS, including route, time, account connection and status where needed for reconciliation or support. We use the reference to investigate a record and avoid requesting unnecessary wallet secrets.

Contact support through the account path and state whether you want access to a record or correction of a detail. Include your registered phone number and a clear description, but leave out passwords and wallet PINs. We verify account control before discussing the requested data.

We keep each record for the period needed for account operation, security checks, support history or legal duties. A device session can end while a payment reference remains for reconciliation. Contact us if you want the retention reason for a particular account or cashier record.

You can send a deletion request through support, and we will assess it under the Privacy Policy and applicable local requirements. Some records may need to remain for security, dispute handling or legal duties. We explain the result and any reason a record cannot be removed.

The policy still applies when you use a phone, tablet or desktop to access the account. Device type, browser and session signals may be recorded for security and technical support. Account access depends on local law, and you can ask us what device record relates to your request.