Reference

Privacy Policy for Your atm4d2 Account

Our Privacy Policy explains how we handle the account, device and wallet details you provide when you use atm4d2.

Account clarityWallet statusLocal access
atm4d2 Privacy Policy for Your atm4d2 Account
HELP WITH PRIVACY

Privacy Questions Through Your Account Path

A clear contact route matters when you want to ask what data we hold or why a wallet record is attached to your account. Start from the account support path and describe the request in plain English, using the phone number or account reference connected with your access. We may ask for a verification step before discussing private account data. That protects you when a login or wallet status stalls, including a receipt linked to QRIS or a bank transfer.

Team online

Account request

Use our account support path to ask for a copy, correction or deletion request under this Privacy Policy. Include your account reference and the email or phone detail connected with access, but do not send a password or full wallet credentials.

Wallet record

If a DANA, OVO, GoPay or QRIS entry looks unfamiliar, tell us the date, amount reference and displayed status. We use those details to locate the relevant record without asking you to share a wallet PIN or one-time code.

Access concern

When your account opens on mobile but a privacy request needs checking, mention the device path and sign-in time. We can compare account activity with the support message and request an identity check where local law permits.

DATA HANDLING

What We Keep Around Your Account

We keep this Privacy Policy practical by linking each data use to an account task: verification, sign-in protection, payment matching, support or legal recordkeeping.

Account details

We may hold the name, phone number, email address and verification result you provide during account access.

Device signals

A browser or mobile device can send session time, operating details and security signals when you sign in.

Cookies

Cookies or similar storage can retain a session choice and help us understand which account page was opened.

Payment matching

Payment records can include a rail name, reference, amount, status and time.

Retention controls

We retain account and payment records for the period needed for account safety, dispute handling or legal duties.

Change request

To request access, correction, restriction or removal, contact us through the account support path with the subject Privacy Policy request.

Privacy Policy Answers for Indonesia

These Privacy Policy answers address the account questions you may have before opening access or while checking a wallet record. We keep the route tied to your account so a request about device activity, phone verification or payment matching can be handled with the right context. Access depends on local law.

The atm4d2 Privacy Policy covers account details, phone verification, sign-in and device records, cookies, payment references and support messages. It explains why we use each category, how long we may retain it and how you can request access or correction where local law permits.

Yes. The Privacy Policy covers payment records connected with DANA, OVO, GoPay and QRIS, including a reference, status and time used to match activity with your account. We do not need your wallet PIN or one-time code to check a receipt.

We use the phone number and verification result to connect account access with the person making the request and to reduce unusual sign-ins. If you ask about that record, we may repeat an identity check before sharing private account details.

You can ask for a copy or correction through the account support path by naming the Privacy Policy request and providing your account reference. We may need to confirm your identity, then explain what can be supplied or corrected where local law permits.

We keep account, device and payment records only while they serve account safety, receipt checks, dispute handling or legal duties. A DANA, QRIS, bank transfer or virtual account reference may remain for that purpose, after which we remove, anonymise or restrict it.

You can manage cookies and similar browser storage through your mobile or desktop settings. Some account functions may then ask you to sign in again or may not remember a session choice. The Privacy Policy still applies to records collected for account access.

Use the account support path and include your account reference, the request type and any relevant date. For a wallet concern, add the displayed rail and status, such as OVO or QRIS. Do not send passwords, wallet PINs or one-time codes.