Reference

civic123 Privacy Policy For Your Account

civic123 Privacy Policy explains what we collect when you open an account, use DANA or QRIS, and move between the lobby and your wallet.

Account dataWallet referencesDevice choicesPolicy requests
civic123 civic123 Privacy Policy For Your Account
CONTACT THE RIGHT DESK

Privacy Questions Through Account Support

A clear contact path helps you act on this Privacy Policy without searching through unrelated pages.

Account data Ask us to correct a contact detail, phone verification record or other account field…
Wallet references For DANA, OVO, GoPay, QRIS, bank transfer or virtual account questions, send the payment…
Access requests If a sign-in or device session creates a Privacy Policy question, tell us which…
HOW WE HANDLE RECORDS

Account Security And Data Choices

We handle this policy area through practical account controls rather than vague promises.

Collection

We collect the details needed to open and maintain your account, such as contact data and phone verification status.

Cookies

Cookies can remember a selected setting, keep a page session working and show us which policy page was opened.

Account security

We use phone verification and session signals to reduce mistaken or unfamiliar access.

Payment records

DANA, OVO, GoPay and QRIS activity can create payment references, while bank transfer and virtual account steps can create matching…

Data retention

We keep account, support and payment-reference records only as long as they serve the stated service, security or legal purpose.

Your request

You can ask for access, correction or deletion of eligible personal data through the account support route.

Privacy Policy Questions About civic123

These Privacy Policy answers address the questions we expect you to ask before opening or using an account from Indonesia. They explain the practical difference between account details, device signals, cookies and payment references, as well as the route for requesting a change. If your situation is not covered, use the support path connected to your account and describe the record or access event you want us to check.

It covers account details, phone verification, sign-in and device signals, cookies, support messages and payment references. It explains why we use each category, how retention is assessed and how you can request access, correction or deletion where local law permits.

Our Privacy Policy does not ask you to provide a DANA or QRIS wallet password. We may receive a transaction reference or status detail needed to match an account action, while wallet credentials remain outside the support request you send us.

Phone verification helps connect account activity to the contact detail you supplied and supports an ownership check. We may use its status when you request a profile change or report unfamiliar access, but we do not treat verification as permission to collect unrelated contact data.

Use the account support route and ask for a personal-data access request. State the account contact detail, the category you want checked and any relevant date. We may verify ownership first, then explain which records can be provided under applicable local law.

Yes, you can request correction or deletion of eligible records through account support. Tell us exactly what appears wrong or what should be removed. Some records may need to remain for account security, payment matching or a legal duty, depending on the request.

We may record device type, browser signals and session events to keep account access consistent and investigate an unfamiliar sign-in. These signals are not a request for your private device files. Contact support if a device record looks incorrect or unexpected.

Cookies may remember page settings, support session functions or help us understand which policy content is opened. Browser controls can limit some cookies. If that affects sign-in or account pages, support can explain the related access step where access depends on local law.