Reference

Privacy Policy For Your arjunasakti Account

arjunasakti Privacy Policy explains what we collect when you open an account, sign in from a phone, or connect DANA, OVO, GoPay and QRIS.

Account clarityWallet recordsCookie choicesDirect support
arjunasakti Privacy Policy For Your arjunasakti Account
CONTACT ROUTES

Where To Ask About Privacy Policy

A clear contact route matters when your account record, cookie choice or payment reference needs attention. We keep policy questions separate from general lobby requests so we can identify the right record without asking you to send a password. Include the email or phone linked to your account, the subject of your request and any relevant date. Never send a full wallet PIN or authentication code. Our support desk is available daily from 09:00 to 22:00 Western Indonesia Time through live chat and the contact form on arjunasakti.bet.

Team online

Policy contact form

Use the contact form on arjunasakti.bet for a copy of your Privacy Policy data, a correction request or a question about retention. Give us your account contact and request type; we will use that context to locate the relevant record without asking for your password.

Live chat desk

Live chat runs daily from 09:00 to 22:00 Western Indonesia Time. Choose the privacy topic when your DANA, OVO, GoPay or QRIS reference appears in a data question, and keep the receipt number ready so we can check the record efficiently.

Account access help

If a phone change or verification step blocks your policy request, tell us which device path you used and when the issue started. We can explain the next account step, but we will not ask you to disclose a login code or wallet PIN.

DATA HANDLING

What We Do With Your Account Records

Privacy Policy choices are easier to use when the handling steps are visible. We separate account identity from routine device signals where our systems allow, restrict staff access by work need and…

Account data

We collect the details you enter when creating an account and the contact used for phone verification. We use them to match you to the correct profile, respond to Privacy Policy requests and keep an access history. Do not place wallet PINs or one-time codes in support messages.

Device signals

A phone or desktop session may provide browser type, operating system, approximate network details and sign-in time. These signals help us spot unusual access and explain why a mobile session may ask for verification again. They are handled as account-security records, not as a substitute for your identity details.

Cookies

Cookies can remember language, session state and consent choices so the Privacy Policy page and account path load consistently. You can clear or block them in your browser settings. After that change, sign-in, cookie preferences or a return from QRIS may require another confirmation step.

Wallet references

A DANA, OVO, GoPay or QRIS transaction reference can be stored with account and status details needed to reconcile a receipt. We do not need your wallet PIN to trace a reference. Bank transfer and virtual account records follow the same account-matching purpose.

Security controls

We use sign-in records, verification events and access controls to reduce unauthorised account changes. If you move from a phone to desktop, we may ask you to confirm the account contact again. Tell support promptly if a device path or profile detail does not look familiar.

Retention requests

You can ask what personal records we hold, request a correction, or ask whether deletion is available for a specific record. We first verify that the request comes from the account holder. Some records may remain for security or legal duties; we will explain the reason and the applicable retention position.

Privacy Policy Answers For Indonesia

These Privacy Policy questions cover the account and device situations you are most likely to meet on arjunasakti. We explain the practical route for checking stored data, changing a contact detail, managing cookies and asking about wallet records. If your situation is not listed, contact us through live chat or the form during the stated support hours. Access and any related request remain where local law permits.

The Privacy Policy covers account details, phone verification, sign-in history, device signals, cookies, support messages and payment references. It applies when you use the mobile or desktop account path, including records linked to DANA, OVO, GoPay, QRIS, bank transfer or a virtual account.

Send a request through the contact form at arjunasakti.bet and include the email or phone connected to your account. State that you want a copy of your Privacy Policy data. We verify account ownership before responding and will not ask for your password or wallet PIN.

Yes, ask us to correct an account contact, profile detail or other personal record through live chat or the policy form. Include the existing detail and the proposed correction. We may repeat phone verification before changing the account, particularly after a device change.

It does. We may retain a DANA, OVO, GoPay or QRIS reference, account match and status needed to reconcile a receipt or investigate a stalled wallet step. The reference is not your wallet PIN. Bank transfer and virtual account records serve the same matching purpose.

Cookies can remember session state, language and your consent choice. You can clear or block them in browser settings, but the account path may ask you to confirm settings or sign in again. The Privacy Policy describes this device behaviour so you can choose how cookies work.

We keep records for the period needed for account operation, security, support handling or applicable legal duties. When a record is no longer needed, our process removes or anonymises it. If you ask about a particular record, we explain its retention reason and whether deletion can occur.

Use the contact form or live chat on arjunasakti.bet daily from 09:00 to 22:00 Western Indonesia Time. Mention the policy topic, your account contact and any relevant date or receipt reference. We can help with access, correction, cookie choices and data questions where local law permits.