Reference

Legal terms for your task55 account

Legal clarity starts with the account steps you can see: task55 sets out access conditions, phone verification, wallet checks and the records used to protect your account.

Account termsData and cookiesLocal-law accessWallet checks
task55 Legal terms for your task55 account
CONTACT THE POLICY TEAM

Get help with Legal account questions

A clear contact path matters when a Legal question affects your account or wallet status.

Account access If phone verification or account entry stops at a Legal check, contact us from the account help path. Include the displayed message and the device route you used, such as mobile browser or desktop.
Wallet status For a DANA, OVO, GoPay, QRIS, bank transfer or virtual account question, share the reference and time shown in your account. We use those details to trace status without asking for your private PIN.
Policy requests To ask about data access, correction or deletion, use the policy contact route linked from your account. Tell us which record or clause concerns you, and we will explain the next step under the applicable Legal terms.
HOW WE HANDLE RECORDS

Inside task55 data and security practice

Legal handling is practical: we use account details to identify your access, connect wallet references to transactions, and investigate requests you send through support.

Account details

We use the details you enter, including your phone number, to create and protect account access. Phone verification comes before account entry, helping us connect a request to the correct account without exposing another person’s records.

Payment references

A wallet or bank record may contain a DANA, QRIS, OVO, GoPay, BCA, BRI, Mandiri or BNI reference. We use the reference to check status and destination, not to request your wallet PIN or online-banking password.

Cookies

Cookies can retain a session choice, support sign-in protection and help us understand whether a page request is working. You can manage browser cookie settings, though removing them may require you to verify your account again.

Account security

Keep your phone, password and wallet credentials private. If an account action looks unfamiliar, stop using the affected session and contact us through the signed-in support route so we can check the access record.

Record retention

We retain account, payment and support records only for the period needed for stated operational, dispute and legal purposes. When a retention reason ends, handling follows the deletion or anonymisation process available under the applicable Legal terms.

Request changes

You may ask us to access, correct or remove personal records by using the policy contact path. Describe the requested change and provide enough account detail for verification; we will explain any restriction required by local law.

What to ask before opening task55

These Legal answers cover the points most often raised before account opening: local access, verification, payment records, cookies, retention and contact requests. Read the relevant answer before you enter account details or connect a wallet. If your circumstances are unusual, use the policy contact path shown in your account and include the exact clause or status message.

Access depends on local law and the location connected to your account. Where local law permits, you can follow the displayed account steps, complete phone verification and read the applicable terms before entering the lobby or using a wallet-linked transaction.

Phone verification helps connect account access to the correct person and helps us investigate unusual sign-in or wallet activity. Complete it before account entry as shown. If the code fails, contact support with the error message, not your password.

We use the transaction reference, amount and status supplied by the payment route to check a DANA or QRIS action. The record supports reconciliation and account support. We do not need your wallet PIN, banking password or full private security code.

Yes. Send an access or correction request through the policy contact path linked in your account. State which record needs attention and provide account details for verification. We will explain the response process and any restriction that depends on local law.

We keep account, payment and support records for the period needed for account administration, payment checking, disputes and applicable legal duties. The exact period can differ by record type. After that purpose ends, the record follows deletion or anonymisation handling.

Cookies can keep a browser session active, remember selected settings and support sign-in protection. They may also help us identify a failed page request. You can change browser settings, but removing cookies may trigger phone verification when you return.

Use the policy contact route displayed in your account and quote the clause, page heading or account message you are asking about. We can explain its practical effect, identify any related wallet step and record a request to correct your details.