Reference

Privacy Policy for at866 Accounts

Our Privacy Policy explains how we collect, use and protect your account details when you open at866 from Indonesia.

Account dataWallet recordsCookie choicesSecurity steps
at866 Privacy Policy for at866 Accounts
CONTACT ROUTES

Privacy Policy Help Through Support

A direct support path helps you act on this Privacy Policy without sending sensitive wallet details to the wrong place.

Account message Send a Privacy Policy request from the signed-in account area when possible.
Wallet status For a QRIS, bank transfer or virtual account record, include the reference shown in…
Access check If a phone verification step blocks your request, tell us whether you used mobile…
DATA PRACTICES

Six Ways We Handle Your Data

We keep this Privacy Policy practical by linking each data use to an account action you can recognise.

Registration details

When you open an account, we collect the details needed to create your profile and provide access. A registered phone helps us distinguish your account from another request, while incomplete or inconsistent details may require a further confirmation step.

Phone verification

Phone verification is an account-security control, not a request for your wallet password. We use the verification result to confirm access attempts and to help prevent another device from changing account details without the required confirmation.

Payment references

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference can show that a payment event belongs to your account. We use status and reference data for reconciliation, support checks and dispute handling rather than collecting unnecessary wallet credentials.

Cookies and devices

Cookies may remember session settings, while device and browser signals help us identify unusual login behaviour and diagnose page errors. You can manage available cookie choices in your browser, although some account functions may need session cookies to work.

Retention requests

We keep personal data only as long as it supports the stated account, security, dispute or legal purpose. You may ask what we hold, request a correction or ask about deletion; where a record must remain, we explain the reason and scope.

Privacy contact

Send a privacy request through the signed-in support route, using your registered phone or account reference for verification. We check identity before discussing personal data and respond with the available action, including access, correction, restriction or deletion where applicable.

Privacy Policy Answers for at866

These Privacy Policy answers focus on the account and data questions you may have before using at866 in Indonesia. Each response points to a practical action, from checking cookies to requesting a copy of account data. If your question concerns a specific DANA, QRIS or verification event, include the account reference through the signed-in support path so we can investigate without exposing sensitive credentials.

It covers data linked to registration, phone verification, sign-in, device signals, cookies, support messages and payment references. It explains why we use each category, how we protect account access, how long records may remain and how you can request access or correction.

We use DANA and QRIS references, status details and related account records to match a payment event and answer support requests. We do not need your wallet password for this process. Send only the reference visible in your account history when asking for a check.

Yes. Use the signed-in support route and identify the account with your registered phone or account reference. We verify that the request belongs to you, then explain which data can be provided, the format available and any reason a record cannot be released.

Contact support from the account area and state which detail is inaccurate. We may ask for a phone verification step before changing account data. For a wallet or bank transfer record, provide the transaction reference so we correct the relevant event instead of changing unrelated records.

Yes. Cookies can maintain a sign-in session, remember selected settings and help diagnose page performance on a mobile browser. You can adjust browser cookie controls, but blocking required session cookies may interrupt account access or force another login.

We retain account, security and payment-reference data for the period needed to operate the account, investigate disputes, protect access and meet applicable duties. When a record no longer serves those purposes, we remove or anonymise it under our retention process.

You can submit a deletion request through signed-in support. We verify your identity and check whether the data must remain for security, dispute handling or legal duties. If removal is possible, we take the applicable action and explain any records that must be retained.