Reference

paito china Privacy Policy, Clearly Set Out

paito china explains in this Privacy Policy how we collect, use and protect the account details connected with your access, including phone verification and wallet activity.

Account dataWallet recordsCookie choicesSupport requests
paito china paito china Privacy Policy, Clearly Set Out
CONTACT YOUR WAY

Get Policy Help Beside Account Support

A clear support route helps when you need a Privacy Policy answer rather than a general account reply. Sign in first where possible, then send your question through the account support path with the phone number on your profile and the relevant receipt reference. If a DANA or QRIS status needs checking, include the date and amount shown in your own wallet. We use those details to locate the right record without asking you to share a password or security code.

Team online

Account support path

Open support from your signed-in account and identify the Privacy Policy question clearly. Adding your registered phone number helps us locate the correct profile while keeping your password and one-time security code private.

Wallet receipt check

For DANA, OVO, GoPay or QRIS questions, attach the payment reference or receipt image with sensitive wallet credentials covered. We can compare the reference with the account record and explain the next step.

Access request route

Ask through support when you want to see, correct or clarify personal data held in your account. We may ask for Account Verification before releasing account-specific material, so the request reaches the right person.

CONTROL YOUR RECORD

What We Do With Your Personal Data

We handle Privacy Policy requests through the same account controls used for login and verification, rather than relying on an unknown message sender.

Collection scope

We collect account details you submit, phone verification results, login activity and support correspondence. Payment references from DANA, OVO, GoPay, QRIS, bank transfer or a virtual account are used to connect a transaction status with your profile.

Use of records

Account data supports login, Account Verification, payment matching, security checks and replies to your Privacy Policy questions. We do not need your wallet password or one-time code to investigate a receipt reference.

Cookie controls

Cookies and similar storage can remember a signed-in device path and basic preferences. You can clear site storage through your browser settings; doing so may require another phone verification before account access continues.

Account protection

We use phone verification and login activity checks to help identify unusual access. Keep your password and wallet PIN private, and contact support if a device reaches your account without your permission.

Retention approach

We keep records only as long as needed for account operation, security checks, dispute handling and legal duties. A request about retention should include your account phone number so we can assess the relevant record.

Change requests

You can ask us to correct inaccurate profile data or explain the material connected with your account. We may confirm identity through Account Verification before changing details that affect login, wallet matching or account access.

Privacy Policy Answers For Your Account

These Privacy Policy answers address the account, wallet and access questions we hear most often from Indonesian customers. If your situation involves a specific receipt, device or verification result, use the support path with the relevant reference instead of sending a password or wallet code.

It covers personal data connected with your account, including your phone number, verification status, login activity, support messages, cookies and payment references. It explains how we use those records for access, security, wallet matching and policy requests where local law permits.

Your phone number supports account creation, login checks and Account Verification. It also helps us connect a support request or DANA, OVO, GoPay or QRIS reference with the correct profile. We will not ask for your wallet PIN or one-time security code.

We use the transaction reference, status and related account details to match a payment and investigate an unclear receipt. The Privacy Policy does not require us to receive your wallet password. Send only the reference needed for the support check, with private credentials covered.

Yes. Send an access request through the signed-in account support path and include the phone number on your profile. We may complete Account Verification before sharing account-specific material, because the request must be separated from an unauthorised device or sender.

Contact support from your account and state which profile detail is inaccurate. We may ask for Account Verification before changing data tied to login, phone access or wallet matching. If access depends on local law, we will explain the applicable restriction.

Retention depends on the purpose of the record, such as account operation, security checks, payment matching, dispute handling or legal duties. Ask support about a specific record and provide your account phone number so we can assess the relevant data rather than give a generic reply.

Change your account password from a known device, avoid sharing any wallet code and contact support with the login time or device detail shown to you. We can use login activity and phone verification records to assess the access request and guide the next account step.