Reference

candy99 Privacy Policy Explained Clearly

candy99 Privacy Policy shows what we collect when you open an account, verify your phone, sign in on mobile, or use DANA and QRIS payment screens.

Account dataWallet recordsCookie choicesAccess requests
candy99 candy99 Privacy Policy Explained Clearly
PRIVACY CONTACT

Reach Us About Personal Data

A clear support route helps when your Privacy Policy question relates to a login, wallet record or device entry. Open the account support path beside the cashier area and describe the request in plain English. Include your registered phone number only when needed for account matching, and never send a wallet PIN. We use the details in your message to locate the relevant record and respond with the next step.

Team online

Account privacy request

Ask us to confirm the personal data connected with your candy99 account. We may ask for a phone verification step before sharing account-specific details, so a stranger cannot obtain your login history or wallet references.

Wallet record check

For DANA, OVO, GoPay, QRIS, bank transfer or virtual account questions, send the payment reference and date shown on your receipt. We use that narrow detail to trace status without requesting your wallet password or full banking credentials.

Cookie assistance

If a browser keeps a cookie you no longer want, contact our support path with your device type and browser setting. We can explain the available control, while access remains subject to local law and required account security checks.

DATA HANDLING

Six Practical Privacy Commitments

Privacy work is easiest to assess when each promise has an operational action behind it. We separate account access records from payment references, use device signals to investigate unusual sign-ins, and keep…

Account details

We use your registered phone number and account details to create access, complete phone verification and connect requests to the right account. If you ask for a copy or correction, we first check that the request comes from the account holder.

Payment references

A DANA, OVO, GoPay or QRIS reference helps us match a cashier event with your account. Bank transfer and virtual account records may also be kept for reconciliation, status checks and handling a support request about that transaction.

Device signals

When you sign in from a phone or desktop, we may note device and browser signals linked to access events. These details help us investigate an unfamiliar login without treating the contents of your personal device as part of our records.

Cookie controls

Cookies can preserve a session or remember a choice made in your browser. You can manage available cookie settings through the browser path, and our policy explains which functions may stop working when a necessary cookie is refused.

Storage periods

We retain different records for different operational reasons rather than keeping everything indefinitely. Account, security and payment records may remain while needed for the stated purpose, a dispute or a legal requirement described in the Privacy Policy.

Policy requests

Send a request through the account support route when you need access, correction, deletion or an explanation of processing. We may request phone verification, define the affected record, and explain any restriction that depends on local law.

Privacy Policy Questions Before Account Access

These answers cover the searches we hear before an Indonesian account is opened or a wallet is connected. They focus on the records created by sign-in, phone verification, device use, cookies and payment references. If your situation is not covered, use the support route linked near the cashier and describe only the details needed to identify your request.

The candy99 Privacy Policy covers account details, phone verification, login events, device and browser signals, cookies, support messages and payment references. It explains the purpose of each record, possible storage periods, request routes and the conditions that depend on local law.

We use the registered phone number to create and protect your account, complete the clear verification step before access, and match a privacy request to the correct account. We do not need your DANA, OVO, GoPay or QRIS wallet PIN for that process.

Yes. The Privacy Policy covers references connected with DANA, QRIS, OVO, GoPay, bank transfer and virtual account activity. We use a receipt reference, date or status detail to trace the relevant cashier event, while avoiding a request for your full banking credentials.

Use the account support path and ask for an access request under the candy99 Privacy Policy. State the registered phone number and the record type you want checked. We may complete phone verification before confirming account-specific data or explaining why a limit applies.

You can request a correction or deletion through support, and our Privacy Policy explains how we assess it. We may retain selected account, security or payment records when needed for a dispute, account protection or a legal requirement, where local law permits.

Cookies can keep a sign-in session active or remember a browser preference. You can manage available choices in your browser settings. Refusing a necessary cookie may affect account access, while optional cookie handling follows the purposes stated in our Privacy Policy.

Start with the support route beside the cashier and label your message as a Privacy Policy request. Share the smallest useful detail, such as a receipt reference or device type, and do not send a wallet PIN. We will explain the next account verification step.