Reference

avanza55 Privacy Policy for Your Account

The avanza55 Privacy Policy explains how we handle account details when you open the lobby, verify your phone or use DANA, OVO, GoPay and QRIS.

Account clarityWallet contextCookie choicesSecurity steps
avanza55 avanza55 Privacy Policy for Your Account
CONTACT ROUTES

Privacy Help Beside Account Access

A clear contact route matters when you want to ask about the Privacy Policy, a cookie choice or a detail connected with your account. We keep policy questions separate from game or wallet troubleshooting, then connect the request to the account path that can check it. If your question follows a DANA receipt, QRIS status or phone-verification step, include only the reference needed to locate the issue. Where access is discussed, our reply uses the wording where local law permits and does not treat a payment record as permission to open an account.

Team online

Policy questions

Ask us which part of the Privacy Policy covers account details, cookies, retention or a request to view your record. We will point you to the relevant section and explain the next account step without asking you to post private details in an open message.

Wallet references

For a privacy question linked to DANA, OVO, GoPay or QRIS, share the payment reference through the account-help route rather than sending a full wallet password. We use the minimum context needed to match the request with your account status.

Access checks

If you cannot reach the policy page after phone verification, tell us your device type and browser path. We can help separate a privacy request from a login issue, while access remains subject to local law and the account details we can verify.

DATA HANDLING

What We Do With Your Policy Requests

Privacy work should be practical, so we explain the handling steps behind each request. We use account and device context to protect sign-in, connect a wallet reference with the correct account and…

Account security

Phone verification helps us distinguish an account request from an unknown sign-in attempt. We do not treat a DANA, OVO, GoPay or QRIS reference alone as proof that a person should receive account details or change security settings.

Cookie control

Cookies can affect session continuity, language display and the way a policy page opens on mobile or desktop. Your browser settings remain part of the choice, and the Privacy Policy explains which cookie purposes apply before you decide how to continue.

Payment records

A wallet or bank reference may be handled to connect a receipt with the right account status. This includes QRIS, virtual account and bank transfer context, but we ask for only the reference needed for the privacy request.

Retention periods

We keep account, security and request records for the periods described in the Privacy Policy, based on the purpose for holding them. When a period ends, handling follows the disposal or restriction process set out on this page.

Change requests

You can ask us to correct account details or explain how a record is used. We may request a phone-verification step before making a change, because confirming the account protects your details from an unrelated request.

Policy contact

For a Privacy Policy question about avanza55, use the account-help route and identify the subject, such as cookies, retention or access. We will keep the conversation on that subject instead of shifting it into a general lobby enquiry.

Privacy Policy Questions About avanza55

These answers address the privacy questions that arise before account access, during phone verification and after a wallet or browser step. They also show how to ask for a correction or clarification without sending more account detail than the request requires. If an access question involves your location, the outcome depends on local law.

The avanza55 Privacy Policy covers account details, phone verification, device and browser context, cookies, payment references and privacy requests. It explains how we use those details for account security, policy support and status checks involving DANA, OVO, GoPay, QRIS, bank transfer or virtual account steps.

Phone verification helps us confirm that a request comes from the correct account path. We may use it before showing, correcting or discussing account details, because a wallet reference or browser session by itself does not establish who should receive private account material.

Yes. The Privacy Policy covers the payment references we may use to match a receipt or status with an account, including DANA and QRIS, as well as OVO, GoPay, bank transfer and virtual account context. We ask for the smallest useful reference.

Use the account-help route and state that your request concerns a correction under the Privacy Policy. Tell us which account detail appears wrong, but do not send a password. We may confirm your phone-verification path before applying or discussing any change.

Cookies can influence session behaviour, saved page settings and how the policy page opens on your phone or desktop browser. The Privacy Policy explains their purposes, while your browser controls provide an additional way to manage cookie behaviour on your device.

Retention depends on the purpose for holding the record and the periods described in the Privacy Policy. Account, security and support-request details may follow different handling stages. Ask through the policy contact route if you need the period linked to a particular request.

Access or eligibility depends on local law. If you are checking the Privacy Policy from Indonesia, including Denpasar, our support route can explain the relevant account path and policy contact. A DANA, OVO, GoPay or QRIS option does not by itself determine eligibility.