Reference

cake 4d Privacy Policy For Your Account

cake 4d Privacy Policy explains how we collect, use and protect details connected with your account, device and wallet status.

Clear data purposesCookie choicesAccount access stepsContact for changes
Browse the lobby Read FAQ
cake 4d cake 4d Privacy Policy For Your Account
CONTACT THE DESK

Get Privacy Help Through Your Account

A clear support path matters when you want to ask about a record, cookie choice or account detail. Sign in where possible and include the phone number linked to your account, the device path you used and the relevant wallet reference. Our support desk can route privacy questions separately from a payment-status request, helping us check the right record without asking you to send unnecessary details.

Team online

Account privacy request

Use the support path inside your account to ask what personal details are connected with your profile. Include your registered phone number and the request you want handled, such as access, correction or removal. We may ask for account verification before discussing private records.

Wallet record question

If your question involves DANA, OVO, GoPay or QRIS, provide the transaction reference rather than a full wallet password or security code. We use the reference to locate payment status and keep the request focused on the transaction data that needs checking.

Device access concern

Tell us whether you used a mobile browser or desktop session when an unexpected sign-in appeared. We can use the account and security log details to investigate access, while you should change your account password and avoid sharing verification codes during the check.

HOW WE HANDLE DATA

Browse The Privacy Controls We Keep

Privacy work is easier to understand when each control has a clear purpose. We separate account access records, payment references, cookie settings and support messages so a request can reach the correct…

Data collection

We may collect your account name, phone number, sign-in details, device signals and transaction references when you use the service. These details help us provide account access, investigate security events and connect a DANA, OVO, GoPay or QRIS status request to the correct profile.

Cookie handling

Cookies can preserve a sign-in session, remember selected settings and help us understand whether a page loads correctly on your device. You can manage browser cookie controls, but switching them off may require you to sign in again when moving between account pages.

Account security

Phone verification is used before account access is completed, and security signals may be checked when a sign-in looks unusual. Never send us a password or one-time code. If your device changes, sign out of old sessions and contact the account support desk.

Record retention

We retain records only for the operational, security or legal purpose connected with them, then assess whether they are still needed. Payment references from bank transfer or virtual account activity may need a different retention period from a temporary cookie.

Correction requests

If your phone number, account name or another stored detail is wrong, ask for a correction through the support path in your account. State the old and new value clearly. We may verify ownership first so a private record is not changed by another person.

Policy questions

For a question about this Privacy Policy, contact us through account support and identify the relevant section: data use, cookies, security, retention or a rights request. Where local law permits, we will explain the next step and any verification needed to respond.

Find Answers About Privacy Policy

These Privacy Policy questions cover the account steps you are most likely to ask about before opening access. We keep the answers tied to actual records, device behaviour and local wallet references, so you can decide what to share and where to send a request. If your situation is not listed, use the support path in your account and mention the specific data issue.

The cake 4d Privacy Policy covers account details, phone verification, sign-in and device records, cookies, support messages, payment references and retention. It also explains how to request access or correction. Service access depends on local law, so eligibility can vary by your location.

We use phone verification to confirm that the person opening or accessing an account controls the registered number. It supports account security and helps us handle privacy requests correctly. Do not send a verification code to support or anyone claiming to act for us.

Yes. The Privacy Policy covers transaction references and status details connected with DANA, OVO, GoPay and QRIS, as well as bank transfer and virtual account activity. We use those records to check a payment question without requesting your wallet password or security code.

Sign in and use the account support path to request access to your stored data. Include your registered phone number and describe the records you want checked. We may verify account ownership first, then explain which records can be provided under local requirements.

You can ask us to correct an inaccurate account detail through account support. Identify the field, explain the correct value and provide the registered phone number. We may ask for verification before making a change, helping prevent another person from altering your profile.

Cookies may keep your mobile browser session active, remember selected settings and help us identify loading problems. If you block or clear them, you may need to sign in again and some account pages may not behave as expected. Browser controls remain available to you.

Use the support path inside your account and label your request as a Privacy Policy question. Mention access, correction, deletion, cookies or retention, and include only the details needed to locate your record. Where local law permits, we will explain verification and the next step.

Related Pages

cake 4d Indonesia Access guide About Us Live Baccarat Gold Indonesia Mobile Lobby 504