Reference

sayap33 Privacy Policy for Your Account

sayap33 Privacy Policy explains how we collect, use, protect and retain the details connected with your account, including wallet records from DANA, OVO, GoPay and QRIS.

Account dataWallet recordsCookie choicesAccess requests
sayap33 sayap33 Privacy Policy for Your Account
POLICY HELP ROUTE

Get Help With Privacy Policy Requests

A clear contact path helps when you want to understand or change personal data held by us.

Access request Ask us to identify the personal details linked with your account.
Correction request If your account detail is inaccurate, use the account help route beside the cashier…
Privacy concern Send a clear description of the concern through account help, including the device path…
HANDLING YOUR RECORDS

How We Apply This Privacy Policy

We apply this Privacy Policy to the account journey rather than treating data handling as a separate task.

Account details

We use your phone number, verification status and account identifiers to provide account access and match a privacy request with the correct record. We do not need unrelated profile details for that verification step.

Wallet references

DANA, OVO, GoPay and QRIS references help us identify payment status and reconcile account activity. We record the relevant transaction detail rather than treating your wallet history as a general-purpose profile.

Cookies

Our browser path may store cookies or similar session data to keep sign-in steps working. You can manage browser storage through your device settings, though removing it may require another account verification.

Account security

Before we disclose private account details or change verification data, we may compare your request with the phone and sign-in details already held. This helps reduce unauthorised changes to your account.

Retention

We retain account and transaction records only for the period needed for account operations, dispute handling and applicable legal duties. Ask through account help if you need the reason for a particular retention period.

Policy changes

When this Privacy Policy changes, we place the revised wording on this page and may connect it to your account access flow. Check the page before submitting a new data request or opening an account.

Privacy Policy Answers for Indonesia

These Privacy Policy answers address the searches we hear most often from Indonesian account holders. They explain the data connected with phone verification, local wallet references, cookies, requests and access conditions. If your situation is unusual, use account help with the relevant account or transaction reference so we can assess it against the policy.

The sayap33 Privacy Policy covers account details, phone verification, sign-in device records, cookies, wallet references and transaction data connected with your account. It also explains access, correction, retention and contact options.

Yes. The Privacy Policy includes payment references and status details linked with DANA, OVO, GoPay and QRIS activity. These records help us match account transactions without treating them as unrelated personal information.

Open the account help link beside the cashier path and request access to your stored details. Include your verified phone number and, if relevant, a DANA, OVO, GoPay or QRIS reference.

Where local law permits, you can request a correction through account help. We may verify your phone or sign-in details first, then explain whether the requested change can be made under this Privacy Policy.

Cookies or similar browser storage can support sign-in and session steps. You can remove or control them in your device browser settings, but doing so may clear session data and trigger phone verification again.

We retain account and transaction records for the period needed for account operations, disputes and applicable legal duties. You can ask through account help why a particular record remains under this Privacy Policy.

Yes. Privacy rights and account eligibility depends on local law. Where local law permits, we assess access, correction or deletion requests and explain any restriction that prevents a requested action.