Reference

Legal terms for your account

Before you open an account, this page tells you what we store, how we verify requests, and how local law affects access.

IndonesiaDANAOVOGoPayQRIS
sizi999 Legal terms for your account
CONTACT PATHS

How to reach our legal team

If you need help with a legal request, use the same channel you are already logged in with, or write from your registered email so we can verify the account faster.

Live Chat Start here when you need a policy answer, a record check, or a correction request. We attach the chat to your account so you do not repeat the same details twice.
Email Desk Send a written request from your registered email if you want a traceable reply. Include your account ID, the change you want, and any file we asked you to share.
WhatsApp Window Use WhatsApp during 09:00-22:00 WIB for quick follow-up after you send a request. We use it for status checks, region questions, and document confirmations with the same case number.
DATA AND ACCESS

How we handle data and access

This page covers how we handle personal data, cookies, account security, retention, and change requests.

Data handling

We store the account details you enter, the request thread, and the device data attached to the session. That lets us match DANA, OVO, GoPay, or QRIS records to the correct profile without asking you to repeat the case.

Cookies and session

Cookies keep your login state, language, and security checks in place while you move between pages. If you clear them on Chrome, Safari, or in-app browsers, we may ask you to verify again.

Account security

Use the same email and phone number you registered with, then change your password after any support handoff. We may pause the session if the login pattern changes, so your request stays tied to you.

Retention

We keep request logs and verification records only as long as needed for support, dispute handling, or the record rules that apply in your region. When the retention rule ends, we remove or archive the file.

Change requests

If you want a correction, deletion, or access check, tell us exactly what should change and where it appears. We verify the request against the account first, then confirm the result in the same channel.

Contact and escalation

If the first reply does not solve the issue, ask for escalation in live chat or email the same case again from your registered address. We keep the thread open until the legal question is closed.

Questions about legal access

These are the questions we hear most when you want to check the rules before you send a request. The answers stay focused on access, data use, cookies, and the contact path that matches your account, so you can act without guessing. If your case involves DANA, OVO, GoPay, QRIS, or a device change on Android or iPhone, we still verify it the same way against your registered details.

Local law controls access, and we only continue the account flow where it permits it. If your region changes, we follow the new rule and update the way we handle the case.

We keep the registered email, phone number, request history, and the device or browser signals tied to the session. That lets us match your case to the right account without asking for the same data twice.

Yes. Send the exact change you want, the page or record it affects, and the email on the account. We verify the request first, then confirm what changed in the same channel.

Cookies help keep login, language, and security checks stable while you move through the site. If you clear them in Chrome, Safari, or another browser, you may need to verify again.

Use live chat for the fastest first reply, WhatsApp between 09:00-22:00 WIB, or email if you want a written trail. Send the message from your registered address so we can match it quickly.

We ask for a document check when the request involves identity, region, or payment records such as DANA, OVO, GoPay, or QRIS. It is the fastest way to keep the case attached to your account.

We stop the account flow for that region and close the request with a clear explanation. If you move later and the local rule changes, send a fresh request from the same registered contact.