Reference

kustom4d Privacy Policy For Your Account

The kustom4d Privacy Policy explains how we collect, use and protect the account details that let you move from phone verification to the lobby, including wallet checks for…

Account dataCookie choicesWallet checksContact requests
kustom4d kustom4d Privacy Policy For Your Account
CONTACT OUR TEAM

Privacy Help Beside Your Cashier Path

A clear contact route helps you ask about the Privacy Policy without exposing account details in the wrong place.

Policy questions Ask us which account, device or cookie records relate to your request. Our support route is linked from the account area, so you can refer to the Privacy Policy while keeping the conversation connected to your profile.
Wallet record checks When DANA, OVO, GoPay or QRIS status needs checking, send the payment reference rather than a wallet password or access code. We use the reference to trace the request and limit the personal data shown in the support exchange.
Access concerns If phone verification or a sign-in step blocks your account, tell us the device path you used, such as mobile browser or desktop browser. We can separate an access issue from a Privacy Policy request without asking for unnecessary credentials.
DATA HANDLING

What We Keep And Why

We handle Privacy Policy requests through the same account flow used to protect your lobby access.

Account creation

When you open an account, we record the contact and verification details needed to create access. We use the phone step to reduce mistaken account matches and to respond to a Privacy Policy request from the correct account holder.

Device signals

Your mobile browser or desktop browser may send device, browser and session signals when you reach the lobby. We use these signals to maintain a session and identify unusual access, rather than to ask you for private wallet credentials.

Cookie controls

Cookies can remember a session path and help us understand whether an account page loads correctly. You can manage available cookie choices in your browser; blocking some cookies may require you to repeat sign-in or phone verification.

Payment records

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account request may create a reference, amount and status record. We use that record for reconciliation and support, while wallet passwords and one-time access codes should remain with you.

Retention requests

We keep account and transaction records for the period needed to operate access, resolve disputes, detect misuse or meet a legal duty. You may ask us what remains on file and request deletion where local law permits and no duty requires retention.

Policy changes

If this Privacy Policy changes, we will place the updated wording on this page and show the effective date. Before opening an account, read the current version; for a past version or correction request, contact us through your account support path.

Privacy Policy Answers For kustom4d

These Privacy Policy answers address the searches we hear most often before an Indonesian account is opened. They cover the records created by phone verification, mobile access and local payment status, along with the practical route for asking us to correct or remove eligible data. If your question concerns a specific account, use the support path connected to that account.

The kustom4d Privacy Policy covers account and contact details, phone verification, device and browser signals, cookies, payment references and support exchanges. It explains why we use each category, how long records may remain, and how you can request access, correction or removal where local law permits.

Yes. The Privacy Policy covers transaction references and status records created when you use DANA or QRIS, as well as OVO, GoPay, bank transfer and virtual account routes. We use those records to match a payment, resolve a receipt question and protect account access.

When you open an account, we collect the contact details and credentials needed for access, together with the phone verification record used to reduce mistaken matches. Your browser or device may also provide session signals when you move from sign-in to the lobby.

Use the support link inside your signed-in account and ask for a copy of the records covered by the Privacy Policy. Include the account contact used for phone verification, but do not send a password, wallet PIN or one-time access code in your request.

You can request a correction or deletion through the account support path. We will check the request against the verified account and explain any records that must remain for security, dispute handling or legal duties. Deletion availability depends on local law and the record type.

On a mobile browser, cookies may remember your session and help us identify loading problems between sign-in and the lobby. You can adjust browser cookie settings, although blocking some cookies may mean repeating phone verification or signing in again on your next visit.

Contact us through the support route shown inside your account, or use the access-screen contact route if you cannot sign in. Describe the policy concern and the relevant account step, such as phone verification or QRIS status, while keeping passwords and wallet codes private.