Reference

sabun 69 Privacy Policy For Your Account

The sabun 69 Privacy Policy explains what we collect when you open an account, sign in from a phone, or use DANA, OVO, GoPay and QRIS.

Account detailsWallet recordsDevice accessCookie choices
sabun 69 sabun 69 Privacy Policy For Your Account
CONTACT DATA TEAM

Get Privacy Policy Help Through Support

A direct support route helps you ask about the Privacy Policy without explaining your concern repeatedly.

Account access Use the account support channel when you need to ask which phone verification detail…
Wallet records Send a payment receipt or reference with sensitive numbers covered.
Privacy requests Ask support to route a correction, access or deletion request to the privacy contact.
DATA HANDLING PRACTICE

What We Do With Your Personal Data

Privacy Policy choices matter most when they match the account steps you actually take. We separate sign-in checks, payment references, device signals and support messages so each record has a clear operational…

Account creation

When you open an account, we collect the details needed to create your profile and support phone verification. We use them to distinguish your account from another person’s request.

Payment matching

DANA, OVO, GoPay and QRIS references help us match a cashier status to your account. Bank transfer and virtual account records may be checked when a receipt needs confirmation.

Device signals

A phone or desktop browser can provide device and session signals used to spot unusual access. These signals help us ask for an account check without storing the contents of your device.

Cookies

Cookies can keep a session active, remember selected settings and help us understand an access error. You can adjust browser cookie controls, although some account functions may then require another sign-in.

Security controls

We use phone verification, session checks and account activity records to protect access. Never send a password or full wallet credential in support messages; our team does not need those items.

Retention requests

We keep personal data only for account security, payment reconciliation, dispute handling and legal duties. You can ask what remains, request a correction, or ask whether deletion is available for a specific record.

Privacy Policy Answers For Indonesian Accounts

These Privacy Policy answers focus on the questions we expect before you create an account or contact us about an existing one. They cover payment references, phone verification, cookies, device access, retention and requests for personal data. If your situation is not listed, use support and include the account step or payment reference involved, with private credentials removed.

It covers account details, phone verification, login and device signals, cookie use, payment references, support messages and retention. It also explains how to ask for access, correction or deletion where that request is available under local law.

No. We use payment references and status details to match a DANA or QRIS transaction with an account request. Do not send wallet passwords, PINs or full credentials to support; those are not needed for a privacy request.

Phone verification helps connect the person requesting account access with the correct account record. It can also reduce mistaken disclosure when you ask about login history, payment status or personal data held under your account.

Yes, you can contact support with your account phone number, request type and relevant date. We may confirm ownership before replying, and any access, correction or deletion outcome depends on local law and required record-keeping.

Cookies may keep your session active, remember selected settings and help identify an access problem. You can change browser cookie controls, but disabling some cookies may require repeated login or affect account pages.

Retention depends on the purpose of each record. We may keep DANA, OVO, GoPay, QRIS, bank transfer or virtual account references for security, reconciliation, disputes and legal duties, then remove or restrict them when no longer needed.

Contact support and include the approximate login date, device type and account phone number. We can explain the available record and check an unusual session, but we will never ask you to provide your password or device contents.