Reference

atas4d Privacy Policy For Your Account

Our Privacy Policy shows how atas4d handles your account details, device signals and payment records when you use DANA, OVO, GoPay or QRIS.

Account clarityWallet recordsCookie choicesRequest support

Browse Our Lobby Read FAQ

How DANA And QRIS Data Is Used

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

Our Privacy Policy applies when you create an account, complete phone verification, sign in, contact support or submit a wallet transaction. We may receive the account name, phone number, verification result, device details, login time, selected payment rail and transaction reference needed to match a deposit

1
or withdrawal request. DANA, OVO, GoPay and QRIS can produce reference details that help us check status without asking you to send a wallet password. Bank transfer and virtual account records may include a bank name such as BCA, BRI, Mandiri or BNI, together with a
2
reference and amount. We use these records to operate account security, answer payment-status questions and meet legal requests where local law permits. We do not ask for your wallet PIN through the account support path.

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

CONTACT YOUR WAY

Get Privacy Help Through Your Account

A clear contact path matters when a privacy request concerns a login or wallet record. Sign in first where possible, then use the account support route so we can match your request with the correct profile without exposing details in a public message.

Team online

Account support route

Ask about a stored phone number, verification record or device sign-in from inside your account. We may request account details to confirm that the privacy request comes from you.

Wallet status check

For DANA, OVO, GoPay, QRIS or bank transfer questions, include the transaction reference rather than a PIN. This lets us trace the record while keeping secret wallet credentials private.

Receipt request

If a payment receipt appears incomplete, send the reference through the account contact path. We use the submitted details only to locate the relevant record and respond to your request.

DATA HANDLING

What Our Privacy Process Covers

We keep the Privacy Policy practical: it connects each data type with a real account action. The sections below explain how we handle sign-in records, browser storage, wallet references, retention and requests…

Account details

We use your phone number and submitted account details to create the profile, complete phone verification and protect sign-in. We do not need your DANA, OVO or GoPay PIN for these account steps.

Device signals

When you sign in from an Android browser, iPhone browser or desktop, we may record device and session signals. These help us notice unusual access and investigate a security request.

Cookies

Cookies can keep a session active, remember selected settings and help us understand which account page caused a technical issue. You can manage browser cookie controls, though some sign-in functions may then change.

Payment references

A QRIS receipt, virtual account reference or bank transfer record can be used to match a wallet event with your account. We use the reference for checking, not for collecting secret wallet credentials.

Retention period

We retain account, security and transaction records only for the period needed for account operation, dispute handling, security checks and legal duties. When a record is no longer needed, our process removes or restricts it.

Change requests

You can ask us to correct inaccurate profile details or explain a recorded transaction through the account support path. We may verify your identity before changing data linked to your account.

Privacy Policy Answers For atas4d

These Privacy Policy answers cover the searches we hear most often before an account is opened. Each answer points to the account, device or payment detail involved.

It covers account details, phone verification, sign-in activity, device signals, cookies, payment references, support messages, retention and requests to correct or explain stored data.

Yes, we may store a transaction reference, status and related account record for DANA or QRIS. We do not ask for your wallet PIN, password or other secret credential.

Phone verification helps connect the account to the correct contact detail and helps us investigate unusual sign-in activity. We may use the verification result when handling an account privacy request.

Yes. Send a correction request through the account support route, describing the inaccurate field. We may ask you to confirm account ownership before changing phone, profile or transaction-linked details.

On an Android or iPhone browser, cookies can keep your session and selected settings available. Browser controls can remove them, but sign-in or account continuity may work differently afterward.

We retain payment and account records for the period needed for operation, security checks, disputes and legal duties. The applicable period can depend on the record and local law.

You can ask through the account contact path how a specific record is used and whether it is shared for a stated operational or legal purpose. We verify the request before giving account-linked details.

atas4d Privacy Policy For Your Account

Get Privacy Help Through Your Account

Account support route

Wallet status check

Receipt request

What Our Privacy Process Covers

Account details

Device signals

Cookies

Payment references

Retention period

Change requests

Privacy Policy Answers For atas4d

01 What does the atas4d Privacy Policy cover?

02 Does Privacy Policy data include DANA or QRIS details?

03 Why does atas4d ask for phone verification?

04 Can I request a correction to my account data?

05 How does the Privacy Policy handle cookies on mobile?

06 How long does atas4d keep payment records?

07 Can I ask who receives my personal data?

Related Pages