Reference

Legal Access for Your Account

We keep the legal page in front of the lobby so you can check access rules before you move further.

Local law firstMenu > LegalDANA / OVO / GoPay / QRISMobile and desktop
birowin Legal Access for Your Account
CONTACT PATHS

Where To Reach Us About Legal

If you need a legal check on access, identity, or account closure, we answer through live chat from 08:00-22:00 WIB and through email after the ticket lands in our queue. Use the account menu on mobile, or the footer link on desktop, to reach the request form and attach a screenshot, wallet name, or reference number. That keeps the thread tied to your record.

Team online

Live chat

Open the chat bubble from the account menu for access or document questions. We use it for region checks, correction requests, and account closure steps when local law allows the action.

Email desk

Send a written request when you need a longer trail. Include your account name, the payment name on DANA, OVO, GoPay, or QRIS, and the detail you want corrected.

Form route

Use the form in the footer on desktop or the menu on mobile. It helps us attach screenshots, store timestamps, and route the thread to the team that handles records.

DATA AND ACCESS

How We Handle Your Data

We treat legal requests as account work, not loose chat text. Session cookies keep you signed in, device logs help us confirm the same account holder, and payment references help us match…

Data handling

Only the details needed for access, verification, and request handling stay in our system. We do not ask for extra fields without a reason, and we limit who can open the record to staff who need it.

Cookies

Session cookies keep the account menu and legal pages aligned to your sign-in state. If you clear them, the next visit may ask you to sign in again and confirm the same access path.

Account security

We use login checks, device signals, and matching payment names to reduce account misuse. If a request looks unusual, we pause it until you confirm the thread through chat or email.

Retention

We keep records only for the time needed to run the account, answer the request, meet legal duties, or settle a dispute. After that period, we delete or anonymize the rest.

Contact owner

If you want access, correction, or closure, send the request from the same account email or chat thread. That helps us confirm you are asking about your own record.

Change request

Tell us the exact field you want updated, attach a screenshot or document if we ask, and wait for confirmation before using the new detail on later sessions.

Questions About Legal Access

These are the questions we answer most when you check access rules, account records, or a change request. Each reply stays tied to local law, the account detail you sent, and the channel you used, so you can see the next step before you submit anything. If your region has a different rule, we follow that rule for your session.

Only where local law permits. If your region blocks access, we do not ask you to bypass it. The legal page and contact paths stay visible, and you can ask chat to confirm the current status.

We may store your name, mobile number, sign-in email, and the payment name you use for DANA, OVO, GoPay, or QRIS. If we need to verify ownership, we compare those details with the account record.

We use the payment name to match your request to the right record and reduce mistakes. That match helps when you ask for a correction, a closure step, or a legal check on an earlier transaction.

Send the corrected detail through live chat or email, and add a screenshot or document if we ask for one. We verify the request against the account record before we update anything.

Yes. Session cookies keep you signed in and help the legal pages load with the right region setting. If you clear them, you may need to sign in again and confirm the same access path.

We keep records only as long as needed for account handling, request replies, legal duties, and dispute resolution. After that period, we delete or anonymize what is no longer required.

A support agent receives the thread first, then routes it to the record team if needed. Use the account menu, the footer form, or email so we can keep the request tied to your record.