Reference

Privacy Policy For Your Account

sadwa4d Privacy Policy explains how we handle the details connected with your account, including login records, device signals and wallet activity when you open titles such as Live…

Clear data purposesWallet record controlsAccount access support
sadwa4d Privacy Policy For Your Account
PRIVACY SUPPORT

Get Privacy Help Through Your Account

A clear support path matters when you want to ask about personal data rather than a wallet balance. Sign in, open the account help route and describe the record or policy point you want us to check. We can connect a privacy request with the right account details without asking you to post sensitive payment data in a public message. If access is unavailable, keep your payment receipt or reference ready and use the available support route when access is restored.

Team online

Account help route

Use the help path after sign-in to ask about your Privacy Policy rights, stored account details or a correction. Include the phone verification stage involved so we can separate your request from another account.

Wallet status query

For DANA, OVO, GoPay or QRIS records, send the payment reference through the account support path. We use that reference to locate the relevant status without requesting your wallet PIN or full secret credentials.

Access concern

If a phone check or sign-in session blocks a privacy request, tell us the device path and approximate time. We can first confirm account ownership, then explain the next step for your data enquiry.

DATA CONTROLS

What We Keep Secure For You

We apply the Privacy Policy to practical account events, not just a page of legal wording.

Account data

We may hold your account identifier, verified phone detail and sign-in history so we can connect the right person with the right account. These fields also help us handle a request to correct or access your records.

Payment references

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference can be used to match a wallet event. We do not need your wallet PIN to investigate a receipt, status question or account mismatch.

Cookies and sessions

Cookies can keep a mobile browser session connected to your chosen account path. You can clear browser cookies through device settings, though doing so may require phone verification again before account access continues.

Security signals

We may record device type, browser details and unusual sign-in patterns to protect account access. A new phone or changed connection can lead to an additional check before you reach the lobby.

Retention choices

We keep records for the period needed for the purpose described in the Privacy Policy or for applicable legal duties. When you ask about removal, we explain which records can be deleted and which must remain.

Change requests

To request access, correction or a permitted deletion, contact us through the account help route with enough detail to identify your account. We may ask for phone verification before changing or disclosing personal data.

Privacy Policy Questions Before Opening

These Privacy Policy answers focus on the account decisions you may make before opening access from Indonesia. We explain what connects to phone verification, how wallet references are treated, what cookies do on a mobile device and where to send a request. Eligibility still depends on local law, so check the policy and account prompts that apply to your location.

The sadwa4d Privacy Policy covers account details, phone verification, sign-in activity, device signals, cookies and payment references. It also explains how we respond to access, correction and permitted deletion requests connected with your account.

No wallet PIN should be sent through account support. The Privacy Policy concerns transaction references and account links for DANA, OVO, GoPay and QRIS, while your payment provider handles its own authentication and processing.

Phone verification helps us connect a request or sign-in with the correct account and reduce unauthorised access. Under the Privacy Policy, the verification event may be recorded so we can protect the account and handle later privacy requests.

Sign in, open the account help route and ask for access to your personal data under the Privacy Policy. Give the account phone detail and request scope; we may confirm ownership before preparing a response.

Yes, you can use the account support path to request a correction. Describe the inaccurate field, such as a phone detail or account identifier, and complete any ownership check needed before we change the record.

Cookies can remember a browser session and help keep your mobile path connected to the correct account. Clearing them may sign you out and trigger phone verification again. The Privacy Policy explains their purpose and related controls.

You may ask whether deletion is available for a particular record through account support. We assess the request against the stated purpose and applicable legal duties, then explain what can be removed, retained or corrected.