Reference

forum syair sdy Privacy Policy

The forum syair sdy Privacy Policy explains what we collect when you create an account, sign in from a mobile device, or check DANA, OVO, GoPay and QRIS…

Account dataWallet recordsCookie choicesPrivacy requests
forum syair sdy forum syair sdy Privacy Policy
CONTACT ROUTES

Where to Ask About Your Privacy Policy

A clear contact path matters when a phone check, wallet reference or device record needs attention.

Privacy request path Use the privacy contact route displayed with this policy when you want to ask what personal data we hold, why it is used, or how long a record remains. Include your account identifier and the subject of your request so we can check the correct profile.
Account access concern If a phone verification step blocks access to your account, describe the device path and the message shown on screen. We can compare that report with sign-in and security records without asking you to disclose a password or one-time verification code.
Wallet record question For a DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference, send the date, amount display and status label visible in your account. We use those details to locate the relevant record while limiting the personal data shared in support.
HANDLING PRACTICES

What We Do With Your Account Data

We handle privacy as part of the account path, from phone verification through wallet status checks and later access from another device.

Data collection

We may collect registration details, phone verification results, sign-in timestamps, device and browser signals, support messages, and payment references from DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. We link these records to an account only when the operational purpose requires it.

Cookie controls

Cookies and similar device storage can help remember a session, preserve a selected account path or identify repeated sign-in attempts. You can manage cookie settings through your browser or device controls, although changing them may affect sign-in continuity and some privacy preferences.

Account security

Phone verification, sign-in history and device signals help us identify unusual access. If you move from a mobile browser to desktop, a new check may appear. We do not ask you to place a password, PIN or one-time code in a privacy request.

Retention periods

We retain account, support and transaction references only for as long as needed for the purpose described in the Privacy Policy, account security, dispute handling or applicable obligations. When a record no longer needs retention, our process is to delete it or remove identifying links.

Requesting changes

You may ask us to correct inaccurate account details, explain a data use, provide access to eligible records or request deletion where applicable. We may first verify that the request comes from the account holder before changing or disclosing personal data.

Third-party handling

Payment and technical providers may process limited information needed for wallet status, bank transfer matching, QRIS references or secure delivery of account functions. We require the shared data to serve that stated purpose and do not treat a payment reference as permission for unrelated use.

Privacy Policy Questions From Indonesia

These Privacy Policy answers address the account questions we expect before registration: what is collected, how wallet references are used, what happens across devices and how to request a change. If your situation is different, send the smallest useful set of details through the privacy contact route rather than sharing credentials.

It covers account and contact details, phone verification, sign-in and device records, cookies, support messages, and payment references such as DANA, OVO, GoPay and QRIS. It also explains purposes, retention, security practices and the steps for requesting access, correction or deletion.

A wallet or QRIS reference helps us match a payment status with the correct account and investigate a receipt question. We use the reference needed for that task, not your wallet password or one-time code. Bank transfer and virtual account references follow the same purpose-based approach.

Use the privacy contact route shown on this page and identify your account with the contact detail attached to it. State whether you want access, a correction, an explanation or deletion. We may verify account ownership before releasing records or changing profile data.

Yes. The policy applies when you sign in through a mobile browser, desktop browser or another supported device path. Device and browser signals may be recorded for session continuity and security. Moving from mobile to desktop can trigger phone verification or another access check.

You can request deletion of eligible personal data through the privacy contact route. We assess the request against account security, unresolved transaction references and applicable retention duties. If some records must remain, we will explain the reason and remove identifying links where the process allows.

Cookies may remember a session, retain a selected account path or help identify repeated sign-in attempts. Your browser or device settings can limit or clear them. That action may interrupt sign-in continuity, so you may need to verify your phone again when returning.

Yes. Access, eligibility and some privacy rights depend on local law. We apply the Privacy Policy to requests from Indonesia and assess the account context before responding. If a legal restriction affects a request, our contact response will explain what we can provide and why.