Reference

kakek merah Privacy Policy for Your Data

kakek merah Privacy Policy explains how we handle the account details, wallet records and device signals connected with your access.

Account dataWallet recordsDevice choices
Explore Our Lobby Read FAQ
kakek merah kakek merah Privacy Policy for Your Data
PRIVACY HELP ROUTE

Get Privacy Help Beside Your Account

A clear contact route matters when a phone number, wallet reference or device record needs attention. From the account help area, you can send a privacy request with the email or phone number linked to your account and describe the change you need. If you are in Bandung and a QRIS status appears beside the wrong session, include the date and reference so we can locate the relevant record without asking for your wallet PIN.

Team online

Data request

Send a request through the account help route when you want to know which personal data we hold. Add your linked phone number and the subject of your request so we can check identity before discussing account records.

Correction path

If your contact detail or wallet reference is inaccurate, tell us which field needs changing. We may ask for the account step or verification result connected to it, then record the correction request against the matching profile.

Status follow-up

For a privacy request linked to DANA, OVO, GoPay, QRIS or a bank transfer, include the visible payment reference and date. We use that limited context to trace the record while avoiding a request for your wallet password.

DATA HANDLING

How Your Data Stays Account-Linked

We keep this Privacy Policy practical by describing the points where data enters, moves and leaves our account process.

Account records

We may store your phone number, verification result, account identifier and access timestamps so we can connect a request to the correct profile. These fields also help us distinguish a new sign-in from a repeated session on the same device.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account entries are handled as transaction references and status data. We use them to match account activity, not to request or retain your wallet PIN or banking login.

Cookie choices

Cookies can support sign-in continuity, language settings and basic session protection. You can adjust cookie controls in your browser, although changing them may require another phone verification step before account access continues.

Device signals

Your browser type, operating system, approximate session time and security events may be recorded when you move from login to the lobby. These signals help us investigate a disputed access event without reading unrelated files on your device.

Retention period

We keep personal data only for the period connected to account service, dispute handling, security checks or duties that depend on local law. When a record no longer has a stated purpose, our process is to remove or separate it.

Change request

You can ask for access, correction or clarification through the account help route. Include the email or phone number linked to your profile, and we may request identity confirmation before releasing or changing personal data.

Privacy Policy Questions Before Access

These Privacy Policy answers focus on the searches we expect before you open an account or ask about a stored record. We keep the wording tied to real account steps, local wallet references and device behaviour, so you can decide what to share and how to contact us. Access and eligibility remain subject to local law.

It covers personal data connected with your account, including phone verification, sign-in events, device signals, cookie settings, support requests and payment references. It also explains why we use those records, how retention works and how you can ask for access or correction.

We may store status and reference data for DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity. These records help match a transaction to your account. We do not need your wallet PIN or banking login to check a payment status.

Cookies may keep a session active, remember selected settings and support basic account protection. Your browser controls can limit them. If a setting blocks a required cookie, you may need to complete phone verification again before account access continues.

Use the account help route and provide the phone number or email connected with your profile. State that your request concerns the Privacy Policy and access to personal data. We may confirm your identity before sharing records linked to the account.

Yes. Tell us which field is wrong, such as a phone detail or payment reference, and explain the correction needed. We may compare the request with your verification result before changing the record or explaining why it must remain unchanged.

Retention depends on the purpose of each record. Account and device data may support access or security checks, while transaction references may remain for reconciliation or duties that depend on local law. You can ask for the retention reason through account help.

You can ask which session data is connected with your account, such as access time, device signal or related payment reference. Include the approximate date and linked phone detail. Where local law permits, we will explain the record and the available request path.

Related Pages

kakek merah Indonesia Access guide kakek merah Casino Account information Live Baccarat Elite