Reference

CINTAWD Privacy Policy For Your Data

CINTAWD Privacy Policy explains what we collect, why we use it and how you can request access or changes to your details.

Account dataWallet recordsDevice accessPolicy requests
CINTAWD CINTAWD Privacy Policy For Your Data
REQUEST PATHS

Get Help With A Privacy Request

A clear request path helps you deal with a data question without repeating your account story. Use the support link connected to your account and include the phone number or account detail needed to locate the record. We may ask for a phone verification step before discussing private data, and we keep payment receipts separate from the request until your identity is checked.

Team online

Account support link

Send an access, correction or deletion request through the support route connected to your account. Include the relevant phone detail so we can locate the correct CINTAWD record.

Cashier status trail

If your privacy question concerns DANA, OVO, GoPay or QRIS, mention the receipt and status shown beside the cashier path. We use those references to investigate without exposing unrelated records.

Device access check

For a phone or browser concern, tell us which device path was used and whether the issue appeared before or after login. We can then separate cookie data from account data.

DATA CONTROLS

Protecting Data From Login To Lobby

We keep this Privacy Policy practical by linking each data use to an account action, payment status or security need.

Account collection

We collect details needed to create and maintain your account, including contact data and verification status. We do not ask for unrelated personal details merely because you browse the lobby.

Wallet matching

A DANA, OVO, GoPay or QRIS reference can be kept with the related account action so we can match a receipt, check a pending status and answer your request accurately.

Cookie choices

Cookies may retain necessary session settings and device preferences. Clearing them can require you to sign in again, but it does not automatically remove account records held for security or legal needs.

Login protection

Phone verification and device signals help us identify unusual access before we discuss private account details. If a login looks unfamiliar, support may request an additional account check.

Retention approach

We retain records for the period needed to complete the stated purpose, resolve payment or access questions and meet applicable legal requirements. When no valid need remains, we assess removal.

Change requests

You can ask us to access, correct or remove eligible data through the support route. Tell us the requested change clearly; we may verify your phone before acting on it.

Privacy Policy Answers For Your Account

These answers focus on the questions you may have before opening an account or sending a data request. We keep the examples tied to the actual account, device and payment records used across CINTAWD, so you can understand what happens at each step.

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

Phone verification helps us confirm account ownership before access is granted or private data is discussed. It also helps separate your request from an unfamiliar login or device.

Yes. The policy covers QRIS receipt and status references when they are connected to your account action. We use them to match a request and investigate a payment status.

Use the support link connected to your account and ask for access to your personal data. Include the relevant phone detail, then complete any verification needed before release.

Yes, you can request a correction through the same support path. Identify the incorrect account detail and the replacement clearly; we may verify your phone before updating the record.

Retention depends on the purpose, payment or access question and applicable legal requirements. We assess records for removal when the original operational or legal need no longer applies.

Access and related processing depends on local law. Where local law permits, the policy supports requests about account, device, cookie and wallet data through our support route.