Reference

Privacy Policy For Your kera303 Account

Our Privacy Policy explains how kera303 collects, uses and protects the details connected with your account, device and wallet activity.

Account clarityWallet detailsDevice controlsPolicy access
kera303 Privacy Policy For Your kera303 Account
CONTACT THE TEAM

Privacy Questions Reach Real Support

A privacy question should not disappear into a general queue, so we provide a direct route through the account support area and the cashier help path.

Live chat Use live chat from your logged-in account when you need to ask about stored…
Support form The support form lets you describe a correction, access request or cookie question in…
Cashier help If your privacy concern involves DANA, OVO, GoPay, QRIS, a bank transfer or a…
SIX DATA PROMISES

How We Handle Account Information

Our privacy process follows the same account journey you use to reach the lobby: contact details are collected at account opening, security checks occur before sensitive changes, and…

Collection

We collect information when you create an account, complete phone verification, contact support or submit a payment status question.

Cookie use

Cookies help keep your account session active, remember selected settings and connect a support request with the right account.

Account security

Before we change a phone number, recovery detail or other private field, we may ask you to complete an account…

Payment references

For DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity, we keep the reference needed to match a cashier…

Retention

We retain account, security and payment records for as long as needed to provide access, resolve disputes, protect the service…

Your requests

You can ask what personal details we hold, request an inaccurate field be corrected, or ask how a particular record…

Privacy Policy Questions From Indonesia

These Privacy Policy answers address the account and wallet questions we hear most often from people accessing kera303 in Indonesia. They explain what we collect, why a phone check may appear, how cookies affect a mobile session and where to send a request. If your question concerns a specific payment receipt or device, use the support route with the smallest necessary set of details.

The kera303 Privacy Policy explains how we collect, use, secure and retain account, device, cookie and payment-reference details. It also describes your choices, the checks used before sensitive account changes and the support routes for access or correction requests.

We may collect your account contact details, phone verification record, login history, device information, browser signals and support messages. If you ask about DANA, OVO, GoPay or QRIS status, we may also keep the transaction reference needed to locate that cashier event.

Phone verification helps us connect an account request with the correct account holder before access or sensitive changes. It can also help us identify an unusual sign-in. We use the verification record for account security and handle it according to this Privacy Policy.

Send a request through logged-in live chat or the support form, identify the field that needs correction and provide your account contact. We may ask for an account check before changing private information, and our team is available daily from 08:00 to 23:00 Indonesia time.

Yes. The Privacy Policy covers cookies and similar tools used to maintain login state, remember device preferences and detect unusual sessions. If you restrict cookies in your mobile browser, you may need to authenticate again when moving between your account and the lobby.

We use DANA and QRIS references to match a deposit or cashier status, while avoiding any need for your wallet password. If you contact us about a receipt, share the reference and transaction time only. We limit the payment detail shown in the support process.

Where local law permits, you can ask what personal details we hold, how they are used and how long relevant records remain stored. Contact live chat or the support form. We may verify your identity first, then explain the available response and any limits.