Reference

Legal terms for Indonesian accounts

We keep the legal side of mahabet clear: access, account data, device logs, and change requests are written in plain language and apply only where local law permits.

Indonesia accountsLocal law firstMobile and desktopDANA / OVO / GoPay / QRIS
mahabet Legal terms for Indonesian accounts
REQUEST CHANNELS

Where to send a legal request

For data access, correction, or a blocked-account question, send the request from the account area so we can match it to your record quickly.

In-app chat Use chat when you need a fast legal check on access, correction, or a…
Email requests Email works well for longer requests, including data access and record retention questions.
Support form Use the form inside your account area when you need a written trail.
DATA AND ACCESS

How we handle data and access

Our policy handling starts with the record you create on mobile or desktop: contact details, login activity, device type, and the payment name you attach to the account.

Data handling

We collect only what we need to run the account, confirm your identity where local law asks for it, and answer disputes. That usually means your name, phone number, device logs, and the payment rail you used.

Cookies and sessions

Cookies keep the session open on Android Chrome, iPhone Safari, and desktop browsers, so you do not repeat steps every time you move between pages. We use them to remember language, login state, and security checks.

Account security

Protect your password, keep your phone number current, and use the same device when you request changes. If we detect a new browser or a new location, we may ask for one more check before we update the file.

Retention

We keep account records only as long as needed for access control, dispute handling, fraud checks, and legal duties. After that, we remove or anonymise what we no longer need in line with the policy.

Change requests

If your name, phone number, or payment rail changes, send the request from your logged-in account and include a short reason. We compare it with the stored record before we edit anything.

Contact path

For urgent access issues or a data request, use in-app chat first, then email if you need a written trail. Our team checks the same file across channels so you do not repeat the full story twice.

Legal questions customers ask us

These are the questions we hear most when you want to understand access, records, and change requests before opening an account. The answers below stay tied to local law, your login record, and the payment name you put on file. If something on your profile changes, the same support routes in your account are the place to ask us first.

Yes, if local law does not permit access or if the details on file do not match what we can verify. When the record and your contact number match, the account opens normally on mobile or desktop after the usual checks.

We keep the details needed for the account file: name, phone number, login history, device type, and the payment rail on record. We do not ask for extra data unless a legal check or support case needs it.

Send the request from the logged-in account and include the old and new details. We compare them against the stored record before we make any edit, so the change stays tied to the right file.

Cookies remember your session, language choice, and security state, which helps when you move between Android Chrome, iPhone Safari, and desktop browsers. You can clear them, but you may need to sign in again.

We keep records for as long as needed to manage access, settle disputes, check misuse, and meet legal duties. After that, we remove or anonymise the parts we no longer need.

Use in-app chat for quick checks, email for a written record, or the support form inside your account. Include your registered contact details so we can match the request without delay.

Yes. The name on the payment rail should match the account record, because that makes verification faster when you ask for a check, correction, or change request.