Reference

pondok969 Privacy Policy for Your Account

Our pondok969 Privacy Policy explains what we collect when you open an account, confirm your phone, browse the lobby or use DANA, OVO, GoPay and QRIS.

Account dataWallet referencesCookie choicesAccess requests
pondok969 pondok969 Privacy Policy for Your Account
HELP WITH YOUR DATA

Get Policy Help Beside Account Support

A privacy question should not get lost among wallet messages, so we keep a clear support route beside the account and cashier path. Use the available support channel when you need a copy of your account details, want to correct a phone record or need help understanding a DANA or QRIS reference. Include your account identifier and the subject of your request; we use those details to locate the right record without asking for your wallet password.

Team online

Account data request

Ask through the account support channel for the personal details linked to your pondok969 access. We may confirm your phone before sending account-related data to the matching account holder.

Wallet reference check

If a DANA, OVO, GoPay or QRIS status appears incorrectly, send the reference and time through support. We use the payment record to check the account match without requesting wallet login details.

Correction request

Tell us which account field needs changing, such as a phone detail or contact record. We may ask for an account step that confirms the request belongs to you before editing it.

OUR DATA PRACTICES

What We Do With Account Records

We keep this Privacy Policy practical by linking each data use to an account task: access, phone verification, wallet matching, security or support.

Account details

Your account contact details support login and phone verification.

Payment references

For DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity, we retain matching references and status details.

Cookies

Cookies can keep a session active and remember basic choices between account pages.

Device security

Browser, device and connection signals can be checked when sign-in behaviour looks unusual.

Retention period

We keep records while they support account access, payment reconciliation, security checks or legal duties.

Your request path

Use the account support channel to request access, correction or clarification about your data.

Answers About pondok969 Privacy Policy

These Privacy Policy answers focus on the account actions you are most likely to ask about before opening access. We explain what happens around phone verification, cookies, local wallets, device signals, retention and requests for account data. If your question concerns a record not covered here, use the support channel beside the account or cashier path and include the relevant reference.

It covers account details, phone verification, cookie use, device and connection signals, payment references, retention and requests about your records. It applies to the pondok969 service where local law permits.

No. For DANA, OVO, GoPay, QRIS, bank transfer and virtual account steps, we use matching references, status and timing details. Support should not require your wallet password.

Phone verification helps connect an account request to the correct account holder before access or a data change. It also gives support a clear account step when login records need checking.

We may handle browser, device and connection signals linked to account access. These details help investigate unusual sign-ins and session problems; they are used for account security rather than unrelated profiling.

Yes, send an access request through the account support channel with your account identifier. We may confirm your phone first, then provide the records that can be shared under applicable local requirements.

Use support and name the field that needs correction, such as a phone or contact record. We may ask for a matching account step before changing the record.

We retain records while they are needed for account access, payment matching, security checks, support or legal duties. After that need ends, handling follows the applicable retention process.