Reference

What Our Privacy Policy Covers

Our Privacy Policy explains what we collect when you open an account, send a message, or move funds through DANA, OVO, GoPay, or QRIS.

Account dataSession cookiesDANAQRIS
senopti4d What Our Privacy Policy Covers
SEND REQUESTS

Where To Send Privacy Requests

Privacy questions move faster when you use the right channel. WhatsApp is open around the clock, live chat runs from 08.00-22.

WhatsApp Use WhatsApp for privacy checks any time. We can confirm what is stored on your account, explain why a field is required, and start a correction request if your phone number or email has changed.
Live Chat Open live chat after you sign in if you want a faster answer inside the site. It is useful for cookie questions, device checks, and short requests about DANA, OVO, GoPay, or QRIS references.
Email Email works best when you want a written record. Send your account email, the change you need, and any payment reference so we can verify the request and reply with the next step.
DATA HANDLING

How We Handle Your Data

We built this policy flow around the steps you actually take: open an account, confirm a device, use a local payment rail, and ask for a change when something does not match.

What We Collect

We keep the minimum account fields needed to run the policy flow: name, phone number, email, device type, login time, and the reference tied to DANA, OVO, GoPay, or QRIS when you choose one of those rails.

Why We Use It

Those details let us check sign-in activity, match a transfer to the right account, answer a support request, and meet legal requests when local law requires it. We do not use them for unrelated messaging.

Cookies On Devices

On Android Chrome, iPhone Safari, and desktop browsers, we use session cookies and similar tools to remember the language choice, keep the session stable, and stop repeated verification prompts. They do not read files on your device.

Account Checks

When a name, phone number, or payment reference does not match, we may ask for a fresh confirmation before we change the record or continue a request. That protects your account and limits accidental edits.

Retention

We keep records only as long as needed for account history, request handling, dispute follow-up, and legal retention. After that period, the data is deleted or made non-identifying where our systems allow it.

Your Requests

You can ask for a copy, correction, or deletion check through chat or email after you sign in. We will compare the request with the account details on file before we make any change.

Privacy Questions We Hear Most

If you want the short answer first, start with the questions below. They cover what we collect, why each field matters, how long records stay on file, and how to ask for a correction or copy. We answer through the same account channels used for profile changes, and any access point remains subject to local law. That keeps the policy in plain language before you contact us.

We collect the details needed to open and protect your account: name, phone number, email, device type, login logs, and the payment reference used for DANA, OVO, GoPay, or QRIS.

We keep those payment details to match transfers, confirm ownership, and reduce mismatched records. They are not used to profile you outside the account checks described in this policy.

Yes. On Android Chrome, iPhone Safari, and desktop browsers, we use cookies that keep the session stable, remember your settings, and help us spot repeated login attempts. They do not read your files.

We keep account records only as long as needed for service, request handling, dispute follow-up, and legal retention. After that, we delete them or remove direct identifiers where our systems allow it.

Yes. After you sign in, you can ask for a copy, a correction, or a deletion check through chat or email. We will verify the account first, then process the request when permitted.

Use WhatsApp for quick checks, live chat for in-site help, or email for written requests that need a record. Any access or eligibility question is handled only where local law permits.

Yes. Any access, sharing, or eligibility point follows local law and is available only where local law permits. If a rule changes, we keep the policy aligned with the applicable requirement.