Reference

Privacy Policy for Your aci303 Account

Our Privacy Policy explains what we collect when you open an aci303 account, use a mobile browser, or connect DANA, OVO, GoPay or QRIS.

Account recordsWallet activityDevice choicesContact requests
aci303 Privacy Policy for Your aci303 Account
PRIVACY CONTACT ROUTES

Get Privacy Policy Help Through Your Account

A clear contact path matters when a Privacy Policy question involves an account record or wallet reference. Start from the support contact shown after you sign in and include the email or phone detail attached to your account, the relevant payment rail and the date of the event. We use those details to locate the correct record without asking you to send a full wallet password or security code.

Team online

Account request

Ask us to locate a specific account record through the signed-in support path. Include your registered phone detail and the request type so we can check the right profile without exposing another person’s data.

Wallet question

For DANA, OVO, GoPay or QRIS data questions, provide the payment reference and date shown in your receipt. We can compare that reference with the account event while keeping your wallet PIN and one-time code private.

Access concern

If a browser or phone change affects your account access, tell us the device path and approximate sign-in time. We use that context to check security records and explain which Privacy Policy step applies.

DATA HANDLING DETAILS

What We Do With Account Data

Our Privacy Policy is applied at practical account points rather than kept as a general statement.

Account opening

When you create an account, we use the submitted contact detail and verification step to identify the correct profile. A clear account path helps us connect later requests to you rather than to an unverified browser session.

Device signals

A phone or desktop browser may send device type, session time and basic browser signals. We use these details to assess sign-in security and diagnose a page problem, not to treat a new device as automatic proof of identity.

Cookie choices

Cookies can keep a signed-in route working and remember choices made during a session. Your browser settings let you remove or restrict them, although doing so may require another account check before policy-related support can continue.

Payment records

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference helps us match a wallet event to the right account. We do not need your wallet PIN or one-time code to investigate that reference.

Retention requests

We keep account and payment records only for the period needed for account support, security checks and applicable legal duties. You can ask about a particular record’s retention through the contact route shown in your account.

Policy changes

If this Privacy Policy changes, we will place the revised wording on this page and identify the relevant update. For a correction, access request or deletion question, contact us with enough account detail to verify the request.

Privacy Policy Questions About aci303

These Privacy Policy answers address the account, wallet and device questions you may have before opening an aci303 account. Each answer points to a practical next step, from checking a QRIS reference to requesting a copy or correction of personal data. Access and eligibility remain dependent on local law.

The aci303 Privacy Policy covers account details, verification entries, sign-in events, device signals, cookies and payment references. It explains how we use those records for account security, wallet matching, support and applicable legal duties where local law permits.

We may store a payment reference, status, amount and timestamp connected with DANA, OVO, GoPay or QRIS. We do not need your wallet PIN or one-time code for a receipt check. Bank transfer and virtual account references follow the same account-matching purpose.

Use the support contact shown after you sign in and state that you want a copy of your account data. Include your registered phone detail and the records you mean, such as device events or a QRIS reference, so we can verify the request.

Yes. Send a correction request through the account support path and identify the field that is wrong. We may ask for an account verification step before changing contact details, payment references or other records connected with your profile.

The policy allows us to record a new device type, browser signal and sign-in time for security checks. If a phone change interrupts access, contact support with the approximate time and device path so we can examine the relevant session.

Retention depends on the purpose of the record, account support needs, security checks and applicable legal duties. You can ask about a particular DANA, OVO, GoPay, QRIS or bank reference through the signed-in contact route.

Yes. You can read this Privacy Policy before opening an account and use the contact route displayed on the site for a specific question. Please do not send a wallet PIN, one-time code or complete payment password with your message.