Reference

Open atto1 Legal terms before access

atto1 puts Legal terms beside the account path so you can check access conditions, wallet handling and data choices before entering the lobby.

Policy accessAccount dutiesData choicesLocal-law wording
atto1 Open atto1 Legal terms before access
ASK OUR TEAM

Contact us about Legal access questions

A direct support route helps when a Legal question affects your account, identity check or wallet record. Contact us through the support route shown after you sign in, and include the phone number linked to your account plus a short description of the issue. We use those details to locate the correct record without asking you to send a password. If access is unavailable, keep the payment reference for DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity ready for the case review.

Team online

Account access

When a Legal access question blocks sign-in, use the account support path and provide your registered phone number. We can match the request to the correct account record and explain which verification step remains before access can continue where local law permits.

Wallet records

For a Legal question about a wallet or transfer record, share the payment reference and rail name, such as DANA, OVO, GoPay, QRIS, bank transfer or virtual account. We use that context to check status without requesting your password.

Policy changes

If you need clarification about a policy wording change, ask support from the signed-in account path and quote the section that concerns you. We will explain the relevant account effect and tell you what request details are needed for a follow-up.

RECORDS AND CONTROL

Protect your Legal choices and records

Legal handling depends on clear records and controlled account access. We use the phone verification step to connect requests with the right account, while transaction references help separate DANA, OVO, GoPay, QRIS…

Data requests

You can ask what account data is held by contacting support through the signed-in path. Include your registered phone number and the request you want handled. We may verify the account first so a data response is sent to the correct person.

Cookie choices

Cookies help keep your account session and Legal page functions working in your browser. You can adjust cookie controls in your device or browser settings, although disabling some cookies may affect sign-in continuity or the way policy pages load.

Account security

Keep your phone number private and never share a password in a support request. Our account path may require phone verification before access changes, wallet status checks or requests involving personal records can proceed.

Retention requests

If you ask how long a record is kept, contact us with the account reference and record type. We will describe the applicable retention reason and whether a request can be completed immediately or needs a required holding period.

Correction requests

Your name, phone number or account detail should remain accurate. Send a correction request through support with the field that needs changing. We may ask for a verification step before updating it, especially when it connects to wallet or access records.

Policy contact

For a Legal question about data, cookies, account access or policy wording, start with the support route connected to your account. State the subject clearly, and keep any DANA, OVO, GoPay or QRIS reference available when it is relevant.

Browse answers about atto1 Legal

These Legal answers cover the questions you may have before opening an account or requesting a change. They explain local access wording, account checks, personal data, cookies and the contact path for a clear next step. Read the relevant answer before sending documents or payment references, and use support when your situation needs an account-specific response.

Access depends on local law and your account circumstances. Check the Legal wording before opening an account, use the stated phone verification path, and proceed only where local law permits. We cannot replace local advice, so confirm your own eligibility before using account or wallet functions.

We may ask you to verify the phone number connected with your account before access changes, data requests or wallet record checks. Keep those details current and do not send a password through support. The check links the request to the correct account record.

Yes. Send a clear request through the signed-in support route, identify the account field or record concerned, and provide the registered phone number when asked. We may verify ownership first, then explain whether the change can be made and what happens next.

A wallet or payment record can include the rail name, account reference, status and transaction details needed for account administration and security checks. For DANA, OVO, GoPay, QRIS, bank transfer or virtual account questions, keep the payment reference ready.

Cookies can support the browser session and help the Legal page or account path function correctly. You can adjust cookie controls in your browser or device settings. Turning some off may affect sign-in continuity, so check the result before sending an account request.

Use the support route connected to your account and state whether the issue concerns access, data, cookies, a policy change or a payment record. Include only the requested details, never your password, and add a DANA, OVO, GoPay or QRIS reference when relevant.

The Legal wording applies across mobile browser and desktop access, but your device session may require phone verification again after a security change. Review the policy on your current device, and continue only where local law permits and your account details remain accurate.