Reference

janji gacor Privacy Policy for Indonesia

Our Privacy Policy explains what we collect when you open an account, sign in from a mobile device, or use DANA and QRIS for account funding.

Clear data purposesWallet record contextAccount request path
janji gacor janji gacor Privacy Policy for Indonesia
CONTACT OPTIONS

Where Privacy Questions Go

A clear contact path helps you resolve a privacy question without sending sensitive details through an unrelated channel.

Account support Ask about a Privacy Policy point through the account support path.
Wallet records For DANA, OVO, GoPay, QRIS, or bank transfer questions, provide the transaction reference and…
Correction request Request a correction when your account name, contact detail, or verification record is inaccurate.
DATA CONTROLS

Six Practical Privacy Safeguards

Privacy works best when each account action has a defined data purpose. We separate contact details, device signals, wallet references, and support messages so a request can be checked in context.

Purpose limits

We collect account and verification details to create, protect, and maintain your account. Wallet references from DANA or QRIS help us match a requested transaction, rather than exposing your wallet credentials.

Cookie choices

Cookies can remember a sign-in state and support page preferences. Browser controls let you clear them, although removing necessary cookies may require you to repeat the account access step.

Device signals

A phone or desktop browser may send technical signals such as browser type, session time, and security events. We use these signals to identify unusual account access, not to request your device passcode.

Account protection

Phone verification can come before account access, while passwords and wallet PINs remain yours to keep private. If a sign-in looks unusual, support may ask for account details without asking for your password.

Retention timing

We retain account, transaction, and support records for the period needed for the stated purpose, account security, or a legal requirement. A deletion request may be limited where a record must still be retained.

Change requests

You can ask us to correct personal details, explain a stored record, or request deletion where applicable. Send the request through account support and identify the specific field or record in question.

Privacy Policy Answers for Your Account

These Privacy Policy answers focus on the records you create through account access, wallet selection, device use, and support. If your situation is not covered, contact us through the account support path with the smallest useful set of details.

It covers account details, phone verification, device and browser signals, cookies, wallet references, transaction status, and support messages connected with your account. Access remains where local law permits.

We keep a transaction reference, selected rail, date, and status so a requested account transaction can be matched and checked. We do not need your DANA or QRIS password for that purpose.

Yes. Use the account support path and name the inaccurate field, such as a contact detail or verification record. We may confirm an account step before applying the correction.

Cookies may preserve a sign-in state or page setting during your browser session. You can clear or restrict them in your browser, but necessary account steps may then need to be repeated.

We may receive browser type, session timing, and security signals from a phone, tablet, or desktop browser. These details help assess unusual access and are not your device passcode.

Retention depends on the data purpose, account security needs, and applicable legal requirements. You may request clarification or deletion where applicable, although some transaction records may need to remain.

You can send a deletion request through account support and identify the relevant account record. We assess the request against security and legal retention needs, with access depending on local law.