Reference

What Our Privacy Policy Covers

Our Privacy Policy explains how we handle the account details, device signals, and payment references tied to DANA, OVO, GoPay, and QRIS.

DANAOVOGoPayQRIS
nemod4d What Our Privacy Policy Covers
REQUEST CHANNELS

Reach Us About Privacy Changes

If you want a correction, a copy of the data we keep, or a request to limit use where the law allows it, we send it…

Email Send privacy requests to [email protected] with the account email, the change you want, and…
Live Chat Open live chat from the footer when you need a faster answer.
Daily Hours We answer privacy messages every day from 09:00-23:00 WIB.
KEEPING RECORDS SAFE

How We Protect Your Records

This policy is built around the data we need, not a broad sweep of your device. We keep account, cookie, and payment-reference data for access, security, and record matching; then we limit…

Data Scope

We collect account details, contact details, and device signals only when they help us open the account, keep it working, or answer a privacy request. Extra fields stay out unless a legal or security check needs them.

Cookie Use

Cookies remember session state, language, and sign-in details across phone and desktop. If you clear them in your browser, the next visit starts fresh and may ask you to verify again.

Account Checks

For a sensitive change, we may ask for a one-time code, recent activity, or wallet confirmation before we update stored data. That protects the account from edits you did not request.

Retention

We keep support threads, payment references, and security logs only as long as we need them for service, legal duties, or dispute handling. After that period, access is restricted or the data is removed where allowed.

Change Requests

If your name, contact details, or wallet reference changes, send the request through support and include the account email. We will confirm what can be edited right away and what needs another check.

Contact Route

For privacy questions, use email or live chat and say whether the issue is cookies, account access, or stored payment data. We route it to the right team without making you start from zero.

Common Privacy Questions Answered

If you want the short version, this policy covers what we collect, why we keep it, and how you can ask for a correction or copy. We also explain cookies, account security, and how payment references are matched with DANA, OVO, GoPay, and QRIS. When local law allows a request, we handle it after account verification and keep the same thread open so the answer stays clear.

We collect the contact details, account name, device signals, and payment references needed to open the account, match activity, and answer support requests. We do not ask for extra fields unless a security or legal check requires them.

Yes. Cookies help us remember your session, language, and sign-in state on phone or desktop. If you clear them, the next visit may ask for another verification step before the account opens again.

We keep the reference fields needed to match each wallet action and answer a later question about it. We do not store more payment data than needed for reconciliation, security, and record keeping.

We keep data only for the time needed to run the account, meet legal duties, and handle support or record questions. After that, we limit access or remove it where local law allows.

Yes. Send the request through email or live chat, include the account email and the change you want, and we will verify the profile before we update any stored field.

Access is limited to staff who need it for account handling, security checks, payment matching, or support. We do not open records broadly, and every request is handled case by case.

If a request cannot be completed in your region, we will say what we can do and what we cannot do. We only provide access or changes where local law permits.