Reference

arjuna4d Privacy Policy Explained

Our Privacy Policy explains what we collect when you create an account, verify your phone, browse Sic Bo or Aviator, and use DANA, OVO, GoPay or QRIS.

Account dataWallet recordsCookie choicesRequest access
arjuna4d arjuna4d Privacy Policy Explained
REQUEST HELP DIRECTLY

Account Help For Privacy Requests

A clear contact route matters when a phone number, wallet reference or cookie choice needs attention.

Account request Use the account support path to ask for a copy, correction or clarification.
Wallet record For DANA, OVO, GoPay, QRIS, bank transfer or virtual account questions, name the payment…
Access concern If a mobile sign-in or phone verification looks unfamiliar, report the account step through…
HOW WE HANDLE DATA

Cookies, Devices And Wallet Security

Privacy choices work best when they match the way you actually use your account. We separate sign-in details, payment references and device signals so a support request can be checked without exposing…

Account details

We collect the details needed for account creation and phone verification. Your registered phone number helps us connect sign-in activity, support requests and account changes to the correct record.

Payment references

We retain transaction identifiers for DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity. These references help us check receipt or status questions without storing your wallet PIN.

Cookies

Cookies can keep a signed-in session working and remember selected settings. You can manage cookies in your phone browser, although restricting them may affect account access and policy controls.

Device signals

A mobile phone or computer may provide browser, session and security signals during sign-in. We use them to spot unusual access, not to ask for private content stored on your device.

Retention period

We keep records only for the period needed for account operations, security checks, support questions and applicable legal duties. Ask support which record category and retention reason applies.

Change request

You may request access, correction or deletion where applicable. Send the request through account support with enough detail for verification, and we will explain any legal or security reason for limits.

Privacy Policy Questions For arjuna4d

These answers address the questions you may have before opening an account or using a local wallet. They cover the records connected with sign-in, payments, cookies and support. If your question concerns a specific transaction or device, include that detail when you contact us so the request can be checked accurately.

It covers account details, phone verification, device signals, cookies, payment references and support requests connected with your use of arjuna4d, including activity involving DANA, OVO, GoPay and QRIS.

We use your phone number to create and verify account access, connect you with the correct support record and investigate an unfamiliar sign-in. Keep the number current so requests can be checked.

Yes. The Privacy Policy covers QRIS, DANA, OVO, GoPay, bank transfer and virtual account references used to trace payment status. We do not need your wallet PIN for that check.

Open the signed-in account support path and request access to your data. State the record type you need, such as account, device or payment details, and complete the identity check.

Yes. Send a correction request through account support and identify the inaccurate field, such as your phone number or account name. We may verify the request before changing the record.

Cookies may keep your session and selected settings available. You can adjust them in your mobile browser, but blocking necessary cookies may interrupt sign-in, phone verification or policy preference controls.

Account access and eligibility depends on local law. The Privacy Policy explains our data handling for supported use, but it does not change the laws that apply where you live.