Reference

pendekar138 Privacy Policy for Your Account Data

Your account details, wallet records and device signals are handled under the pendekar138 Privacy Policy, so you can understand what we collect before opening an account.

Account clarityWallet recordsCookie choicesLocal access
pendekar138 pendekar138 Privacy Policy for Your Account Data
REQUEST HELP CLEARLY

Switch to Support for Privacy Requests

A clear support path matters when you want to ask about the Privacy Policy, correct an account detail or understand a wallet record. Use the support route connected to your account and include the phone number or receipt reference involved. We use the supplied details to locate the request without asking you to send an account password.

Team online

Policy questions

Ask through the account support route when a Privacy Policy paragraph is unclear. Include the relevant page, account phone number and a short description so we can direct your request to the right handling path.

Wallet record check

For DANA, OVO, GoPay or QRIS concerns, share the payment receipt reference rather than your wallet password. We compare that reference with the account event and explain the status connected with your data.

Account correction

If your phone or personal details need correction, request an account review through support after signing in. We may ask for a verification step before changing data tied to account access.

DATA HANDLING DETAILS

Browse How We Handle Account Privacy

We apply the Privacy Policy to practical account events rather than treating data handling as a vague promise.

Data collected

We may collect your name, phone number, verification result, login time, device type and account actions. Payment references from DANA, OVO, GoPay, QRIS or bank transfer can connect a transaction event with your account.

Cookie controls

Cookies can keep your session active and remember selected settings on a phone or desktop browser. You can manage browser cookie controls, though disabling them may affect sign-in continuity and policy-page preferences.

Account security

Phone verification is used before account access, while login and device signals help us identify unusual attempts. Never send a password or one-time code through support when asking about your Privacy Policy rights.

Retention rules

We keep records for as long as needed for the stated service purpose, account security, dispute handling or a legal requirement. When a retention reason ends, handling follows our internal deletion or removal process.

Your requests

You can ask for access to personal data, correction of inaccurate details or clarification about its use. We may verify your identity first so another person cannot request changes to your account.

Contact route

Use the support path beside your account area for privacy questions, data requests and cookie concerns. Include a useful reference, but remove passwords, wallet PINs and one-time codes before sending.

Check Common Privacy Policy Questions

These Privacy Policy answers address the account, device and payment questions you are most likely to have before opening an account. If your situation is not covered, use the account support route and describe the specific record or request without sharing secret login credentials.

The Privacy Policy covers personal details, phone verification, login activity, device signals, cookies, payment references, retention, account security and the steps for requesting access or correction.

We use payment references and status details to connect a DANA or QRIS event with your account. You should never send a wallet password, PIN or one-time code to support.

Device type, browser signals and login events can help us recognise unusual access and protect your account. These signals also help maintain a working session on your phone or desktop.

Use the account support route and ask for a personal data access request. Include your account phone number and the records you mean; we may complete an identity check first.

Yes, you can request correction of inaccurate personal details through support. We may ask you to complete phone verification before changing data that controls account access or wallet matching.

Retention depends on the purpose of each record, account security needs, dispute handling and legal requirements. When those reasons end, we follow the applicable removal or deletion process.

Contact us through the support path connected with your account and specify cookies, stored data or a Privacy Policy question. Access to services depends on local law and your location.