Reference

How Your Privacy Works Here

We keep your account data, wallet records, device checks, and cookie choices tied to clear privacy steps before you jump into the lobby.

DANA privacy contextOVO wallet recordsGoPay transaction logsQRIS receipt checksAccount > Security
jipan288 How Your Privacy Works Here
CONTACT ROUTES

How To Contact Our Privacy Team

Privacy requests work faster when you contact us from the same account you want us to check.

Live chat privacy queue Open live chat from your account menu between 09:00 and 23:00 WIB, choose privacy help, and tell us whether your request is about login data, wallet records, cookies, or account details.
Email request path Send your privacy request to [email protected] using the email linked to your account. Add your username, payment rail name if relevant, and the exact record you want us to check.
Account security screen Go to Account > Security > Active Sessions to see device sessions we use for account protection. If a session looks unfamiliar, contact us before asking for data removal.
DATA HANDLING

6 Ways We Handle Privacy Requests

We treat privacy work as an account-operation task, not a generic form reply. Our team checks the request, confirms account ownership, then looks at the related record set: profile details, device sessions…

Account ownership check

Before we change personal data, we match your request to your login email, username, recent session, and a wallet reference if needed. This keeps another person from changing your account records.

Cookie choice handling

Cookies help keep your session active, remember language preference, and flag unusual login behavior. You can clear browser cookies anytime, though you may need to log in again after doing so.

Payment record privacy

DANA, OVO, GoPay, and QRIS receipts are stored with transaction time, reference code, and account link. We use them to match deposits, withdrawals, refunds, and wallet disputes accurately.

Device session control

Your mobile browser may create a session record with device type, IP range, and login time. Check Account > Security > Active Sessions, then close any session you no longer use.

Retention decisions

We remove or shorten records when they are no longer needed for account service, payment matching, or dispute checks. Some wallet records remain longer because transaction tracing requires them.

Correction request process

If your name, email, or contact detail is wrong, send the correction through live chat or privacy email. We may ask for account proof before updating the profile record.

Questions You May Ask Before Joining

These answers explain the privacy steps you are most likely to need before or after you open an account. We focus on account records, payment traces, device behavior, cookie choices, and contact routes. If your question involves access, the answer depends on local law, and our support team will handle it through the same privacy process described above.

We collect the details you submit during account creation, such as username, contact email, login data, and security signals. Wallet records from DANA, OVO, GoPay, or QRIS are added only when you use those payment rails.

We keep payment references so deposits, withdrawals, refunds, and disputes can be matched to the correct account. The record usually includes rail name, time, amount, transaction code, and related account activity.

Yes, you can ask through live chat or [email protected]. We check account ownership first, then confirm which records can be deleted and which must remain for payment tracing or dispute handling.

Cookies keep your session active, remember simple preferences, and help spot unusual access. If you clear them, your account is not deleted, but you may need to log in again and repeat security checks.

Open Account > Security > Active Sessions after login. You can see recent session entries by device type and time, then close a session you do not recognize before contacting privacy support.

Only support and account-security staff assigned to privacy work can handle your request. They check the specific record involved, such as profile data, wallet receipts, support chats, or device session history.

We aim to answer simple privacy messages during support hours, 09:00 to 23:00 WIB. Requests involving payment records or account ownership checks can take longer because we must match the records carefully.