Reference

cika4d Privacy Policy For Your Account

cika4d Privacy Policy explains what we collect when you open an account, use the mobile lobby, or connect DANA, OVO, GoPay and QRIS.

Account dataWallet recordsCookie choicesSecurity checks
cika4d cika4d Privacy Policy For Your Account
CONTACT YOUR WAY

Policy Help Beside Account Support

A clear contact route lets you ask about Privacy Policy matters without explaining your entire account history. Use the support path connected to your account when a wallet receipt, phone verification or cookie choice needs clarification. Include the email or phone linked to your account and the relevant DANA, OVO, GoPay or QRIS reference, but never send a password or security code. We use those details to locate the right record and keep the conversation focused.

Team online

Account contact

Ask about the Privacy Policy through the account support path. We may request your registered phone number so we can confirm that the data request comes from the account holder.

Wallet record check

For a DANA, OVO, GoPay or QRIS question, share the transaction reference and date rather than private wallet credentials. We use the reference to trace status without asking for your wallet PIN.

Security concern

If a login alert or phone verification does not match your activity, contact us through the same support route. We can place the request into a security check and explain the next account step.

DATA HANDLING

Six Practical Privacy Controls We Apply

Privacy is handled through specific account routines rather than a broad statement. We separate sign-in details from wallet references, limit internal access to records needed for a support or security task, and…

Collection

We collect details you provide during account opening, including a phone number for verification. We also receive technical signals such as device type and session activity when you reach the lobby from a mobile browser.

Wallet matching

DANA, OVO, GoPay and QRIS references help us match a wallet action to the correct account record. We do not need your wallet PIN or password to investigate a receipt or status question.

Cookie controls

Cookies can remember your selected preferences and help maintain a session on your browser. You can clear them through browser settings, although doing so may require you to repeat account verification.

Account security

Phone verification and device signals help us identify an unusual sign-in before account details are shown. If the device changes, we may ask you to repeat the account step for protection.

Retention

We retain account, wallet and support records only while they serve an operational, security or legal need. When that need ends, our process removes the record or keeps it in a form that does not identify you.

Change requests

To request a copy, correction or deletion of personal data, contact support from the registered account route. Tell us the request type and linked phone number so we can verify ownership before acting.

Privacy Policy Answers For cika4d

These Privacy Policy answers cover the account and wallet questions we expect before you open an account. Each answer points to a practical step, from checking a QRIS reference to requesting a copy of your records. If your question concerns eligibility or access, remember that access depends on local law and the support route can explain the available account process.

The Privacy Policy covers account details, phone verification, device signals, cookies, wallet references, support messages and retention. It explains why we use each category and how you can contact us about a copy, correction or deletion request.

We use your phone number to complete verification before account access and to connect support requests with the correct account. If you contact us about DANA or QRIS activity, the registered number helps us confirm ownership without requesting a wallet PIN.

Yes. The Privacy Policy covers transaction references and status records connected with DANA, OVO, GoPay and QRIS. We use those details to match a wallet action, investigate a receipt and answer a status question without storing your private wallet credentials.

Contact us through the support route linked to your account and ask for a data copy. Include your registered phone number and the request date. We verify account ownership first, then explain which records can be provided and in what format.

Yes. Send a correction request through account support and identify the detail that is wrong, such as a phone number or account label. We may ask for a verification step before changing records, so another person cannot alter your account data.

We keep account, wallet and support records while they are needed for account operation, security or legal requirements. After that need ends, our retention process removes the record or changes it so it no longer identifies you.

Yes. The Privacy Policy applies when you use a mobile browser to sign in, complete phone verification or open titles such as Aviator Mobile Play. Device and cookie details may be processed to maintain the session and protect account access.