Reference

Open sabun69 Privacy Policy for Your Account

Our Privacy Policy explains what sabun69 collects when you create an account, sign in, use DANA or QRIS, and contact support about wallet status.

Account recordsWallet activityDevice checksSupport requests

Explore Our Lobby Read FAQ

Check Privacy Policy Before Account Access

sabun69 Service availability depends on jurisdiction. Users are responsible for checking local law before access.

This Privacy Policy applies to the account path, lobby pages and support contacts connected with sabun69. We may collect your phone number, verification result, sign-in time, device details, IP address, wallet selection and transaction reference when you use DANA, OVO, GoPay, QRIS, bank transfer or a

1
virtual account. Payment partners may process their own records under their separate terms, while we retain the references needed to match a deposit, withdrawal request or receipt query. Cookies and similar tools help keep your session active, remember selected settings and identify unusual sign-in activity. We
2
restrict internal access to account data, keep records only for operational, security or legal needs, and remove or anonymise them when those needs end. Account access depends on local law, and we may ask for additional checks where local law permits.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

CONTACT THE TEAM

Browse Support Paths for Privacy Requests

Our support route is designed to keep a privacy request connected to the right account record. Use the support form beside the cashier path for questions about a receipt, wallet status or stored contact detail. Include your registered phone number and request type, but do not send a password or full payment credentials. We use the account trail to confirm ownership before making a change.

Team online

Account data request

Ask us what account details we hold through the support form linked to your account area. We may confirm your phone verification before sending a copy or discussing any stored record.

Wallet record question

For DANA, OVO, GoPay or QRIS records, share the transaction reference and date through support. We use those details to locate the relevant entry without requesting your wallet password.

Security concern

If a sign-in or device entry looks unfamiliar, contact us from the account support path and change your password. We can check session records and help protect the account after ownership confirmation.

HOW WE HANDLE DATA

Explore Privacy Controls Inside sabun69

We keep this policy practical by linking each data use to an account action you can recognise.

Account details

We use your phone number and verification result to identify the account holder, send account notices and handle support requests. We do not ask for your password through a support message.

Session cookies

Cookies can remember your sign-in state, language choice and selected page settings. You can clear them through your browser, although removing them may require another account check.

Device signals

A phone or desktop session may provide browser, device and network signals that help identify unusual access. These signals support account protection and are not used as a public profile.

Payment matching

DANA, OVO, GoPay, QRIS and bank transfer references help us match a payment question to your account. We use the reference and status, not your wallet password or banking PIN.

Retention period

We retain account, support and transaction records for operational, security or legal needs, then remove or anonymise them when no valid reason remains to keep them.

Change request

You can ask us to correct contact data, explain a stored record or request deletion through support. We first confirm account ownership and may retain limited records where local law permits.

Ask About Privacy Policy and Account Data

These Privacy Policy answers cover the questions we expect before you open an account from Indonesia. They explain the records created by sign-in, wallet activity, cookies and support, plus the route for correction or deletion. If your situation is not covered, use the support path beside the cashier area and refer to the relevant transaction or device.

It covers account details, phone verification, device and session data, cookies, payment references, support messages, retention and requests to correct or remove personal data.

We use your phone number to create and identify the account, complete phone verification before account access and connect support questions with the correct account record.

It covers the payment references and status we receive for DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity. Each payment provider may keep separate records.

We may receive browser type, device signals, IP address, sign-in time and session activity. We use them to protect account access and investigate unusual sign-in behaviour.

Send a request through the account support form with your registered phone number and the specific record involved. We confirm ownership before providing a copy or changing details.

You can request deletion through support. We assess the request against active account needs, security checks and records we must retain where local law permits.

Yes. Account access and certain data requests depend on local law. Where local law permits, we explain the available choice and any records that must remain.

Open sabun69 Privacy Policy for Your Account

Browse Support Paths for Privacy Requests

Account data request

Wallet record question

Security concern

Explore Privacy Controls Inside sabun69

Account details

Session cookies

Device signals

Payment matching

Retention period

Change request

Ask About Privacy Policy and Account Data

01 What does the sabun69 Privacy Policy cover?

02 Why does sabun69 need my phone number?

03 Does the Privacy Policy cover DANA and QRIS payments?

04 What device data can sabun69 collect?

05 How can I request a copy or correction?

06 Can I ask sabun69 to delete my data?

07 Does local law affect Privacy Policy access?

Related Pages