Reference

Privacy Policy For Your Account

Our kode syair sdy Privacy Policy shows how we handle account details, wallet references and device signals from your first account step onward.

Clear data purposesWallet reference checksPolicy access before signup
kode syair sdy Privacy Policy For Your Account
HELP WITH PRIVACY

Privacy Requests Through Your Account

You do not need to search across the lobby to ask about your privacy.

Account privacy request Use the account help path to ask what personal details we hold or why…
Wallet reference check If a DANA, OVO, GoPay or QRIS reference looks unfamiliar, send the receipt reference…
Access correction path When your name, phone detail or account record needs correction, describe the exact field…
HANDLING DETAILS

How kode syair sdy Handles Privacy

We keep our privacy work tied to practical account events rather than collecting details without a purpose.

Account data use

We use your registered phone number and account details to create the correct login path, complete phone verification and send account-related replies. We do not need your DANA, OVO, GoPay or QRIS PIN to identify a payment reference.

Cookie choices

Cookies and browser storage can keep a session active or remember a setting during your visit. You can clear them from Android or desktop browser controls, though clearing storage may require you to complete the account login step again.

Device security

We may record browser type, device signals and login timing to detect an unusual account attempt. If an access check interrupts your session, use the account help path rather than sharing a password or a one-time phone code.

Payment references

A wallet or bank reference can show that a payment request belongs to a particular account. We use that reference for status checks involving DANA, QRIS, bank transfer or virtual account steps, without requesting your banking password.

Retention choices

We keep account, support and transaction records only for the period needed for security, dispute handling and legal duties. When you ask about removal, we explain which records can be deleted and which must remain for a stated operational reason.

Your change request

You can ask us to access, correct or clarify personal details through account support. Include the registered phone number, the field in question and your preferred reply route; we may confirm ownership before making a change.

Privacy Policy Answers For Indonesia

These Privacy Policy answers focus on the account situations you are most likely to meet: opening access, checking a wallet reference, using a mobile browser and requesting a change. We keep each answer practical so you know what to send, what we may verify and where local law affects account eligibility. If your question is not listed, use the account help route with the registered phone number.

It covers account details, phone verification, login records, device and browser signals, support messages, cookies and payment references. It explains why we use each category, how long records may remain, and how you can ask about access or correction where local law permits.

Yes. The policy covers transaction references connected with DANA and QRIS, as well as OVO, GoPay, bank transfer and virtual account steps. We use those references to check account status, but we do not ask for your wallet PIN, banking password or one-time code.

Phone verification helps connect the account to the person completing the account step and helps us respond to access questions. We may keep the verification result and related security record for the period needed for account protection, dispute handling and legal duties.

Yes. Send the request through account support with your registered phone number, the detail that is wrong and the correction you want. We may confirm account ownership before changing it, and we will explain if a record cannot be changed for a legal or security reason.

Use the account help path and ask for a Privacy Policy data access request. State which category you want, such as login records, phone verification, device signals or payment references. We may ask for an ownership check before describing or releasing the relevant record.

Cookies or browser storage may support a login session and remember a setting on your Android or desktop browser. You can clear them in browser controls. After clearing storage, you may need to complete phone verification or the account login step again.

You can submit a removal request through account support, and we will separate eligible details from records that must remain for security, payment disputes or legal duties. Our reply will explain the result and identify the relevant category without asking for your private wallet credentials.