Reference

Privacy Policy for Your soda69 Account

Our Privacy Policy shows what data we collect when you open a soda69 account, sign in from a mobile device, or check DANA and QRIS wallet status.

Clear data purposesWallet record detailsCookie choicesContact path
soda69 Privacy Policy for Your soda69 Account
HELP WITH PRIVACY

Get Clear Answers About Your Data

A direct support route helps when you want to understand a record rather than guess from a wallet screen. Start from the account help path near the cashier area and describe the Privacy Policy question in plain English. Include the account phone number only through the secure contact route, never in a public message. We can then identify the relevant login, wallet or verification record and explain the next step. If your concern involves DANA, OVO, GoPay, QRIS, bank transfer or a virtual account, mention the payment rail so our team can check the right status.

Team online

Account privacy request

Use the account help path beside the cashier area when you want to ask what personal data is held for your soda69 account. Tell us whether the request concerns phone verification, login activity or profile details, and we will direct it to the relevant privacy process.

Wallet record question

Payment references can look different across DANA, OVO, GoPay and QRIS. Send your question through the account contact route with the rail name and approximate transaction context, while keeping passwords and one-time codes private. This gives us a usable starting point without exposing unnecessary data.

Access or correction help

If you cannot reach the account area to request a copy or correction, begin with login help and state that the request concerns the Privacy Policy. We may ask for an account step or phone verification detail to confirm the request belongs to you before discussing records.

DATA HANDLING

What We Do With Account Records

Privacy depends on practical controls, so our Privacy Policy connects each data type to a clear account task.

Account creation

When you open an account, we receive the details needed for the account path, including your contact information and phone…

Device and login signals

A mobile or desktop sign-in can produce technical details such as browser type, device signals and session time.

Payment references

For DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity, we may retain a reference, amount status and account…

Cookies and sessions

Cookies can keep an essential sign-in session working and remember a setting that supports your account path.

Retention and deletion

We retain account, security and payment-reference records only as long as needed for the stated operating purpose, dispute checks or…

Requesting a change

To request access, correction or an eligible deletion, contact us through the account help route and identify the record type.

Privacy Policy Answers for Indonesia

The questions below focus on the parts of our Privacy Policy that matter during account access, wallet checks and privacy requests. Read them before opening an account, and use the support path if your situation needs a record-specific answer. Any access or eligibility point depends on local law.

The Privacy Policy covers details you submit for an account, phone verification results, device and login signals, cookies, and payment references linked to DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. It also explains purposes, retention, security handling and ways to request access or correction.

Phone verification supports the account access step and helps us check that a privacy request comes from the account holder. We use the verification result for these account and security purposes. We do not ask you to place a password or one-time code in a support message.

When you use DANA or QRIS, we may keep a payment reference, status and account match so a wallet question can be checked. These records help distinguish a pending or completed reference from another account. Wallet passwords and one-time codes should remain private and are not needed.

Yes, you can contact us through the account help path and ask for access to eligible personal data held for your account. State whether you need profile, phone verification, login or payment-reference details. We may confirm ownership before responding, and the process depends on local law.

Use the account contact route and identify the specific detail that needs correction, such as a profile field or phone verification record. Avoid sending sensitive credentials. We may request an account step to confirm identity, then assess the change against the Privacy Policy and local law.

We keep records for the time needed to operate the account, protect login access, reconcile payment references, handle disputes or meet legal duties. The period can differ by record type. If you ask about deletion, we explain which data is eligible and which must remain.

Yes. The Privacy Policy explains cookies used to maintain an essential session and support account settings, along with browser controls for cookie storage. Removing a required session cookie may sign you out or require another login. Optional cookie choices depend on the controls available on your device.