Reference

villa66 Privacy Policy For Your Account

villa66 Privacy Policy explains what we collect when you open an account, sign in from a phone or desktop, and use wallet routes such as DANA, OVO, GoPay…

Account clarityWallet recordsYour privacy choices
villa66 villa66 Privacy Policy For Your Account
HELP WITH PRIVACY

Where To Ask About Your Data

A clear contact path helps you resolve a Privacy Policy question without guessing which team to reach.

Account data request Use the support route inside your account to ask which personal details we hold. Tell us whether your request concerns registration, phone verification, sign-in activity or a DANA, OVO, GoPay or QRIS reference.
Payment record question If a bank transfer or virtual account entry looks unfamiliar, send its date, amount and reference through support. We use those fields to locate the record without asking you to reveal a password or wallet PIN.
Access and correction When you cannot reach the account, explain the device path you used and the change you need. We may ask for account details before correcting data, especially where a phone verification record protects access.
DATA HANDLING

How We Keep Policy Practical

Privacy Policy choices should fit the way you actually use the account, whether you sign in on a mobile browser for QRIS or return on desktop to check a payment record.

Account details

We collect details such as your contact information and verification status when you open an account. These records help us connect a sign-in request to the correct account and prevent an unauthorised change to your phone or wallet path.

Device signals

A phone or desktop session can create technical signals such as browser, device and sign-in time details. We use them to identify unusual access patterns and investigate why your account path may have stalled.

Cookies

Cookies can keep a session active and preserve selected settings while you move between account pages. Your browser controls these files, so you can clear or restrict them, although some account steps may then need to be repeated.

Wallet security

DANA, OVO, GoPay and QRIS references are used to match payment status with the account action you made. We do not need your wallet PIN for a support request, and you should not place that secret in a message.

Retention period

We keep account, payment and security records only for the operational, dispute and legal reasons described in this Privacy Policy. When a record is no longer needed, our process removes it or separates it from direct account identity.

Policy changes

If this Privacy Policy changes in a way that affects your account choices, we will place the updated wording on this page. You can contact support to ask what changed, request a copy, or question a data decision.

Privacy Policy Answers For villa66

These Privacy Policy answers focus on the account actions you are most likely to take from Indonesia. We explain the records behind sign-in, phone verification, cookies and wallet status in direct terms, so you can decide what to share before opening an account. If your question is personal to your account, use the support path and include only the minimum details needed to locate it.

The villa66 Privacy Policy covers account details, phone verification, device signals, cookies, payment references and support messages. It explains why we use each category, how long selected records may remain, and how you can ask for access, correction or removal where local law permits.

We do not need your DANA, OVO, GoPay or QRIS PIN for ordinary account support. Payment references and status details may be linked to your account action, but you should never send a wallet PIN, password or one-time security code through a support message.

Phone verification connects an account action to the contact detail you provided and can protect sensitive changes. We may use its status when checking account access or correcting records. If the phone number is no longer yours, contact support and explain the required change.

We use cookies and similar browser storage to maintain a sign-in session and preserve selected settings. You can clear or restrict them in your browser. If you do, some account pages may ask you to sign in again or repeat a verification step.

Yes, send a data request through the account support route and identify the account with its attached email or phone detail. We may verify ownership before responding. The records available to you depend on applicable obligations and where local law permits.

We retain payment and account records for the operational, security, dispute and legal reasons described in this Privacy Policy. A bank transfer, virtual account, DANA or QRIS reference may remain after a session closes, then be removed or anonymised when no longer needed.

You can request a correction through support, stating which detail is wrong and what it should say. For a phone number or verification record, we may ask for an account check before changing it. We will explain any limit that depends on local law.