Reference

buku mimpi 2d Privacy Policy

buku mimpi 2d Privacy Policy explains what we collect when you open an account, sign in, check DANA or QRIS status, and contact our support path.

Account dataCookie choicesPayment referencesSupport requests
buku mimpi 2d buku mimpi 2d Privacy Policy
ACCOUNT HELP PATH

Privacy Help For Account Access

A clear support route matters when you want to ask about your personal data rather than a lobby title.

Account request Use the support path attached to your account to ask for a copy, correction or explanation of personal data. We may ask you to complete phone verification before discussing account records, so a request is not disclosed to the wrong person.
Payment reference For DANA, OVO, GoPay, QRIS, bank transfer or virtual account questions, share the transaction reference and date only. We use those details to locate a status record without asking for your wallet PIN, card secret or full banking password.
Access concern If a login or device check blocks your privacy request, tell us the account contact and device type through the support channel. We can explain the next verification step while keeping sensitive credentials out of chat and account messages.
SIX DATA CHECKS

Six Checks Behind Your Data

We handle privacy through practical checks rather than vague promises. The account path records the details needed for access, the cashier path keeps payment references separate from wallet secrets, and device signals…

Account collection

We collect details you enter during account creation and phone verification, plus sign-in records needed to keep access working. Fields that are not needed for an identified account purpose should not be placed in support messages or payment references.

Cookie controls

Cookies can remember a session, language setting or security preference on the device you use. Your browser can block or clear them, although removing session cookies may require you to sign in again before reaching the lobby.

Device signals

Browser type, operating system and related security signals may be checked when an account signs in. A change from mobile to desktop, including a connection from Bandung, can trigger an extra account check without revealing your wallet credentials.

Payment separation

DANA, OVO, GoPay and QRIS references are used to match a cashier event with its status. Bank transfer and virtual account records serve the same reconciliation purpose, while wallet PINs and banking passwords remain outside our requested support data.

Account security

Phone verification and sign-in checks help us confirm that an account request comes from the account holder. We will not ask you to place a password, wallet PIN or one-time secret in a support message when investigating access.

Retention requests

Records are kept for the period connected with account operation, payment reconciliation, disputes or legal duties. You may contact us to ask what remains, request a correction or seek deletion where local law permits and no valid retention duty applies.

Privacy Policy Questions For Your Account

These Privacy Policy answers focus on the account actions you are most likely to take before opening access or while checking a record. We explain the practical route for Indonesian payments, device use, cookie choices and data requests. If your question depends on eligibility or a local restriction, the answer depends on local law and the terms that apply to your account.

The Privacy Policy covers account details, phone verification, sign-in and device signals, cookies, support messages, and payment references from DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity. It also explains retention, security checks and how to request access or correction.

Phone verification helps us connect an account request with the person opening or recovering that account. We use the result as an access and security check, not as permission to request your wallet PIN. Extra steps may apply where local law permits account access.

No. Our Privacy Policy describes the use of payment references and status details, such as a DANA receipt or QRIS transaction code. We do not ask you to send a wallet password, PIN or one-time secret through support when checking a cashier record.

You can clear or block cookies through your browser settings on the mobile or desktop device used for account access. Session cookies may be required to keep you signed in, so changing the setting can send you back to phone verification before the lobby opens.

Yes, contact the account support path and ask for a data copy. Include the account contact needed for identity checking, but leave out passwords and wallet secrets. We process access requests according to the Privacy Policy and applicable local law.

Send a correction request through the support channel linked to your account and state which detail is inaccurate. We may confirm your identity by phone verification before changing it. Payment references can require a separate reconciliation check before correction.

You may request removal of eligible data through support where local law permits. Some records may remain for account security, payment reconciliation, disputes or legal duties. We will explain which category applies rather than removing a record that must be retained.