Reference

as1131 Privacy Policy for Your Account

The as1131 Privacy Policy explains what account, device and wallet details we use, why we use them, and how you can ask about your data before opening an…

Clear data purposesWallet status checksAccess request pathCookie choices
as1131 as1131 Privacy Policy for Your Account
CONTACT PATHS

Where to Ask About Privacy Policy

A direct account route helps you raise a Privacy Policy question without describing your issue across unrelated channels.

Account data request Ask us to explain the account details connected with your as1131 profile.
Wallet record question If a DANA, OVO, GoPay or QRIS status looks incorrect, send the transaction reference…
Access concern For an unfamiliar login or a device concern, tell us which account step was…
DATA PRACTICES

Inside as1131 Privacy Policy Controls

The Privacy Policy is supported by practical controls rather than broad promises. We separate account identification from the payment status needed to reconcile DANA, OVO, GoPay, QRIS, bank transfer and virtual account…

Account details

We use your submitted contact details to create and verify the account, including the clear phone verification step before account access. Keeping your phone or email current helps us respond to a data request and identify the right profile.

Payment references

A wallet choice is not the same as a wallet password. Our records can include the selected DANA, OVO, GoPay or QRIS rail, amount status and receipt reference needed to reconcile your account activity.

Cookies

Required cookies support the account path, session continuity and security checks. Where optional cookie controls are shown, you can adjust them in the site settings; changing them may affect remembered login steps without changing the Privacy Policy.

Device security

We may record device or browser signals linked to sign-in activity so we can examine an unfamiliar access event. If you notice a problem, use the support route and state the device path, such as mobile browser or desktop.

Retention

We keep information for the period needed for account operation, security checks, dispute handling or applicable legal duties. A retention question can include the record type, such as phone verification or a QRIS receipt, for a more useful response.

Policy requests

You can ask for access, correction or a suitable deletion review through account support. We may need to verify that you control the profile before releasing personal data, and some records may remain where local law permits.

Privacy Policy Questions About as1131

These Privacy Policy answers focus on the account, device and payment records you are most likely to ask about before using as1131. If your situation is not covered, send the account detail and relevant receipt reference through the support path so we can address the specific record.

The as1131 Privacy Policy covers account details, phone verification, device and login signals, cookies, payment status and support records. It explains why we use each category, how retention works, and how you can request access or correction subject to local requirements.

We use your phone number for account identification and the clear phone verification step before account access. It also helps us match a support request to the correct profile. We do not need your wallet PIN or password to investigate a DANA or QRIS status.

Yes. Our Privacy Policy covers payment references created when you choose DANA, OVO, GoPay or QRIS, including the selected rail, status and receipt reference. These details help us reconcile account activity and resolve a wallet status question without receiving secret wallet credentials.

Use the support path connected to your account and ask for a personal data access request. Include the registered phone or email and describe the record you want, such as phone verification, device access or a QRIS receipt. We verify account control first.

You can request a correction through account support and explain which field is inaccurate. Providing the registered contact detail and the corrected value helps us locate the profile. We may ask for an account check before changing information linked to access or wallet status.

We retain information for the period needed for account operation, security investigation, dispute handling or applicable legal duties. The period can differ by record type, such as a login event, phone verification or bank transfer reference. You can ask support about a specific category.

The Privacy Policy applies to the as1131 website and linked account areas when you access them from Jakarta or another supported location. Account eligibility depends on local law, and access is provided where local law permits. Device and account records are handled under the same stated practices.