Reference

palem4d Privacy Policy For Your Account

Our palem4d Privacy Policy shows what we collect when you create an account, verify your phone and move between the lobby and wallet area.

Clear data purposesWallet reference handlingPhone verification detailRequest paths
palem4d palem4d Privacy Policy For Your Account
REQUEST SUPPORT

Three Ways To Ask About Privacy

A clear contact route helps when you need to ask about personal data rather than a wallet status.

Account help route Open account help after signing in and identify the Privacy Policy question. We can use your account identifier to locate the relevant login, phone verification or access record.
Cashier record path For DANA, QRIS, bank transfer or virtual account references, use the support route beside the related cashier record. Share the date and status, not a password or complete wallet credential.
Privacy request Ask to see, correct or remove eligible personal data through the contact route linked with this policy. We may request account details to confirm that the request belongs to you.
DATA PRACTICE

How We Handle Your Personal Data

We separate account access records from the payment references needed to check a transaction status.

Data we receive

When you create an account, we may receive your contact details, phone verification result, login events and device signals. Payment references from DANA or QRIS can connect a wallet action with the correct account record.

Purpose of use

We use account and device data to authenticate access, detect unusual sign-in activity, answer support requests and check payment status. We do not need unrelated wallet content to identify a DANA, OVO or GoPay reference.

Cookies and devices

Cookies and similar device storage can keep a session working, remember basic preferences and support security checks. Clearing browser storage may sign you out and require phone verification again before account access.

Account security

Keep your password and phone verification details private. If a sign-in looks unusual, we may use device and session signals to protect the account before you reach casino or sports pages.

Retention choices

We retain records only for the period needed for account security, payment reconciliation, support handling and applicable legal duties. Some transaction or access records may remain after an account request is closed.

Changes and contact

You can ask us to correct eligible account details or explain a data decision through the policy contact route. Include the affected email or phone detail, while keeping passwords and wallet credentials out of the message.

Privacy Policy Questions From Indonesia

These answers address the searches we hear around account records, wallet references, device use and personal data requests. They are written for your palem4d account journey, from phone verification through a return to the lobby. If your situation involves eligibility or access, that outcome depends on local law.

It explains how we handle account details, phone verification, device signals, cookies, security events and payment references. It also sets out contact paths for access, correction and eligible removal requests.

Yes. We may handle references needed to match DANA or QRIS activity with your account and check status. We do not need unrelated wallet content for that reconciliation step.

Phone verification helps connect an account request with the person seeking access and supports account security. We may retain the verification result with related login records for security and support purposes.

You can send a data access request through the contact route linked with this Privacy Policy. We may ask for an account identifier or other details to confirm the request is yours.

Use the policy contact route and name the detail that needs correction, such as a contact record. Do not include your password, full wallet credential or private security code.

We keep payment references for the time needed to reconcile status, protect accounts, answer support requests and meet applicable legal duties. The exact period can differ by record type and local law.

Yes. It covers data handled when you sign in through a mobile browser, including cookies, session details and device signals. Clearing storage can end the session and trigger phone verification again.