Reference

Privacy Policy for Your Account Data

This page explains what we collect when you open an account, how we use login, device, and contact data, and how we treat messages linked to DANA, OVO…

Account dataCookiesSession checksDANAQRIS
bansos188 Privacy Policy for Your Account Data
REQUEST CHANNELS

Where to Send Privacy Requests

If you want help with this policy, send the request from the account menu, use live chat, or email the privacy desk. Our chat line runs daily from 09:00 to 23:00 WIB, and we ask for the account email plus any payment reference so we can locate the record quickly. For requests tied to DANA, OVO, GoPay, or QRIS, include the time and amount shown in your app.

Team online

Live chat

Use live chat for a quick privacy question during the day. We will ask for your account email before we touch any record, so the reply stays tied to the right account.

Email

Email works well when you need to attach screenshots or a payment reference from DANA, OVO, GoPay, or QRIS. We keep the thread open until the case is closed.

Dashboard form

Use the dashboard form if you want a written trail inside your account. Add the time of the issue, the device you used, and the change you want, and we route it from there.

ACCOUNT SAFETY

How We Protect Your Data

Privacy works best when the rules are clear. We keep the policy tied to account use, session control, and support replies, then trim data once the reason to hold it ends.

Login records

We store login time, device type, and browser data so we can spot account sharing or a stolen session. That log helps us confirm your request without exposing more of your profile than needed.

Cookies

Our cookies remember your session and language choice on mobile and desktop. They are small browser files, and you can clear them in Chrome, Safari, or your preferred app browser when you close the page.

Payment references

When you send a DANA, OVO, GoPay, or QRIS payment check, we keep the reference, time stamp, and the contact used for the case. That record helps us match the request and close it cleanly.

Data retention

We keep account and support records only as long as needed for security, dispute handling, and required records. After that, we remove or anonymize the parts we no longer need.

Change requests

If your phone number, email, or name changes, send a request from the account form. We verify the account first, then update the record where local law permits and the details match.

Contact route

Privacy questions go to live chat, email, or the dashboard form. We answer in the same channel when we can, and we keep the thread so you can track each step.

Privacy Questions You Can Ask

These are the questions we hear most when you want to check, change, or understand a privacy record. We answer them from the account side, not with vague policy language, so you know what data we keep, how cookies work, and where to send a request. If your case involves a payment reference or a device change, include the time stamp and the device you used.

We collect the contact details you submit, the device and browser data needed to secure access, and the messages linked to your account. If you send a DANA, OVO, GoPay, or QRIS check, we also keep the reference.

Yes. Send the request from your account menu or email the privacy desk, and we will verify ownership first. Where local law permits, we update the record and tell you what changed.

We keep it only as long as needed for account security, support, and required records. Once the reason ends, we delete, trim, or anonymize the parts we no longer need.

Our cookies remember sign-in state, device choice, and language settings so you do not have to reset them each visit. They do not replace your password and you can clear them in your browser.

Only the staff who need it to match the request can see the reference, time stamp, and contact detail tied to the case. That keeps DANA, OVO, GoPay, and QRIS checks narrow and traceable.

Use live chat, the email route, or the dashboard form. Add your account email, the time of the event, and any payment reference so we can locate the record quickly and reply in the same thread.

Yes. Where local law permits, we process correction or deletion requests. If a request conflicts with retention duties or security checks, we explain the limit and keep the minimum record needed.