Reference

argowin Privacy Policy for Your Account

argowin Privacy Policy sets out how we handle the details connected with your account, mobile browser, login, and local wallet activity.

Account clarityWallet contextCookie choicesAccess requests
argowin argowin Privacy Policy for Your Account
CONTACT PATHS

Where To Ask About Your Privacy

A clear contact route helps when you want to understand or change the data linked to your account. Send your privacy request through the account support path and include the phone number or account detail we can use to locate your record. We may ask for an account step or identity check before discussing private details, while payment receipts and wallet status questions stay connected to the cashier support route.

Team online

Account privacy request

Use the support path inside your account to ask what personal details we hold, why they are used, or how to request a correction. Include enough account context for us to find the right record.

Wallet data question

For a DANA, OVO, GoPay, or QRIS reference, include the relevant receipt or status detail without sending your full password. We use the reference to separate payment records from unrelated account activity.

Access and deletion request

Ask through account support when you want a copy, amendment, or deletion assessment. We first verify the request belongs to you, then explain any record that must remain for security or legal reasons.

DATA CONTROL

What We Do With Account Records

Your privacy choices work alongside the account steps used to protect login and wallet activity. We separate routine account data from payment references where practical, restrict internal access, and investigate unusual sign-in…

Data we receive

We may receive your account details, phone verification result, device and browser signals, support messages, login events, and payment references. The exact record depends on which account and cashier steps you complete.

Cookies on mobile

Cookies can keep your session connected and help us identify a failed page on a mobile browser. You can manage browser cookie settings, although switching them off may affect account access or saved preferences.

Account security

Phone verification and sign-in checks help us confirm account ownership before private account details are discussed. Never send your password through support, and contact us if a login or wallet status looks unfamiliar.

Payment references

We use transaction references to match cashier status with your account, not to replace the records held by DANA, OVO, GoPay, QRIS, or your bank. Each provider may apply its own privacy terms.

Retention approach

We keep records for as long as needed for account operation, security checks, dispute handling, or legal duties. When a record is no longer needed for those purposes, we assess it for removal or secure disposal.

Changes and contact

If your name, phone detail, or account record needs correction, contact us through the account support path. We may request verification, then record the request and explain the result in the same route.

Privacy Policy Answers for argowin

These Privacy Policy answers cover the questions we expect when you are checking account access, local wallet references, cookies, and data requests. If your situation is not listed, use the account support path and describe the specific record or action you need us to check.

It covers personal details, phone verification, login events, device signals, cookies, support messages, and payment references connected with your account. It also explains access, correction, retention, and contact routes.

We use your phone detail for account creation, verification, and account ownership checks. It helps us connect support requests and cashier references to the correct account without exposing private details to another person.

We handle the account-side reference needed to match DANA or QRIS activity with your cashier status. DANA, QRIS, banks, and other payment providers may keep separate records under their own privacy terms.

Use the account support path and ask for a copy of the personal details linked to your account. Include your account phone detail, complete the requested ownership check, and wait for our response route.

Yes. Send a correction request through account support and identify the detail that is wrong, such as a phone record. We may verify ownership before updating the record or explaining why it cannot change.

Retention depends on account operation, security checks, disputes, and legal duties. We assess records when those needs end and remove or securely dispose of data that no longer has a valid purpose.

Yes. Ask through account support if a cookie or mobile browser signal is affecting access. You can also adjust browser settings, but disabling cookies may interrupt your session or account preferences.