Reference

Privacy Policy for Your cendol138 Account

cendol138 Privacy Policy explains how we handle the details you provide when opening an account, checking DANA or QRIS status, and moving from mobile login into the lobby.

Account clarityWallet dataCookie choicesMobile access
cendol138 Privacy Policy for Your cendol138 Account
POLICY HELP ROUTES

Where To Ask About Privacy Policy

A clear support route matters when you want to ask what a record means or request a correction. We connect privacy questions to the account support path rather than asking you to post personal details in a public message. Include your account phone number only through the signed-in contact route, and describe whether the question concerns login, wallet status, cookies or a device record. We will use the details supplied for that request and may ask for an account step to confirm identity.

Team online

Account privacy request

Use the support route inside your account when you want to ask what personal details we hold or request a correction. We may ask you to complete phone verification before discussing account-specific records.

Wallet record question

For DANA, OVO, GoPay or QRIS references, send the payment date and visible status through the account support path. Do not include a wallet PIN; we need the transaction reference, not your private passcode.

Device and cookie help

If a mobile browser keeps an old session or cookie choice, tell us the device type and browser path you used. We can explain the record linked to access without asking for unrelated personal details.

HANDLING YOUR RECORDS

What We Do With Account Data

Privacy at cendol138 is managed around practical account events: registration, phone verification, wallet status checks and requests sent to support.

Data collection

We collect details needed to create and maintain your account, including contact details, phone verification results and records that help match a wallet status to your account request. Optional details are not required for unrelated browsing.

Cookie controls

Cookies and local browser storage can remember a signed-in session, language setting or policy choice. You can clear them in your browser settings, though clearing storage may require you to complete login and phone verification again.

Account security

We use account access checks to reduce the chance that another person can discuss your records. Keep your phone and login details private, and use the signed-in support route rather than sending credentials through an open message.

Retention approach

We retain account, wallet-status and support records only for the period needed for account operation, dispute handling, security checks and applicable legal duties. When a record is no longer needed, our handling follows the relevant deletion process.

Change requests

You can ask us to correct inaccurate account details or explain how a particular record is used. Send the request through your account support path, identify the field concerned and complete any identity check we reasonably need.

Policy contact

Questions about this Privacy Policy can be raised through the same account support route, including questions about DANA, QRIS, device access or cookie storage. We will keep the request focused on the privacy matter you describe.

Privacy Policy Answers for cendol138

These Privacy Policy answers address the searches we hear most often before an account is opened. We explain what data connects to login, how wallet references are treated, what happens on a mobile device and where to send a request. If your situation is different, use the account support route and give us only the details needed to identify the question.

The cendol138 Privacy Policy covers account details, phone verification, wallet-status references, device records, cookies and support requests. It also explains how we use those records for access, security and account administration, including when you use DANA, OVO, GoPay, QRIS or a bank route.

Phone verification helps us confirm that an account request belongs to you before we discuss account-specific data or wallet status. We may request this step during account access or a privacy request, and eligibility for access depends on local law.

Yes. The Privacy Policy covers the payment references and status details connected with a DANA or QRIS request, as well as OVO, GoPay, virtual account and bank transfer references. We do not need your wallet PIN to investigate a visible status.

Send a correction request through the signed-in account support path and name the field that needs changing. We may ask you to complete phone verification before changing or discussing personal details, so the request is linked to the correct account.

Our mobile browser may use cookies or local storage to retain a session, language choice or policy setting. Clearing browser data can remove that state and may send you back through login before you reach the lobby or account support path.

We keep personal data for the period needed to operate an account, answer support requests, handle disputes, maintain security and meet applicable legal duties. The exact period can depend on the record type and the reason it was collected.

Use the account support route linked from your signed-in area and describe the Privacy Policy question clearly. You can ask about account data, cookies, device records or wallet references; avoid sending passwords, wallet PINs or unnecessary identity details.