Reference

Privacy Policy For Your Account

petani 303 slot Privacy Policy explains what we collect when you open an account, use DANA or QRIS, and move between the lobby and cashier.

Account clarityWallet recordsDevice controlsContact rights
petani 303 slot Privacy Policy For Your Account
CONTACT THE DESK

Three Ways To Ask About Privacy

Questions about our Privacy Policy should reach the same support path used for account access, because that lets us confirm the right account without exposing personal details. Use the on-site chat for a quick question, the account help route when a data request needs checking, or the cashier status path when a payment record is part of your request. We answer through the support hours shown in our contact panel and keep the request tied to your verified account.

Team online

On-site chat

Ask how we use login, device or cookie data through the chat panel. We may ask for your account phone verification before discussing account-specific records, and we will not ask you to send a full wallet password or security code.

Account help

Use account help to request a copy, correction or removal of personal data where that option applies. Include the phone number linked to your account and the change you want, so our team can match the request without collecting another identity document.

Cashier status

When your privacy question concerns DANA, OVO, GoPay, QRIS or a bank transfer receipt, use the cashier status path. Share the transaction reference rather than your wallet password; we use the reference to locate the relevant payment record.

SIX DATA PROMISES

Six Practical Privacy Controls

We apply the Privacy Policy through account routines you can recognise: phone verification before account access, controlled session records and a clear route for data requests.

Collected data

We collect account details you submit, phone verification results, session activity, device signals and cashier references. The Privacy Policy separates data needed to provide account access from optional preferences, so you can understand why each record exists.

Cookie purpose

Cookies help keep your signed-in session working and remember selected device settings. You can clear browser cookies, but doing so may sign you out and remove stored preferences; our policy does not treat cookie clearing as an account deletion request.

Account security

Phone verification is checked before account access, while sign-in time, browser type and unusual session changes can support security checks. We do not ask for your wallet PIN, one-time code or full password through on-site chat.

Retention period

We keep account, cashier and security records while they serve access, dispute handling or legal needs. When a record no longer has one of those purposes, we remove it or reduce its connection to your account.

Correction requests

If your phone, account name or contact detail is wrong, contact account help with the requested correction. We may verify ownership before changing the record, and we explain any field that cannot be changed while a payment check remains open.

Policy contact

Send Privacy Policy questions through on-site chat or the account help route shown in our contact panel. For a request involving DANA, QRIS or another rail, add the reference number and never include wallet credentials.

Privacy Policy Answers For Indonesia

These Privacy Policy answers address the account and device questions we hear before access begins. We explain what happens around phone verification, cookies, payment references, correction requests and account closure in plain terms. If your case involves a specific receipt or sign-in event, use the support route above and provide only the reference needed to locate that record.

The petani 303 slot Privacy Policy covers account details, phone verification, sign-in sessions, device signals, cookies, cashier references and support requests. It also explains how we use these records for access, security, payment matching, dispute handling and lawful retention where local law permits.

Phone verification helps us connect a sign-in request to the account holder and reduce mistaken access. We record the verification result rather than asking support to receive your private code. If verification fails, contact account help through the on-site route shown in our contact panel.

Yes. Our Privacy Policy covers the payment rail you select and the reference, amount status and account link needed to check a cashier event. We do not need your wallet password or PIN. For a mismatch, send the transaction reference through cashier status support.

You can request a correction through account help, including for a phone number or contact detail. Tell us which field is wrong and provide the account phone number for verification. We may delay a change while an open payment or security check must be completed.

Cookies support sign-in sessions and device preferences; they do not replace your account rights under the Privacy Policy. Clearing them can sign you out and remove preferences. To ask about a stored record or request a change, contact us through on-site chat.

We keep data while it is needed for account access, cashier matching, security checks, disputes or legal duties. After that purpose ends, we remove the record or reduce its link to you. The exact period can depend on the record type and local law.

Start with account help and state that you want a data removal request under the Privacy Policy. We verify account ownership before acting, explain any records that must remain for an open dispute or legal duty, and confirm the result through the contact route.