Reference

Your legal terms for Indonesia, in one place

We set out the rules for account access, data use, and request handling before you open the rest of the account area.

Data useAccess checksCookie controlRequest path

How local law shapes access

nagabet76 Service availability depends on jurisdiction. Users are responsible for checking local law before access.

Our legal position is simple: we collect only the account details needed to run login, verification, support, and request handling, and we keep those records tied to the region you choose. If access depends on local law, we say so before you proceed, and we do

1
not push you past that point. When a request touches deposits or withdrawals, the same rule set applies whether the rail is DANA, OVO, GoPay, or QRIS, because the payment context must match the jurisdiction. You can view the current version inside your account, and we
2
log changes so you know which wording applied when you opened it. Where local law permits, you may continue; where it does not, we stop the flow and ask you to use the contact paths listed here. Retention follows the same principle: we keep request logs
3
only as long as needed for security checks and dispute handling, then archive or remove them under our schedule.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

REQUEST CHANNELS

Where to send policy questions

When you need a change, we keep the contact paths simple: live chat for urgent access questions, email for written requests, and the in-account form for corrections that need a record.

Live chat Live chat runs every day from 08:00 to 23:00 WIB for access, data, or closure questions. Send your registered email and the exact page you are asking about, and we route it to the right team.

Email Email suits written requests for corrections, copies, or policy changes. Keep the subject clear, include your account email, and expect the reply to reference the same record used in chat.

In-account form Use the form inside your account when you want a traceable request about data use or access. It captures the time, device, and page path, which helps us answer without asking you to repeat the basics.

DATA AND ACCESS

How we handle records and requests

We keep the legal side practical: login records, device checks, and contact history stay linked to your account so we can verify changes without asking you to repeat the same details.

Data scope

We store the account email, contact number, and recent login history to handle access checks and policy requests. We do not ask for more than we need, and we keep each field tied to the same account record.

Cookie control

Cookies remember your session, device, and preferred language so the legal page and contact links load correctly on the next visit. You can clear them in your browser, then sign in again if the page asks.

Device security

On Android, iPhone, and desktop, we keep the same sign-in checks and logout path. If a device changes, we may ask you to confirm the email or phone number on file before we process a request.

Retention

We retain request logs and support history for a limited operational period, then archive or remove them under our schedule. That helps us answer disputes, trace changes, and show which policy version applied when you contacted us.

Change requests

For edits, correction, or deletion requests, use live chat or the in-account form and tell us exactly what should change. We work from the name, email, and timestamp on your account to avoid mistakes.

Regional access

If a question touches access, legality, or regional availability, we review it against the current wording and reply with where local law permits. That keeps the answer tied to your account and the region set on it.

What you can ask us about

These are the questions we hear most when you want to check the current policy, change account details, or ask why a request was paused. Each answer points you to the same record inside your account, so you can read the wording that applies to you and contact us without starting again. That keeps the process clear whether you are on mobile in Bandung or on desktop at home.

It covers account access, data use, cookies, request handling, and the contact paths we use when you ask for a correction or closure. If a section depends on local law, we say so before you proceed.

Yes. Use live chat, email, or the in-account form with the exact field you want changed. We match the request to your account record, then confirm the result in the same channel.

Access depends on local law and the region on your account. When a rule blocks a step, we stop the flow and point you back to the current wording rather than letting you guess.

You can open it on Android, iPhone, or desktop. The layout keeps the same sections, and the contact links stay visible so you can send a request without switching devices.

We keep support history and request logs for a limited period so we can trace changes and answer follow-up questions. After that, we archive or remove them under our retention schedule.

The legal area references DANA, OVO, GoPay, and QRIS when payment context matters. We use those names only to show the rails tied to your account and the region you selected.

Use the in-account form any time, then add the account email and the issue in a short line. Email stays open outside chat hours, and the team replies from the current record.

Your legal terms for Indonesia, in one place

Where to send policy questions

How we handle records and requests

Data scope

Cookie control

Device security

Retention

Change requests

Regional access

What you can ask us about

01 What does this legal page cover?

02 Can I ask for my data to be changed?

03 How do you decide if I can access the account area?

04 What device can I use to read this policy?

05 Do you keep my request history?

06 Which payment rails appear in the legal area?

07 How do I contact you after hours?

Related Pages