Reference

Privacy Policy For Your cempaka66 Account

cempaka66 Privacy Policy explains how we handle your account details, device signals and wallet records when you use our Indonesia service.

Account clarityWallet recordsDevice awareness

Browse Our Lobby Read FAQ

How Privacy Applies To Wallet Records

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

Our Privacy Policy covers details you provide when opening an account, phone verification before account access, and records created when you use DANA, OVO, GoPay, QRIS, bank transfer or a virtual account. We use these records to confirm account ownership, match payment status and investigate a

1
stalled transaction, rather than to create unrelated profiles. Device type, browser signals and security events can help us recognise unusual access and protect your session. We keep records only for operational, security or legal needs, then remove or anonymise them when they are no longer needed.
2
If you are in Makassar or elsewhere in Indonesia, the same policy request path applies, while access depends on local law. Ask our support team which record category applies before sending sensitive details.

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

HELP WITH PRIVACY

Get Clear Answers About Your Data

A direct privacy question should not require you to search through your account screens. Our support route helps you identify the right request, confirm which account details are needed and keep payment…

Account requests Ask us to confirm the account details connected with your phone verification, including the contact record used before account access. We may need an account identifier to avoid sending personal details to the wrong person, and we will explain the next step through our support route.

Wallet questions For DANA, OVO, GoPay or QRIS records, include the payment reference and date rather than sharing a wallet password or full security code. We can check the status trail, explain what was retained and separate a privacy request from a payment-status question.

Access concerns If a new phone, browser or login event appears unfamiliar, tell our support team before sending documents. We use the account-security path to verify ownership, restrict unsafe access when needed and explain how device signals relate to the Privacy Policy.

DATA HANDLING

What We Do With Account Details

Privacy works best when each data use has a clear reason. We connect account, device and payment records only where they help provide access, check security or respond to a request.

Account data

We may hold your name, phone details and verification status so we can identify your account and protect access. We use those details for account administration and support, not as a reason to request unrelated personal records from you.

Payment data

DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity can create reference numbers, timestamps and status records. These help us match a deposit or withdrawal request without needing your wallet password, card secret or banking login.

Cookies

Cookies and similar device storage can remember a session choice, reduce repeated login steps and help detect unusual browser behaviour. You can manage browser settings, although limiting necessary storage may affect account access or the way policy choices are saved.

Security signals

We may assess device type, browser details, IP-related signals and login timing when an account event looks unusual. These checks support phone verification and session protection; they are used to examine access risk, not to infer unrelated personal traits.

Retention

We retain each category only while it serves account operation, security, dispute handling or a legal requirement. When the reason ends, we delete the record or separate it from direct account identifiers where that approach is suitable.

Your requests

You can ask what personal data we hold, request a correction, question a use or seek deletion where applicable. Contact our support route with enough account detail to verify ownership, and we will explain any limit that depends on local law.

Privacy Policy Answers For Indonesia

These Privacy Policy answers address the account and payment questions we expect you to ask before opening access. They explain what cempaka66 records, how you can make a request and why certain checks may be needed for wallet activity or an unfamiliar device.

It covers account details, phone verification, device and browser signals, cookies, support exchanges and payment references linked to DANA, OVO, GoPay, QRIS, bank transfer or a virtual account. It also explains retention, security use and the ways you can request access or correction.

Phone verification helps us confirm that the person requesting account access or a data change controls the registered contact. It also helps us investigate an unfamiliar login. We use the result for account security and administration, subject to what depends on local law.

Yes. The Privacy Policy covers payment references, status details and timestamps connected with DANA and QRIS, as well as OVO, GoPay, bank transfer and virtual account activity. We use those records to match requests and resolve status questions without asking for wallet passwords.

You can contact our support route and ask us to check or correct account details that are inaccurate. Include a safe account identifier, not a password or security code. We may verify ownership first, then explain the action available under the Privacy Policy.

Retention depends on why a record exists. We keep account, security or payment references while they support access, dispute handling, safety or a legal requirement. After that need ends, we remove the record or separate it from direct identifiers where suitable.

Yes, you can ask for a description or copy of personal data connected with your account through our support route. We first confirm ownership and may withhold details that would expose another person or security control, where local law permits.

Send our support team the approximate time, device type and account identifier, without sharing your password. We can compare the event with security records, explain the relevant Privacy Policy use and help protect the account if the access was not yours.

Privacy Policy For Your cempaka66 Account

Get Clear Answers About Your Data

What We Do With Account Details

Account data

Payment data

Cookies

Security signals

Retention

Your requests

Privacy Policy Answers For Indonesia

01 What does the cempaka66 Privacy Policy cover?

02 Why does cempaka66 need phone verification?

03 Does the Privacy Policy cover DANA and QRIS records?

04 Can I ask cempaka66 to correct my personal data?

05 How long does cempaka66 keep account information?

06 Can I request a copy of data held about me?

07 How do I ask about an unfamiliar device event?

Related Pages