Reference

asupan55 Privacy Policy For Your Account

The asupan55 Privacy Policy explains what account, device and wallet details we collect when you open an account, sign in and use our services where local law permits.

Account dataWallet recordsCookie choicesContact requests
asupan55 asupan55 Privacy Policy For Your Account
CONTACT YOUR WAY

Get Privacy Help Before Changing Details

A clear contact path helps you act on the Privacy Policy without guessing which account detail matters. When you ask about stored data, include the phone or account identifier used during registration, but do not send your password or wallet PIN. We may ask for reasonable account checks before discussing private records. Our support route can also connect a payment receipt or status question to the correct account case, including when you are using a mobile browser from Makassar.

Team online

Account data request

Ask us what personal details are connected to your asupan55 account and why they are used. Include your registered phone identifier so we can locate the correct record, then complete any account check we request before private data is disclosed.

Wallet record question

If a DANA, OVO, GoPay or QRIS reference appears in a privacy question, send the transaction reference through our account support path. We use that detail to separate wallet status records from unrelated account activity and reduce mistaken disclosures.

Correction or deletion

Tell us which account field, cookie choice or contact record you want changed. We assess the request under the Privacy Policy and local requirements, explain any retention reason, and confirm the next step through the account contact route you provide.

DATA HANDLING

What We Do With Your Account Details

Privacy decisions should be visible in the ordinary account flow, so we describe the practical points here rather than hiding them behind broad wording.

Account information

Registration can involve your phone identifier and account credentials. We use those details to provide account access, respond to account-specific requests and maintain a record of your choices. Do not share your password with support; we will not need it to handle a Privacy Policy request.

Payment references

A wallet or bank transaction can leave a reference, amount, status and timestamp connected to your account case. DANA, OVO, GoPay, QRIS, BCA, BRI, Mandiri and BNI may appear in the payment context you provide, while we use the record for reconciliation and support.

Cookies and storage

Cookies or similar browser storage can remember a session state, language choice or security signal. You can manage browser settings on your mobile or desktop path, although removing necessary storage may sign you out or require phone verification during the next account access.

Device security signals

We may process device, browser and connection signals when you sign in so we can identify unusual access patterns. These signals are used for account protection and investigation, not as a reason to request your wallet PIN or password through an unsolicited message.

Retention decisions

We keep account, support and transaction records only while they serve the purposes described in the Privacy Policy or a required legal, security or dispute process. When a retention need ends, we review the record for deletion, aggregation or restricted storage.

Your policy choices

You can contact us to request access, correction, restriction or deletion where the applicable rules provide that option. We may need to verify account ownership first, and we will explain if a record must remain because it supports security, payment reconciliation or a legal obligation.

Privacy Policy Answers For asupan55

These Privacy Policy answers address the account questions you are most likely to have before opening access or connecting a local wallet. They cover the data collected during registration, the records created by payment activity, browser choices, account security and requests sent to support. If your situation is not listed, use the contact path in this policy and give us enough account context to respond without exposing details to the wrong person.

The asupan55 Privacy Policy covers personal and account details processed when you register, sign in, contact support, use cookies or connect payment activity. It explains purposes, security steps, retention and your request options where local law permits, including access or correction of information linked to your account.

We may collect the phone identifier and credentials needed for the account path, plus device or browser signals used for access security. If you contact us, the conversation and account references can be retained to resolve the request. We do not need your password or wallet PIN for support.

Yes. When you use DANA, OVO, GoPay or QRIS, the connected account case can include a transaction reference, status, timestamp and related payment context. Bank transfer or virtual account activity can create similar records. We use them to reconcile status, investigate disputes and answer privacy questions.

You can contact us with the phone or account identifier used during registration and describe the data request. We may verify ownership before sharing private records. If a field is wrong, explain the correction; we will assess it under the Privacy Policy and applicable local requirements.

Cookies or browser storage can preserve a sign-in session, remember a choice or support a security check on mobile and desktop. You can manage them through your browser controls. Removing necessary storage may sign you out, clear a preference or trigger phone verification during the next access.

We retain account, support and payment reference records while they serve the purposes in the Privacy Policy or while security, dispute handling, reconciliation or legal duties require them. After that need ends, we review the record for deletion, anonymisation or restricted retention under applicable rules.

Use our account support path and include your registered phone identifier, the request type and any relevant transaction reference. Never send a password or wallet PIN. We may ask for an ownership check, then explain the next step for access, correction, deletion or a cookie-related question.