Terms page alignment
Our Terms page sets account rules, while this Privacy Policy explains data use behind those rules. We keep both pages aligned so access checks and account records are described consistently.
candu123 puts privacy controls beside your casino, slot and sportsbook account flow, so you know what data we collect before you jump into the lobby. Open your account...
This Privacy Policy explains how we collect, use, store, share, and protect data connected to your candu123 account in supported regions of Indonesia. We use account details to create access, run login checks, maintain security, manage wallet references, answer privacy requests, and keep records required where local law permits. When you interact with casino tables, slot rooms, sportsbook markets, promos, or support,
we may connect activity records to your account so your experience stays consistent and your requests can be handled accurately. We limit access to staff and service partners who need data for account, security, compliance, or support tasks. DANA, OVO, GoPay, and QRIS appear here as context chips only; this policy explains how related account records are handled, not how those services
operate.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
Privacy questions should feel easy to raise before and after you join. Use the paths below when you want to access your data, correct account details, ask how records are stored, or...
We keep this Privacy Policy practical for your account, not buried in legal fog. Our checks focus on clear data purposes, short retention wording, local context for Indonesia, and privacy contact paths...
We write privacy wording in direct en-ID English so you can see what each data use means. Legal terms are kept short, and account examples stay tied to candu123 activity.
Indonesia references are checked against the way your account works here, including e-wallet and QRIS-related records. We avoid copying language built for another market without context.
Each data category is matched to a purpose, such as login, wallet reference, security, support, or account service. That helps you understand why a detail is requested.
We avoid vague storage claims. Where records must be kept for account, security, dispute, or legal reasons, the policy explains the purpose and points you toward support.
When a service partner helps us run account, support, security, or wallet-reference tasks, we check that the privacy wording explains why that partner may see limited data.
When our account flow changes, we check whether the Privacy Policy needs a matching change. Major privacy updates are surfaced through account or site prompts when suitable.
Your privacy experience should not change from one legal page to another. We align this Privacy Policy with related candu123 pages so account, cookie, wallet-reference, support, and security wording all point back...
Our Terms page sets account rules, while this Privacy Policy explains data use behind those rules. We keep both pages aligned so access checks and account records are described consistently.
Cookie language is kept separate, but it connects back to this page where tracking touches account privacy. You can see how session, security, and preference data fit together.
Security wording explains protection steps, while this page explains related data handling. We keep login checks, device signals, and alert records described with the same practical language.
Promo pages may ask for account eligibility checks. This policy explains how related data is used for those checks, including account status, location context, and reward visibility records.
Wallet screens may show DANA, OVO, GoPay, or QRIS references. This page explains privacy handling for related account records without describing those services as our own systems.
Support pages collect details so we can answer your request. This policy explains how support messages, attachments, identity checks, and account follow-ups are stored and handled.
When we adjust legal wording, the update page and this Privacy Policy should point in the same direction. That keeps your account privacy choices easier to follow.
This page is arranged for quick privacy decisions, not long scrolling confusion. You can scan what we collect, why we use it, who may receive it...
Each privacy section starts with the reason data is used, then explains the account flow it supports. That helps you decide whether the request makes sense before you continue.
Privacy contact paths are placed near the policy details, not hidden at the end. You can ask about access, correction, deletion, or security concerns without hunting around.
The wording stays close to your candu123 account, including login, profile, wallet-reference, lobby activity, support, and security records. It avoids drifting into generic legal language.
Local context is included where it matters, especially around supported regions, e-wallet references, QRIS context, and account service partners that may help us operate candu123.
When privacy wording changes in a meaningful way, we aim to make the change visible through this page or account prompts. You can come back and compare new wording.
The FAQ uses direct questions you may ask before joining. Each answer points back to privacy rights, account data use, support paths, or security handling inside candu123.