Reference

delta575 Legal: Clear Terms Before Access

delta575 Legal sets out how account access, personal data, wallet records and policy requests work before you enter the lobby.

Access depends on local lawPhone verificationWallet record clarity
delta575 delta575 Legal: Clear Terms Before Access
POLICY HELP

Contact Us When Legal Questions Stall

A clear support route matters when you need a policy answer rather than a lobby explanation.

Account request Use the account support route to ask about Legal terms, access conditions or a personal-data request. Include your account phone detail so we can connect the request to the correct record without asking you to post private data in an open chat.
Wallet record For DANA, OVO, GoPay, QRIS, bank transfer or virtual account questions, attach the relevant reference and date. We can then check the account record and explain which policy step applies without treating a payment label as proof of identity.
Access concern If access is unavailable, tell us the device path, account phone detail and the message shown on screen. We will explain whether the issue relates to verification, a policy condition or local eligibility, which depends on local law.
DATA PRACTICE

Protect Your Data Through Clear Requests

Legal treatment of account data should be understandable in practical terms. We use account details, verification records, device signals and wallet references to operate access, check security events and respond to policy…

Data handling

We handle the details you submit for account access, phone verification, wallet records and policy support. A request is assessed against the relevant account record, so accurate contact details help us avoid attaching a Legal response to the wrong account.

Cookies

Cookies can keep a signed-in session active and preserve necessary browser settings during account access. If you clear or block them, the page may ask you to verify again. Browser controls do not erase records already held for a policy request.

Account security

Phone verification is required before account access, and we may compare account details with security signals when a request looks unusual. Never send a passcode through support. If your device changes, describe that change in the account support request.

Record retention

We retain account, verification and transaction records only for the period needed for service operation, security checks, dispute handling or applicable legal duties. When a retention reason ends, handling follows the deletion or restriction process available under the applicable policy.

Correction request

You can ask us to correct an inaccurate account detail through the account support route. State the field that needs changing and provide the matching phone detail. We may request another verification step before changing information tied to wallet or access records.

Policy contact

For a Legal request about access, data use, cookies, retention or account security, contact us through account support and label the subject clearly. We will review the request against the applicable policy and explain the next step in writing.

Browse Answers About delta575 Legal

These Legal answers address the questions you may have before opening an account or requesting a policy change. They cover eligibility, verification, data handling, cookies, wallet records and contact steps for Indonesian account holders. Where a question depends on location or eligibility, the answer remains subject to local law and the access conditions shown for your account.

delta575 Legal covers account access, phone verification, personal-data handling, cookies, security records, wallet references, retention and policy requests. It also explains that access depends on local law, so you should check the applicable condition before opening or using an account.

Access is available only where local law permits and depends on local law for your location. We may require phone verification before account access. If the screen shows an eligibility or verification message, use account support and include the device path and account phone detail.

Phone verification helps us connect an access request with the correct account record and reduce mistaken or unauthorised changes. It may also be used when you request a correction involving DANA, OVO, GoPay, QRIS, bank transfer or virtual account history.

Wallet records can include a payment label, reference, date and account status for DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. We use those details for account operation, security checks and dispute handling, subject to the applicable policy.

Send a request through the account support route and identify the detail you want corrected, restricted or removed. Include your account phone detail, but do not send a passcode. We may verify ownership before changing data connected to access or transaction records.

Yes. Cookies can maintain a signed-in session and preserve necessary browser settings during account access. You can manage them through your browser, but clearing or blocking cookies may require another verification step. Browser controls do not automatically remove account or policy records.

Use the account support route for questions about Legal, data handling, retention, access conditions, cookies or security. For a wallet matter, add the payment reference and date. We will match the request to the relevant account record and explain the next step.