Reference

Open the arjunasakti Privacy Policy

Your account details, wallet records and device activity are covered in the arjunasakti Privacy Policy, so you can understand what we collect before opening an account.

Account clarityWallet recordsMobile accessPolicy contact
arjunasakti Open the arjunasakti Privacy Policy
CONTACT ROUTES

Reach us about privacy questions

A clear contact route helps you correct a detail, ask how a record was obtained or request a copy of information linked to your account. We ask you to contact us through the support path shown on arjunasakti, using the same account phone number where possible. That lets us compare your request with the phone verification step without exposing account data to an unrelated sender.

Team online

Account support

Use the account support chat when a phone number, verification result or login record looks wrong. We will ask for the account identifier and may request a confirmation through your verified phone before discussing personal data.

Wallet questions

For a DANA, OVO, GoPay or QRIS reference, include the receipt time and the last visible transaction detail. Do not send a wallet password or full banking credential; our team only needs enough information to locate the record.

Privacy request

Send a written privacy request through the contact address shown in our support area when you need correction, access or deletion guidance. We will confirm ownership first and explain any record that must remain for account or transaction reasons.

DATA PRACTICE

Explore our account data controls

We keep this policy practical by connecting each data category with an account action you recognise.

Account details

We use your phone number and submitted account details to create your profile, complete phone verification and help recover access. Check the account settings path from the mobile menu if a contact detail changes, then ask support to confirm the correction.

Wallet matching

A DANA, OVO, GoPay or QRIS transaction can create a reference, amount, status and time record. We use those fields to match a receipt with your account, rather than asking us to store your wallet password or private wallet access code.

Cookies

Cookies and related device storage can keep your session active, remember a language choice and help us see whether a login page loads correctly. You can clear them in your browser settings, though clearing session data may require another account login.

Device security

We may record device type, browser signals, approximate access time and security events to identify unusual sign-ins. A mobile browser opening the lobby after phone verification can therefore produce a different security record from your usual desktop session.

Retention periods

We retain account, security and transaction records only for the period needed for the stated purpose, account administration or a legal obligation. When a record no longer has a valid reason to remain, our process removes it or separates it from direct account identification.

Your requests

You can ask us to access, correct or delete personal data, subject to identity checks and records we must keep. Contact support with the account phone number and request type; we will explain the next step, scope and any reason a change cannot be completed.

Browse Privacy Policy answers

These Privacy Policy answers address the account, device and wallet questions we hear most often from people considering arjunasakti in Indonesia. If your situation is different, use the support route rather than sending sensitive credentials in chat. Eligibility and any request outcome depend on local law and the records connected with your account.

It covers account details, phone verification, login and device signals, cookies, support messages, and transaction references for DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity. It also explains why we use each category, how long records may remain and how to contact us.

We use your phone number to create and identify the account, complete the phone verification step and help protect access. If the number is incorrect, open account settings from your mobile browser or desktop session and contact support before requesting a correction.

The policy describes transaction references such as status, time and matching details for DANA or QRIS activity. We do not need your wallet password for that purpose. Never place a wallet password, banking PIN or full credential in a support message.

Use the privacy contact route shown in our support area and state that you want an account data copy. Include the verified phone number or account identifier, but not a password. We confirm ownership first, then explain the data scope and the available delivery step.

Yes, you can ask for correction or deletion through support. We verify that you control the account and assess whether a record must remain for security, transaction handling or a legal obligation. The Privacy Policy explains the reason and next step if removal is limited.

We may collect device type, browser signals, access time, session data and security events linked to a login. This helps us identify unusual access and diagnose a mobile path from phone verification to the lobby. Browser cookie controls let you clear local session data.

Start with the support chat or written contact address displayed on arjunasakti. Mention the request type and the account phone number so we can route it correctly. Do not send wallet credentials. Access, eligibility and the response to a request depend on local law.