Reference

pisang777slot Privacy Policy

The pisang777slot Privacy Policy shows you what we collect when you open an account, sign in from a phone, or use DANA, OVO, GoPay and QRIS.

Account dataWallet recordsDevice choicesYour requests
pisang777slot pisang777slot Privacy Policy
DATA REQUESTS

Where To Ask About Your Data

A clear contact route matters when a record looks unfamiliar or you want to change an account detail. We keep privacy questions close to the signed-in account and cashier paths, so you can provide the reference needed for a useful response. If you are in Makassar or another Indonesian location, use the same online route rather than sending sensitive details through an unrelated channel. Access depends on local law, and we may ask for account verification before discussing personal data.

Team online

Account support path

Use the support contact route inside your account when you want to ask what personal data we hold. Include your registered contact detail and the specific correction or access request, but do not send a password or wallet security code.

Cashier data question

For a DANA, OVO, GoPay or QRIS record, start from the cashier help path and include the transaction reference shown in your account. We use that reference to locate the relevant record without asking you to repeat private wallet credentials.

Receipt and status check

If a bank transfer or virtual account receipt is attached to the wrong account detail, tell us through the support route linked to your account. We may verify ownership before changing the record, which helps prevent another person from requesting changes for you.

ACCOUNT SAFETY

Data Controls Behind Your Account

Privacy starts with practical controls rather than a long promise. We separate account details from payment references where our operating process allows, use sign-in checks before discussing account records, and explain the…

Data we receive

We may receive your account contact details, phone verification result, sign-in events, device and browser signals, support messages, and payment references. For DANA, OVO, GoPay and QRIS, we use the reference and status needed for account matching rather than requesting your wallet password.

Cookies and sessions

Cookies and similar session tools help keep your signed-in path working on a phone or desktop browser. They can remember session state and security signals, while you can clear browser data or contact us if you want help understanding a cookie linked to your account.

Account security

Before account access, we may use phone verification and account checks to confirm that the request comes from you. Keep your password and verification code private, and contact support promptly if a sign-in event or wallet status does not match your activity.

Retention choices

We keep personal data for the period needed to operate the account, resolve a payment reference, meet a legal duty or examine a security issue. When a reason ends, we remove, anonymise or restrict the record according to the process that applies.

Who you contact

Our account support route is the first place for a privacy question, correction request or data access request. Describe the record and the action you want, and we may ask for account verification before sharing details connected with your pisang777slot account.

Requesting a change

You can ask us to correct inaccurate account details, explain a data use or review a retention question through support. For wallet records, include the relevant DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference where one is shown.

Privacy Policy Questions From Indonesia

These answers focus on the questions you may have before opening an account or using the privacy contact path. They cover the records created during phone verification, mobile browsing, wallet activity and support conversations. If your situation is not listed, contact us from the account area with the smallest amount of personal detail needed to identify your request.

It covers account details, phone verification, browser and device signals, support messages, cookies, and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or a virtual account. It also explains retention, security checks and how to request correction or access.

We use the verification result to support account access and reduce the chance of an unauthorised person changing account details. We do not need your verification code in a support message. Keep that code private and contact us if a verification event seems unfamiliar.

Yes. The Privacy Policy includes browser, device and session signals created when you sign in from a phone or desktop. These signals help maintain a secure session and investigate access issues. You can clear browser data or ask support about a particular session record.

We use payment references and status details to match an account activity, investigate a receipt question and show the relevant wallet state. We do not ask you to send a wallet password. For a data request, provide the reference visible in your account.

Yes, send a correction request through the account support route and identify the detail that needs changing. We may verify your account before making an adjustment. If the request concerns a bank transfer or virtual account, include its displayed reference.

We retain records for the operational, legal, security or dispute reason that requires them. The period can differ by record type, such as account access, payment status or support contact. When the reason ends, we remove, anonymise or restrict the data where applicable.

The policy is available for you to read before using the account, but access to the service and related eligibility depends on local law. Where local law permits, we may apply extra checks or retain specific records needed for legal and security purposes.