Reference

Open Our Privacy Policy

We keep this page focused on the data we collect, why we keep it, and how you can ask for changes.

DANAOVOGoPayQRIS
moi4d Open Our Privacy Policy
SUPPORT LINES

Switch To Our Contact Paths

For privacy requests, we keep the path simple: live chat in the account area, email from your registered address, or the request form in Settings > Privacy. Our team replies every day from 09:00 to 23:00 WIB, and we may ask you to confirm ownership before we change data or release copies. If your question concerns a payment record, include the DANA, OVO, GoPay, or QRIS reference so we can locate it faster.

Team online

Live chat

Use live chat from the account screen if you need a data correction or a copy request. We use that thread to verify your account name, check the request, and reply during 09:00-23:00 WIB.

Email

Send your request from the address on file so we can match it to your account. Include the issue, the date, and any DANA, OVO, GoPay, or QRIS reference tied to the record.

Privacy request form

Open Settings > Privacy and submit the form when you want a data change, deletion request, or a question about cookies. That path helps us route the case without exposing your details in public channels.

SECURE RECORDS

Browse Our Data Handling Rules

Our handling rules are written to keep your account usable and your record trail short. We separate sign-in data, support messages, cookies, and payment references so each request can be checked without…

What we collect

We keep the account name you submit, contact details, login timestamps, device type, browser data, and request history. We do not need more than that to verify identity and answer privacy questions.

Cookie use

Cookies help the site remember your language choice, session state, and recent page path. On Android Chrome or iPhone Safari, you can clear them in browser settings if you want a fresh session.

Payment traces

When you use DANA, OVO, GoPay, or QRIS, we keep the reference number, amount, and time stamp needed to match the transfer to your account. That record stays separate from your profile until the case is closed.

Account security

We watch for unusual logins, repeated password attempts, and device changes. If we see a risk, we may ask you to confirm your ownership before the next edit, withdrawal request, or data change is accepted.

Retention timing

We keep records only as long as needed for account support, dispute handling, tax duties, and audit trails. After that, files move to deletion or restricted storage under our retention rules.

Change requests

To update, copy, or remove details, use Settings > Privacy or email us from the address on file. We verify the request, make the change where allowed, and reply with the result through the same channel.

Open Common Privacy Questions

It covers the account data you submit, cookies, device logs, payment references, support messages, and the steps we use to handle requests. It also explains when local law changes what we can store or share.

Yes. We keep the reference number, amount, and time stamp needed to match a transfer to your account, then store it only for support, dispute handling, and required retention.

Open Settings > Privacy, use live chat, or email us from your registered address. Tell us what needs changing, and we will check ownership before we update the record where local law allows.

We keep each record for the shortest time needed for account support, transaction checks, and legal duties. When that period ends, we delete it or move it into restricted storage under our retention rules.

Your browser may store cookies on Android Chrome, iPhone Safari, or desktop browsers when you stay signed in. Session cookies end when you sign out; persistent cookies stay until you clear them.

Use live chat in the account area, send email from the address on file, or open the request form in Settings > Privacy. We reply daily from 09:00 to 23:00 WIB.

Access depends on local law and is available only where local law permits. If your region is not eligible, we do not open the service there or process requests tied to that region.