Reference

Open keraton4dsite Privacy Policy Clearly

Our keraton4dsite Privacy Policy explains what we collect during account access, why wallet details such as DANA or QRIS appear in records, and how you can ask about…

Account dataWallet recordsCookie choicesPrivacy requests
Browse Our Lobby Read FAQ
keraton4dsite Open keraton4dsite Privacy Policy Clearly
PRIVACY CONTACT

Contact Us About Your Privacy Policy

A clear contact path helps when an account record, wallet reference, or cookie choice needs attention. Start from the account help panel while signed in, or use the support route beside the cashier status area if you cannot reach your account. Include your account details carefully; we may ask for a verification step before discussing personal data.

Team online

Account help panel

Use the signed-in account help panel for a Privacy Policy question, correction request, or query about phone verification records. We check the account step before sharing details.

Cashier status route

If a DANA, OVO, GoPay, or QRIS reference appears incorrectly, use the support path beside cashier status and provide the transaction reference shown in your account.

Security contact

For a suspected sign-in issue, describe the device path, browser session, and time you noticed it. We use those details to locate the relevant account-security record.

HANDLING DETAILS

Explore How We Handle Account Data

Privacy choices work best when the account trail is easy to understand. We separate details needed for sign-in, wallet matching, support replies, and security checks, then connect them only when an operational…

Collection purpose

We collect account details to create access, complete phone verification, answer support requests, and connect a payment reference with the correct account. We do not need every detail for every request.

Cookie controls

Cookies can retain a login session, remember a page setting, or help us understand page performance. You can manage available browser cookie controls, although some account steps may then require another sign-in.

Mobile sessions

When you sign in through a phone browser, we may record device type, browser details, session time, and security signals. This helps us distinguish your account path from unusual access attempts.

Account protection

Phone verification and sign-in checks help protect personal details. If an access pattern changes before you reach the lobby, we may request an additional account step before discussing wallet or profile records.

Record retention

We retain account, support, and payment references for the operational, security, dispute, or legal period that applies. After that need ends, we remove, anonymise, or separate records where appropriate.

Change requests

You can ask us to correct eligible details, explain a record, or request deletion where local law permits. Use the account help panel and identify the exact record you want us to check.

Check Privacy Policy Answers Before Opening

These Privacy Policy answers focus on the account and wallet questions you may have before opening access. They explain the records created by phone verification, mobile browsing, payment references, cookies, and support contact, while keeping eligibility subject to local law.

It covers details linked to account opening, phone verification, sign-in, mobile sessions, support contact, cookies, and payment references for DANA, OVO, GoPay, QRIS, bank transfer, or virtual account use.

Yes. The Privacy Policy covers references used to match DANA or QRIS activity with your account, check a payment status, handle a dispute, and answer a support request without exposing unrelated account details.

A phone browser may provide device type, browser details, language, session time, and security signals. The Privacy Policy explains how those technical records support sign-in protection and account troubleshooting.

Use the signed-in account help panel and name the specific detail or record. We may verify your account first, then assess correction, restriction, explanation, or removal where local law permits.

We keep records while they serve an operational, security, dispute, or legal need that applies. When that need ends, we remove, anonymise, or separate eligible records according to the applicable requirement.

Yes. Ask through the account help panel about cookies connected with your session or page settings. Browser controls can also manage cookies, though turning them off may require another sign-in.

Yes. Account access, data choices, and the handling of some requests depend on local law. Where local law permits, we assess requests to explain, correct, restrict, or remove eligible details.

Related Pages

keraton4dsite Indonesia Access guide Sic Bo FAQ Account information