Reference

atas4d Legal Terms For Your Account

atas4d sets out its Legal terms so you can see how account access, personal data, wallet checks and policy requests are handled before you open an account.

Account conditionsData handlingLocal-law access
atas4d atas4d Legal Terms For Your Account
POLICY CONTACT PATH

Get Legal Help Near Your Account

A clear contact path matters when a Legal question affects your login, wallet status or access decision. Sign in first where possible, then use the account support route so we can match your request with the correct record. Our team can direct questions about identity checks, payment receipts, policy wording and access that depends on local law.

Team online

Account access

If a Legal condition blocks your account, send the account identifier and the wording shown on screen through the support route attached to your login.

Wallet records

For DANA, OVO, GoPay, QRIS or bank transfer questions, include the receipt reference so our team can separate a policy check from a payment-status query.

Policy changes

To ask about a correction, deletion or policy clarification, use the same account contact path and describe the specific record or Legal clause involved.

DATA PRACTICE

Know How atas4d Handles Legal Records

We keep our Legal process practical: account details support access checks, payment records help us trace wallet activity, and security controls protect the account path.

Data use

We use submitted account details to confirm identity, connect policy requests with the right record, and assess whether access can continue where local law permits.

Cookie choices

Cookies can support sign-in continuity and page preferences. If your device clears them, you may need to repeat the account step before reaching Legal pages.

Account security

Keep your login details private and complete phone verification before account access. We may request matching details when a policy or wallet question needs checking.

Record retention

We retain relevant account, payment and contact records for as long as needed to address disputes, assess access and meet applicable Legal obligations.

Correction requests

If a name, phone detail or payment reference is wrong, contact us from the account path and identify the exact record so we can assess the requested change.

Account decisions

When access is paused or declined, we aim to explain the applicable condition and the next contact step, subject to local law and the available account record.

Answers Before You Open An Account

These Legal answers cover the questions we hear before account creation: access by location, personal data, wallet checks, cookies, corrections and contact steps. Read the relevant point first, then use the account route if your situation needs a record-specific response.

It covers account conditions, data use, cookies, security, record retention, payment checks and policy contact steps. Access or eligibility depends on local law and the terms shown for your account.

Access is available where local law permits and depends on local law. If your location or account details require a check, we may ask for phone verification before access continues.

DANA and QRIS references may be used to match a wallet event with your account. Keep the receipt reference available when asking us to clarify a policy or payment record.

A further check can arise when account details, phone verification or wallet ownership do not match. We use the available record to assess access and explain the next contact step.

Use the contact route shown after login, name the exact detail that needs correction, and provide the account identifier. We assess the request against the stored record and applicable Legal duties.

Cookies may support session continuity and page preferences. Clearing them can sign you out or require another login step, but it does not remove records retained for policy purposes.

Contact us through the support route attached to your account and include the decision wording, account identifier and relevant receipt reference. We can then direct the request to the correct policy record.