Reference

acc4d Privacy Policy for Your Account Data

acc4d Privacy Policy explains how we handle the account details, wallet records and device signals needed when you access our Indonesia service.

Account recordsWallet statusDevice controlsPolicy requests

Explore Our Lobby Read FAQ

Open the Privacy Policy Before Account Access

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

Our Privacy Policy covers data you provide when opening an account, signing in, completing phone verification and contacting account support. It also covers technical data from the device and browser used to reach the lobby, plus records connected with DANA, OVO, GoPay, QRIS, bank transfer or

1
a virtual account. We use these details to maintain account security, identify payment status and respond to a policy request, not to add unrelated material to your profile. Cookies may remember a session or language choice, while security logs help us investigate unusual access. We retain
2
records for the period needed for these purposes and for applicable legal duties. Where local law permits, you can ask what we hold, request a correction or ask about deletion. Some records may remain when a legal, security or transaction reason requires retention.

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

CONTACT ROUTES

Browse Your Privacy Support Options

A clear contact path helps when you need to ask about Privacy Policy records rather than account play.

Account data request Ask what personal details we hold by using the account support path. Include your sign-in phone detail so we can match the request without exposing another account.

Wallet record question For DANA, OVO, GoPay or QRIS records, mention the relevant payment reference and date. We use those details to locate status data without asking for your wallet password.

Correction or deletion Request a change or deletion through the policy contact path. We explain which fields can be changed and which records may remain for security or legal reasons.

HANDLING DETAILS

Explore How We Handle Privacy Requests

Privacy work is handled through specific account events, not vague promises. We check the sign-in phone detail before discussing a record, separate cookie settings from payment history, and keep access logs for…

Data collected

We may hold your account contact details, phone-verification result, sign-in records and payment references. These fields help us connect a wallet status or account request to the correct profile.

Cookie choices

Cookies can keep a session active and remember a selected setting. Your browser controls whether they remain, while disabling some cookies may require another sign-in before account access.

Account security

We use phone verification and sign-in checks to reduce mistaken access. Never send a wallet password or one-time code when asking us about a Privacy Policy matter.

Retention period

We keep personal and transaction records only as long as needed for the stated service, security checks or legal duties. A deletion request receives an explanation when a record must remain.

Requesting changes

You can ask us to correct an incorrect name, phone detail or contact record through the account support route. We may verify ownership before applying the change.

Who to contact

Use the policy support path linked with your account and describe the exact record or cookie issue. For a DANA or QRIS question, add its payment reference and date.

Check Privacy Policy Answers Before Joining

These Privacy Policy questions cover the account steps Indonesian customers usually want clarified before opening an account. We keep each answer tied to a real data event, such as phone verification, device access or a DANA and QRIS payment reference. If your situation is different, use the policy support route and describe the record you want us to check.

It covers account details, phone verification, device and browser signals, cookies, support requests and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or a virtual account.

We use phone verification to confirm account ownership before access or a privacy request. It helps prevent us from sharing account data with someone who cannot establish control of the sign-in detail.

Yes. The Privacy Policy covers payment references and status details linked to DANA and QRIS, as well as OVO, GoPay, bank transfer and virtual account activity connected with your account.

You can request a correction through the policy support path. Tell us which field is wrong and include the sign-in phone detail; we may verify ownership before changing the account record.

Cookies may keep your session active or remember a setting. Browser controls let you remove or block them, although some account pages may ask you to sign in again afterward.

Where local law permits, you can ask about deletion through account support. We explain what can be removed and what may remain because of security checks, payment records or legal duties.

Use the policy support route connected to your account and describe the exact record involved. For wallet data, add the payment name, reference and date, but never send a password or one-time code.

acc4d Privacy Policy for Your Account Data

Browse Your Privacy Support Options

Explore How We Handle Privacy Requests

Data collected

Cookie choices

Account security

Retention period

Requesting changes

Who to contact

Check Privacy Policy Answers Before Joining

01 What does the acc4d Privacy Policy cover?

02 Why does acc4d need my phone verification detail?

03 Does the Privacy Policy cover DANA and QRIS records?

04 Can I ask acc4d to correct my account data?

05 How does the Privacy Policy treat cookies?

06 Can I request deletion of my acc4d data?

07 How do I contact acc4d about a privacy request?

Related Pages