Reference

Open dtg288 Legal terms before access

dtg288 sets out its Legal terms before you open an account, including eligibility, account checks, wallet records and requests about your data.

Account termsData requestsLocal-law access
dtg288 Open dtg288 Legal terms before access
CONTACT ROUTES

Reach support about a Legal request

A clear contact path helps when you need to ask about Legal wording, account access or a wallet record. Start from the signed-in account contact route so we can match your request to the correct account. If login is unavailable, use the contact path displayed on the access screen and include only the details needed to locate the issue.

Team online

Account request

Send a Legal question from your account contact route after phone verification. We can connect the request to your account record without asking you to repeat unrelated wallet details.

Payment record

For a DANA, OVO, GoPay, QRIS or bank-transfer question, include the receipt reference and account name. We use those details to check status without requesting your wallet password.

Access concern

If the Legal page or login step does not open, use the contact route shown on the access screen. Tell us your device type and the page step where the issue appeared.

DATA PRACTICE

Protect your account under Legal rules

Legal handling is tied to practical account work: phone verification, payment matching, security checks and support correspondence.

Data use

We use account details to provide access, verify ownership, match payment references and respond to Legal requests. We do not need your DANA, OVO or GoPay password for a support check.

Cookie choices

Cookies can support sign-in continuity, page settings and security checks. Your browser controls can clear them, although removing required cookies may affect the Legal page or account access step.

Account security

Phone verification helps connect an account request to its owner. Keep your sign-in details private, and contact us through the account route if an access attempt was not yours.

Record retention

We retain account, payment and support records for the periods described in the current Legal wording. A retention request should identify the account and the record category involved.

Policy changes

When Legal wording changes, we publish the revised text on this page and show its effective date. Check the page before opening an account or continuing after a material change.

Change requests

Ask us to correct eligible account data through the signed-in contact route. Include the field needing correction and a reason, while leaving out wallet passwords and unnecessary identity details.

Browse Legal answers before you join

These Legal answers address the questions we expect before account creation: what the wording covers, how data requests work, and how local access affects your next step. If your question concerns a particular account or payment record, use the support route rather than sending sensitive wallet credentials.

The Legal notice covers account creation, access conditions, phone verification, payment records, data handling, cookies, policy changes and contact routes. Read the current page before completing your account step.

Yes. Access and eligibility depend on local law. The Legal wording applies where local law permits, so check the current notice before opening an account or using account services.

You can request correction of eligible account details through the signed-in contact route. State the field and reason clearly, and do not include your DANA, OVO or GoPay password.

Legal payment records may include DANA, QRIS, OVO, GoPay, bank transfer or virtual account references. We use the reference to check account activity and support requests, not to request wallet passwords.

Use your browser controls to clear or manage cookies, then contact us through the account route if a required sign-in or security step changes. The current Legal page explains their stated purpose.

Use the contact path shown on the access screen and provide your device type, account identifier and the step that failed. We can then check whether the issue concerns access or local-law eligibility.

Send the request through the signed-in account contact route so we can connect it to the correct record. For payment questions, add the receipt reference and omit private wallet credentials.