Reference

Open the forum syair hk Privacy Policy

forum syair hk Privacy Policy sets out what we collect when you open an account, enter the mobile lobby, or connect DANA, OVO, GoPay and QRIS.

Account dataWallet recordsDevice accessPolicy requests
forum syair hk Open the forum syair hk Privacy Policy
REQUEST A HAND

Ask us about your stored account data

A clear contact route helps when a Privacy Policy question concerns your account or wallet record.

Account help path Use the account help route when you need to ask what contact details we…
Wallet status check For a DANA, OVO, GoPay or QRIS record, send the payment reference and approximate…
Policy contact route If you want a copy, correction or deletion assessment under this Privacy Policy, contact…
DATA HANDLING

See how we handle wallet and device data

Our handling steps are tied to practical account events rather than a broad collection of unrelated details.

Account details

When you open an account, we collect the contact details needed for account access and phone verification. We use them to identify your account, send account-related messages and investigate access issues. We do not ask you to place a password inside a support message.

Payment references

A DANA, OVO, GoPay or QRIS payment can create a reference, amount and status record linked to your account. Bank transfer and virtual account entries serve the same matching purpose. These records help us reconcile receipts and answer wallet questions.

Device signals

When you move from phone login to the mobile lobby, we may record device and session signals such as browser type, access time and security events. These signals help us spot unusual access without reading unrelated content stored on your device.

Cookies in use

Cookies can keep your session active, remember security preferences and help us understand whether an account page loaded correctly. You can manage cookies through your browser settings, although changing them may interrupt login, verification or the path from account access to the lobby.

Security controls

We use account verification, session checks and restricted internal access to protect stored records. If a login or wallet status appears unusual, we may pause the request and ask for an account step before discussing it. Never share your password or wallet PIN with us.

Retention requests

We retain records only for the account, payment reconciliation, security and support purposes described here, subject to applicable requirements. To request access, correction or removal, contact us with the relevant account step or payment reference so we can assess the request safely.

Find answers about Privacy Policy requests

These Privacy Policy answers cover the questions you may have before opening an account or connecting an Indonesian wallet. We explain what can be requested, how verification works and what happens when a device, payment reference or account record needs attention. Access remains subject to local law.

It covers account contact details, phone verification, wallet references, device and session signals, cookies, security events, retention and requests concerning your records. It also explains how DANA, OVO, GoPay, QRIS, bank transfer and virtual account entries may be matched to an account.

Phone verification helps us confirm that the person requesting account access controls the contact number supplied during opening. It also supports account recovery and data requests. We use the verification step for account security, not as permission to request your password or wallet PIN.

Yes. Send an access request through the account support route and identify the account step or record you mean. We may verify your identity first, then explain which contact, device, cookie or payment details can be provided under this Privacy Policy.

Contact support with the payment reference and approximate date, rather than your wallet PIN or password. We will compare the request with the account record, explain any mismatch and correct eligible details after confirming that the request comes from the account holder.

Yes. It covers session and security signals connected with your phone or browser, such as access time, browser type and unusual login activity. We do not use those signals to read unrelated device content. Browser cookie controls remain available to you.

Retention depends on the purpose of each record, including account access, payment reconciliation, security and support. We do not promise one period for every entry. You can ask us to assess a record through support, and we will explain whether removal is available.

You can submit a deletion request through the account support route. We first verify the request and identify the affected records. Some entries may need to remain for security, reconciliation or applicable requirements; we will explain the reason and the resulting action.