Reference

Open aba303 Privacy Policy Clearly

aba303 Privacy Policy explains how we handle the account details, wallet references and device signals used when you access our Indonesia lobby.

Account dataWallet referencesDevice controlsAccess depends on local law

Explore lobby Read FAQ

Read How Wallet Data Is Used

aba303 Service availability depends on jurisdiction. Users are responsible for checking local law before access.

Our Privacy Policy covers the data needed to open and protect your account, confirm phone ownership, process wallet activity and respond to account requests. We may record your contact details, verification results, login events, device and browser signals, approximate network details, support messages and payment references

1
linked to DANA, OVO, GoPay, QRIS, bank transfer or a virtual account. We use these records to provide account access, match a payment to the correct account, investigate an unusual login and answer a status question. We do not treat a wallet reference as permission to
2
use unrelated personal data. Where local law permits, we retain records only for operational, dispute, security or legal needs, then remove or anonymise them according to our retention process. The policy applies to access from Indonesia, including your phone or desktop connection in Yogyakarta, and eligibility
3
depends on local law.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

CONTACT OUR TEAM

Ask About Privacy From Your Account

A clear contact route matters when a data question affects your account or wallet status.

DATA HANDLING

Browse Your Privacy Controls With Clarity

Privacy choices are easier to manage when each record has a defined reason and route. We separate account security data from wallet references, use cookies for session continuity where enabled, and limit…

Account records

We use your phone number, account credentials and verification result to create and protect access. A clear phone verification step helps us distinguish an account request from an unverified device, especially when you switch from a mobile browser to desktop.

Payment references

For DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity, we keep the references needed to match a receipt or status request. We do not need your wallet PIN or full bank password to check that operational record.

Cookies and sessions

Cookies can keep your signed-in session and selected privacy choices available while you move through account pages. You can adjust browser cookie settings, although removing session cookies may require you to verify your phone again before access continues.

Device security

Browser type, operating system, network signals and login timing can help us identify unusual access. These signals may be compared with your normal account path, such as a phone login followed by a desktop session, to protect the account.

Retention requests

We retain records for account operation, payment matching, security checks, disputes or legal duties, where local law permits. When a retention reason ends, we remove or anonymise the record through our internal data process.

Your privacy contact

Use the support channel inside your account to request access, correction, deletion or an explanation of a data use. We confirm account control before responding, because sending private account data to an unverified contact could expose you.

Find Answers About Privacy And Access

These Privacy Policy answers focus on the account steps you are most likely to ask about before opening an account or checking a wallet status. We explain what data may be collected, how device access is handled and how to contact us from Indonesia. If your request depends on a legal right or eligibility rule, the outcome depends on local law.

It covers account details, phone verification, login and device signals, cookies, support messages, payment references and retention. The policy explains why we use each category, how it supports account access or wallet matching, and how you can request access or correction where local law permits.

Yes. We may keep a DANA or QRIS reference, receipt detail and status record needed to match activity to your account. We do not need your wallet PIN for that check. OVO, GoPay, bank transfer and virtual account references follow the same operational approach.

Your phone number supports account creation and verification, while browser, operating system, network and login-time signals help identify unusual access. These details can protect a session when you move from a mobile browser to desktop, without giving us your device contents.

Use the support channel displayed inside your account and describe the Privacy Policy request as access or correction. We confirm that you control the account, locate the relevant record and respond with the data we are allowed to provide under local law.

You can submit a deletion request through the account support path. We assess which records can be removed and which must remain for payment matching, security, disputes or legal duties. Where local law permits, data no longer needed is removed or anonymised.

Changing cookie settings can reduce session storage and may require another phone verification before account access continues. Cookies help remember a session and selected choices; they do not give us access to your wallet PIN, private files or unrelated device content.

Start with the support channel shown after you sign in, because it lets us verify the account before discussing private records. Include the request type, such as access, correction, deletion or retention, and refer to a receipt only when your question concerns wallet activity.

Open aba303 Privacy Policy Clearly

Ask About Privacy From Your Account

Browse Your Privacy Controls With Clarity

Account records

Payment references

Cookies and sessions

Device security

Retention requests

Your privacy contact

Find Answers About Privacy And Access

01 What does the aba303 Privacy Policy cover?

02 Does the Privacy Policy cover DANA and QRIS data?

03 Why does aba303 collect phone and device details?

04 How can I request a copy or correction of my data?

05 Can I ask aba303 to remove my account data?

06 Does changing browser cookies affect my privacy?

07 Where local law permits, who can I contact about privacy?

Related Pages