Reference

AUDI108 Privacy Policy For Your Account

AUDI108 Privacy Policy sets out what we collect, why we use it and how you can ask about your account records.

Account clarityWallet record careCookie choicesRequest path
AUDI108 AUDI108 Privacy Policy For Your Account
CONTACT ROUTES

Three Privacy Policy Help Paths

A clear contact route helps when a Privacy Policy question concerns your login, wallet record or device session. Start from the account support path and describe the exact issue rather than sending payment credentials in an open message. We can then match your request with the relevant account step, receipt reference or security event while keeping the discussion focused on your personal data.

Team online

Account data request

Ask about the personal details linked to your account through the account support path. Include your account identifier, but do not send a password, wallet PIN or full payment credential.

Wallet record query

For DANA, OVO, GoPay, QRIS, bank transfer or virtual account records, provide the transaction reference and date. We use those details to locate the relevant entry without requesting unnecessary wallet access.

Security concern

If a phone, browser or login event looks unfamiliar, contact us through the account route and describe the device path. We can review the security event and explain the next account step.

HANDLING YOUR DETAILS

Six Ways We Apply This Privacy Policy

The Privacy Policy is useful when you want to understand the practical handling behind an account request.

Data collection

We collect details you submit for an account, such as contact information and phone verification data, plus operational records created during login or a wallet status check. We avoid asking for unrelated personal details.

Cookie controls

Cookies and similar device markers can help remember a session and protect account access. Your browser settings provide a way to manage them, although changing settings may affect sign-in continuity or policy prompts.

Account protection

Phone verification before account access helps connect a login to the correct account. We may review device type, sign-in timing and unusual access signals when checking a security question.

Payment records

A DANA, OVO, GoPay or QRIS reference helps us match a wallet event, while bank transfer and virtual account details support reconciliation. We do not need your wallet PIN to investigate a receipt.

Retention approach

We keep account, security and transaction records only for operational, dispute-handling or legal reasons described by the Privacy Policy. When a record is no longer needed, our handling follows the applicable retention process.

Change requests

To request a correction, access copy or clarification, contact us through the account support path with enough detail to identify the record. We may confirm your identity before changing or disclosing personal data.

Privacy Policy Questions Before Account Access

These Privacy Policy answers address the questions you may search before opening an AUDI108 account. They cover what is recorded, how wallet references are handled, what happens on a mobile device and how to ask for access or correction. Where an eligibility or access question arises, the answer depends on local law.

It explains how we handle account details, phone verification, device signals, cookies, wallet references and support messages. It also describes retention, security checks and the process for requesting access or corrections.

DANA and QRIS references help us match a payment status, receipt or reconciliation question to your account. We use the reference for that operational purpose and do not need your wallet PIN.

Yes. The Privacy Policy covers OVO and GoPay references in the same way as other supported wallet records. We may use a date, amount reference or status detail to investigate your account query.

We may record device type, browser session details, sign-in timing and security signals connected with access. These details help us investigate an unfamiliar login while keeping the account and phone verification path connected.

Use the support path connected to your account and request access to your personal data. Include your account identifier and a clear description; we may verify your identity before preparing a response.

Yes. Send a correction request through the account support route and identify the detail that needs changing. We may ask for confirmation before editing contact, verification or transaction-related records.

Yes. Any access, disclosure, deletion or eligibility request depends on local law. We assess the request, confirm account ownership where needed and explain the available result through the stated contact path.