Reference

keju4d Privacy Policy for Your Account

Clear account data choices help you use keju4d with fewer surprises: we explain what we collect, why we use it, and how you can ask for changes.

Account data explainedWallet records coveredRequest changes directly
keju4d keju4d Privacy Policy for Your Account
HELP WITH YOUR DATA

Get Privacy Help Beside Account Support

A direct support path lets you ask about a stored detail without explaining your concern to several teams. Use the support chat from your signed-in account and include the phone number or account reference connected to your request. We may ask you to confirm ownership before discussing records, changing contact details or responding to a wallet-data question.

Team online

Account data request

Ask support chat what account details are held for your profile. We will first confirm account ownership before sharing records or explaining how a field is used.

Wallet record query

For DANA, OVO, GoPay, QRIS or bank transfer references, send the relevant receipt number through support chat so we can locate the matching account entry.

Access concern

If a new device or login creates a privacy concern, tell support chat promptly. We can check the session path and help secure the account after verification.

OUR DATA PRACTICE

What We Do With Policy Requests

We keep this Privacy Policy practical by connecting each request to an account step, device event or payment record rather than giving you vague assurances.

Account data

We use your name, phone details and login credentials to create and protect the account. We do not need unrelated profile details for ordinary account access.

Device signals

We may record browser type, device identifiers and login times to recognise unusual sessions. These signals help us respond when your account opens from an unfamiliar device.

Cookie choices

Cookies can keep a session active and remember basic page settings. You can adjust cookie controls in your browser, although some account pages may then require another login.

Account security

Phone verification can be required before account access or a sensitive change. We use that step to reduce unauthorised changes to login, wallet and contact details.

Retention approach

We retain account, support and transaction references while needed for service records, disputes or legal duties. When those needs finish, we delete or anonymise data where practical.

Change requests

Send a correction, access or deletion request through support chat with your account reference. We may verify you first, then explain the action and any necessary retention.

Answers About Your keju4d Privacy Policy

These common Privacy Policy questions focus on the records you create when opening an account, signing in from a device or checking a wallet status. If your situation is not listed, use support chat and include enough account detail for us to locate the correct record.

It covers account details, phone verification, device signals, cookies, support messages and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account use.

Phone verification helps confirm that you control the account before access or a sensitive profile change. It also gives support a safer way to discuss account and wallet records.

Yes. We may retain a payment reference, status and receipt detail needed to match QRIS, DANA, OVO or GoPay activity with the correct account, without treating it as unrelated profile data.

Open support chat from your account and describe the field that needs correction. Include your account reference, complete any ownership check and we will explain the next step.

We keep records while they are needed for account administration, support, disputes or applicable legal duties. After that, we remove or anonymise them where practical.

Yes. Request the device and session categories linked to your account through support chat. We may verify ownership before explaining login times, browser signals or device identifiers.

Yes, account access and eligibility depends on local law. We use location and session signals only as part of access protection, and you should check local requirements before opening an account.