LEGAL REFERENCE

Privacy Policy For Your Account

Privacy controls for Indonesia account flow: we explain what data we collect, why we use it and how your DANA, OVO, GoPay and QRIS references stay limited to...

Indonesia privacyAccount dataQRIS contextE-wallet care
zona gacor Privacy Policy For Your Account

How We Handle Your Privacy

Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.

HELP CHANNELS

Privacy Contact Paths

If you have a privacy question, ask us through the same account space you use for the lobby. Keep your message specific...

Live chat privacy desk Use live chat when you need quick routing...
Email request channel Email works well for access copies, correction requests...
Account message centre Your account message centre lets us keep privacy...
WHY VISITORS TRUST US

Policy Care Signals

We keep this policy written in plain English for Indonesia, then align it with the actual account screens you see. When we change data use, retention periods or partner roles, we update...

Plain-language drafting

We avoid legal noise where possible and explain each data use in account terms. You can see why we ask for details before you decide to continue.

Data purpose mapping

Each personal data category links to a purpose, such as account access, security checks, support replies or payment reference matching. This makes our privacy flow easier to audit.

Limited partner sharing

We share only what a service partner needs to perform a specific task for us. Partner access is kept narrow and tied to support, security or processing roles.

Retention checkpoints

We keep records only as long as needed for account operation, dispute handling, security checks or legal duties. When the reason ends, we archive or delete data.

Change logging

Policy changes are checked against account pages, consent prompts and support scripts. This keeps privacy wording consistent from the first visit to ongoing account use.

Indonesia context

We include DANA, OVO, GoPay and QRIS references because you may use them in supported regions. They appear only where privacy handling needs local context.

Consistency Across Policy Pages

Our privacy wording lines up with the other policy pages connected to your account. That means the same definitions, contact steps and data handling language appear wherever privacy...

Terms alignmentOur terms describe account rules, while this policy explains data handling behind those rules. We keep both pages consistent so your rights and obligations are not split awkwardly.
Cookie alignmentCookie choices connect to this policy because browser data can identify devices and sessions. We explain that link without turning cookie settings into a separate account promise.
Promo page alignmentPromotion screens may use account preferences and eligibility checks. This policy explains the data side, while promo terms explain the offer rules shown on your account.
Security notice alignmentSecurity notices may mention login alerts, device checks and suspicious activity flags. This policy explains what personal data supports those alerts and how we limit use.
Payment context alignmentDANA, OVO, GoPay and QRIS references may appear in account records. This policy explains privacy handling, not wallet balances or bank-side processing outside our control.
Support script alignmentSupport teams follow the same privacy wording you read here. When you ask for access, correction or deletion, the response path should match this policy.
Update timing alignmentWhen another policy changes data handling language, we check this page too. That keeps privacy meaning stable across your account journey and reduces mixed messages.
SERVICE CONTEXT

Privacy Page Layout Highlights

This page is arranged to help you scan privacy choices quickly before opening or managing an account. We separate collection, use, sharing, retention and contact paths, then show...

Quick badge row The badge row flags account privacy themes before long text...
Short policy blocks Each block focuses on one privacy action, such as collection...
Local context chips DANA, OVO, GoPay and QRIS appear as context chips, not...
Contact cards Contact cards show where to ask privacy questions and what...
Change cues Update cues help you notice when privacy wording changes. If...
FAQ placement The FAQ sits near the end so quick answers stay...

Privacy Policy Questions

We collect account details, contact data, device signals, session records, support messages and transaction references needed to operate your account, protect access and answer requests. We avoid collecting data that is not relevant.

We may keep payment references to match account activity, resolve disputes and support reconciliation in supported regions. We do not need your wallet PIN, password or private banking credentials for this process.

Yes. Contact us through live chat, email or the account message centre and ask for access. We will verify your account first, then explain what data we can provide.

Yes. If your contact details or profile data are wrong, send a correction request through a support path. We may ask for verification before changing records linked to security or payments.

We keep data while your account is active and as needed for security checks, disputes, legal duties or support records. When those reasons no longer apply, we delete or archive data.

We share limited data with partners that help us run hosting, security checks, account support and payment reference matching. Each partner should use the data only for the task we assign.

We update this page when our privacy handling changes in a meaningful way. If the change affects your account choices, we aim to make the wording clear before you continue using the service.