Reference

Privacy Policy For Your post66 Account

post66 Privacy Policy sets out how we collect, use and protect details linked to your account, wallet activity and device access.

Clear data purposesWallet activity explainedAccount access stepsContact path included
post66 Privacy Policy For Your post66 Account
PRIVACY HELP DESK

Where To Ask About Your Data

A direct support request gives you a practical route when your Privacy Policy question concerns an account, device or wallet record. Sign in first where possible, then use the support path connected with your account so we can match the request to the right profile. If login stalls, include the phone number used for verification and the payment reference, not your wallet password or one-time code. We handle requests in English for the Indonesian service and explain any identity check before taking action.

Team online

Account request

Ask us to access, correct or clarify personal details held against your post66 account. Include your verified phone number and the exact change you want, so we can check ownership before editing a profile record.

Wallet record

For DANA, OVO, GoPay, QRIS, bank transfer or virtual account questions, send the transaction reference shown in your account. We can explain the record we hold without asking you to disclose a wallet password or verification code.

Device access

If a mobile browser or desktop sign-in looks unfamiliar, tell us the device type, approximate access time and account phone number. We use those details to review the sign-in context and explain the next account-security step.

DATA CONTROL DETAILS

What We Do With Account Data

Privacy Policy choices are easier to use when each data practice has a clear purpose. We separate account access, payment records, device signals and support conversations so a request can be handled…

Collection

We collect details needed for account creation, including your contact information and phone verification result. When you use the lobby or account area, we may also receive activity linked to the selected service, such as Live Casino or a slot room.

Payment records

Our records can contain a payment method, amount status, reference and time for DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. We do not need your wallet password to match a payment record with your account.

Cookies

Cookies and similar browser storage can keep a session active, remember selected settings and help us identify a device during sign-in. You can manage browser storage through your device settings, although removing it may require another account login.

Account security

Phone verification helps connect account access to the contact detail you supplied. We may compare sign-in context, device signals and account events when activity appears unusual, then ask for an account check before changing sensitive details.

Retention

We keep personal data and transaction records only for the period needed for account operation, dispute handling, security checks or a legal obligation. When a record is no longer needed for those purposes, we seek to remove or de-identify it.

Your request

You can ask what personal data we hold, request a correction, or ask about deletion where local law permits. Contact support from the verified account path when available; we may request identity details before completing the change.

Privacy Policy Answers For Indonesia

The questions below address the searches we most often expect before an account is opened or a wallet is connected. Each answer relates to the post66 Privacy Policy rather than general lobby use. If your situation involves a specific DANA, OVO, GoPay, QRIS or bank transfer reference, keep that reference ready when contacting support. We will explain the applicable account check and whether a request can be completed under local requirements.

The post66 Privacy Policy covers account details, phone verification, device and browser signals, support messages, cookies, and payment records connected with your account. It explains why we use each category, how long records may remain, and how you can ask about access or correction.

Phone verification helps us confirm that an account request belongs to the person controlling the supplied contact number. We use the result for account access and security checks, not as permission to request your DANA, OVO, GoPay or QRIS password.

No. Our Privacy Policy distinguishes payment references from private wallet credentials. A record may show that DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity was linked to your account, but you should never send us a wallet password or one-time code.

Cookies can preserve a sign-in session, remember settings and help us recognise the browser used for account access. You can remove or restrict them through your mobile or desktop browser. After removal, the account path may ask you to sign in and verify again.

Yes, you can contact us to ask for a correction where local law permits. Use the verified account path when you can, name the field that is wrong, and provide the phone number connected with the account. We may check ownership before changing the record.

We retain account and payment records for the period needed to operate the account, investigate disputes, protect access or meet a legal obligation. The period can differ by record type. Ask support about a particular reference if you need a clearer retention explanation.

You may ask for deletion of personal data where local law permits, but some records can need to remain for security, dispute handling or a legal obligation. Contact support from your verified account path and we will explain which parts can be removed.