Reference

pondok88 Privacy Policy For Your Account

Our Privacy Policy explains how pondok88 handles the details you provide when you open an account, use the lobby, or check a wallet status.

Clear data purposesWallet detail controlsAccount access requestsCookie choice path
pondok88 pondok88 Privacy Policy For Your Account
CONTACT DATA CARE

Three Ways To Ask About Privacy

A clear contact route helps you act on this Privacy Policy without searching through the lobby.

Account support link When you can sign in, open the support link in your account area and choose the privacy request path. Include the account email or verified phone so we can locate the correct record without asking you to share a password or wallet PIN.
Cashier detail check If your question concerns DANA, OVO, GoPay, QRIS, bank transfer, or a virtual account reference, tell us the date and visible transaction label. Keep the full wallet number and banking credentials private; we only need enough context to trace the record.
Access recovery route If a sign-in problem blocks your privacy request, use the support contact displayed on the site and state that you need account-data help. We may ask for a verification step before discussing records, which protects your account from an unapproved request.
DATA HANDLING RULES

Six Practical Privacy Commitments

Privacy choices matter most when they fit the way you actually use an account. Our handling process separates sign-in details, support messages, device signals, and payment references so each request has a…

Account details

We use your name, contact details, phone verification status, and sign-in record to create and protect your account. The clear account path helps us distinguish your request from another person’s request, especially when you ask to change or access personal details.

Payment references

A DANA, OVO, GoPay, QRIS, bank transfer, or virtual account reference can be used to match a cashier event with your account. We do not need your wallet PIN or full banking password for a privacy request or payment-status check.

Device and cookies

Our mobile website may store cookies or device signals that keep a session working, remember a selected setting, or help identify repeated failed sign-ins. You can control cookies through your browser settings, though some account functions may then require another sign-in.

Security checks

Before we disclose account data or change a verified contact detail, we may ask for a phone or account check. This step is part of our privacy process and helps prevent a person with access to your device from taking over the account.

Retention periods

We retain account, support, and transaction records only for the period needed for account operation, security checks, dispute handling, or a legal requirement that depends on local law. When a record is no longer needed, our process removes or separates it.

Changes and requests

You can ask us to correct inaccurate data, explain how a record is used, or request deletion where local law permits. Send the request through account support, identify the relevant record, and complete verification before we discuss or change it.

Privacy Policy Answers For Indonesia

These Privacy Policy answers cover the questions we expect you to ask before opening an account or while using pondok88 from Indonesia. Each answer points to an account step, a payment reference, a device setting, or a support route so you know what to do next. If your situation is different, contact us through the privacy path and mention the specific record or access issue.

The pondok88 Privacy Policy covers account creation, phone verification, sign-in activity, support messages, cookies, device signals, and payment references. It explains why we use each category, how we protect account access, and how you can request correction, access, or deletion where local law permits.

Phone verification helps us confirm that the account request comes from you and supports safer recovery when a sign-in issue occurs. We may use the verified status before discussing personal records or changing account details, but you should never send us your phone PIN.

We use visible DANA or QRIS references to match a cashier event with the correct account and answer a payment-status question. We do not need your wallet PIN. For a data request, provide the date and displayed reference rather than sending a full wallet credential.

Yes, you can request access to personal account data through the signed-in support link or the public support contact shown on our site. Include your linked email or verified phone, describe the records requested, and complete the identity check before we release details.

We keep records for the time needed to operate the account, investigate security events, resolve payment questions, handle disputes, or meet a requirement where local law permits. The exact period can depend on the record type; support can explain the reason for a particular record.

Open the account support link, identify the incorrect name, contact detail, or verification record, and request a correction. We may verify your phone or account before making the change. Do not include a password, wallet PIN, or full bank credential in the message.

You may request deletion through the privacy support route, and we assess it where local law permits. Some account, transaction, or security records may need temporary retention for a stated operational or legal reason. We will explain that reason and the next available step.