Reference

Open Your soi55 Privacy Policy

soi55 Privacy Policy explains what we collect when you open an account, verify your phone, sign in from a mobile browser, or use DANA, OVO, GoPay and QRIS.

Clear data purposesWallet record detailsRequest path
soi55 Open Your soi55 Privacy Policy
CONTACT OPTIONS

Find Help With Privacy Requests

A clear contact route matters when you want to ask what data we hold or why a payment record appears in your account.

Account request Use our account support path to ask for a copy of personal data, explain…
Payment record For DANA, OVO, GoPay, QRIS, bank transfer or virtual account questions, include the payment…
Access concern If a privacy choice affects sign-in from your phone or desktop browser, describe the…
DATA PRACTICES

Explore How We Handle Account Data

We treat privacy as part of the account flow rather than a separate page you have to chase.

Data we receive

We receive details you provide during account creation and phone verification, plus sign-in time, browser or device signals, support messages…

Cookie handling

Cookies can preserve your session, remember an account state and help us detect an unusual sign-in path.

Account security

We use phone verification and account checks before discussing personal records or changing account details.

Payment matching

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references help us match a payment state to the correct account.

Retention period

We retain account, payment and support records only for the operational, dispute and legal purposes described in this Privacy Policy.

Changes and contact

You can ask us to access, correct or delete eligible personal data through the account support path.

Browse Privacy Policy Answers

These Privacy Policy answers address the searches we hear before an account is opened or a wallet is connected. They cover the records created by account access, the treatment of local payment references and the steps for asking us to change or remove data. If your question is not listed, send the account phone number and a short request through support without sharing secret credentials.

The soi55 Privacy Policy covers account details, phone verification, sign-in activity, browser and device signals, cookies, support messages and payment references. It also explains why we use those records, how long we retain them, how we protect them and how you can request access or changes.

Yes. The Privacy Policy explains how we use DANA and QRIS references, along with OVO, GoPay, bank transfer and virtual account status, to match a payment with your account. We do not need your wallet password or PIN to check a receipt or transaction state.

We use your phone number to create and verify your account, support sign-in checks and connect a privacy request to the account holder. If you ask to access, correct or delete data, we may ask for phone verification before discussing records or changing account details.

You can request access to eligible personal data through our account support path. Include your verified phone number and describe the records you want, such as sign-in history, cookie details or payment references. We may confirm your identity first and respond within the limits of local law.

Send a correction or removal request through support with the account phone number and the specific detail that needs attention. We review the request, verify ownership and explain any retention requirement. Removal is handled where local law permits and may not cover records needed for disputes or legal duties.

Cookies help keep your browser session connected to the right account and help us investigate unusual access. If you remove or block them, sign-in may restart and phone verification may appear again. Your browser settings control cookie removal, while our Privacy Policy explains their service purpose.

Contact support with the account phone number, the affected field and a short explanation. For a DANA, OVO, GoPay or QRIS mismatch, add the payment reference and date, but never include a wallet PIN, password or one-time code. We will check the record and explain the next step.