Reference

Open angsawin Privacy Policy details

The angsawin Privacy Policy explains how we handle your account, wallet and device data before you open an account or browse the lobby.

Account dataWallet recordsCookie choicesData requests
angsawin Open angsawin Privacy Policy details
CONTACT PATHS

Ask about Privacy Policy and wallet data

A clear contact route helps when you want to ask how your personal data is used or why a wallet reference appears in your account history. Send your request through the on-site support channel and include the phone number linked to your account, without sharing a password or one-time code. From Yogyakarta or elsewhere in Indonesia, you can ask about a receipt, device record, correction or access request. We use the details you provide only to locate and answer the policy matter.

Team online

Policy request

Use the on-site support path to ask for a copy of your account data or an explanation of a Privacy Policy section. Include your linked phone number and request type so we can route the matter without asking for your password.

Wallet query

If a DANA, OVO, GoPay or QRIS reference looks unfamiliar, send the receipt reference through support. We can compare it with the account record and explain the data held for that payment event without requesting your wallet PIN.

Correction route

For an incorrect phone detail, verification entry or device record, contact us from the account support path. Tell us which field needs attention and we will assess the request against the Privacy Policy and applicable local requirements.

DATA PRACTICES

Explore angsawin data handling steps

We keep our Privacy Policy practical by linking each data use to an account action you can recognise.

Account security

Phone verification is connected to account access, while device and session signals can help us identify unusual entry. Never send a password or one-time code to support. We use the minimum account details needed to examine a security concern.

Cookie control

Cookies can keep policy pages, login steps and account preferences working across your browser session. You can adjust cookie settings in your browser. Blocking some cookies may change how account access or policy controls appear on your device.

Payment records

A QRIS receipt, virtual account reference or bank transfer detail may be retained to match a payment event with your account. DANA, OVO and GoPay status can be checked against the related transaction record when you contact support.

Retention review

We keep personal data only for the stated service need or an applicable record period. When that need ends, we assess whether the record should be removed, anonymised or retained for a clearly stated reason in our Privacy Policy.

Access requests

You can ask what account, device or wallet data we hold by using the support route. Provide the linked phone number and a clear request. We may need to verify account ownership before releasing personal records.

Change requests

If your phone detail or account record is inaccurate, tell support which entry should change and why. We assess the request against account security needs, transaction records and local requirements before applying an appropriate correction.

Browse Privacy Policy answers

These Privacy Policy answers address the account and wallet questions you may have before opening an account with angsawin. They cover the records linked to phone verification, payment references, cookies, device access and requests sent through support. If your question is not listed, use the on-site contact path and describe the specific record or policy section you want us to check.

It covers how we collect and use account, phone verification, device, cookie and payment-reference data. It also explains retention, account security, access requests, corrections and contact steps. Wallet references may include DANA, OVO, GoPay, QRIS, virtual account or bank transfer details.

We use the phone number connected to your account for account access and verification steps. It can also help support locate the correct record when you ask about Account Verification or a payment status. Do not send your password or one-time code in a support request.

Yes. The Privacy Policy explains how transaction references can be used to match a DANA or QRIS event with your account and answer a receipt question. We may also handle related OVO, GoPay, virtual account or bank transfer references for the same purpose.

Send an access request through the on-site support channel and include the phone number linked to your account. State that you want your account data and mention any specific area, such as device records, cookies or payment references. We may verify ownership first.

Yes. Use support to identify the incorrect phone detail, verification entry or other account record and describe the correction needed. We assess the request against account security, transaction accuracy and local requirements, then explain the next step under the Privacy Policy.

Cookies can support page functions, policy access and browser session preferences. You can manage them through your browser controls. If you block certain cookies, account access or policy settings may not display in the same way on your device.

Contact us through the on-site support route and name the record you are asking about, such as a QRIS receipt, device signal or account detail. We explain the applicable retention reason and assess removal or restriction requests where local law permits.