Reference

Open the rejekibet slot Privacy Policy

The rejekibet slot Privacy Policy explains what we collect when you create an account, complete phone verification, sign in from a mobile device, or check DANA and QRIS…

Account dataCookie choicesWallet recordsContact requests
rejekibet slot Open the rejekibet slot Privacy Policy
CONTACT ROUTES

Contact us about Privacy Policy

A clear contact route helps when you want to ask what we hold or correct an account record.

Policy questions Use the support contact route for questions about this Privacy Policy, including the data…
Correction requests Tell us which account detail needs correction and why.
Access concerns If a sign-in device is unfamiliar or your wallet status looks wrong, contact us…
DATA PRACTICES

Check rejekibet slot data handling

Our Privacy Policy is designed around the points you encounter during an account session: creating a profile, confirming a phone number, signing in on mobile, checking a wallet…

Account creation

When you open an account, we record the contact details you submit and the account steps you complete.

Device signals

A mobile browser may send device, browser, language, and session signals when you sign in.

Cookies

Cookies can remember a login session, preserve a selected setting, or help us understand whether a page request completed.

Wallet records

A DANA, OVO, GoPay, QRIS, bank transfer, or virtual account event may create a payment reference, amount, timestamp, and status…

Retention period

We keep account, security, and payment records only for as long as needed for the stated service purpose, dispute handling…

Your request

You can ask what account data we hold, request a correction, ask about processing, or raise a deletion question through…

Browse Privacy Policy answers

These Privacy Policy answers address the account and device questions we expect from Indonesian customers before they open an account. Each answer stays focused on personal data, wallet references, cookies, access checks, and the contact steps available through our support route. If your situation is not covered, send us the relevant account detail without sharing a password.

It covers data connected with your account and sessions, such as contact details, phone verification, device signals, cookies, security events, support requests, and payment references from DANA, OVO, GoPay, QRIS, bank transfer, or virtual account activity.

Phone verification helps us connect your sign-in with the correct account and reduces the chance that private account or wallet data is shown to someone else. We record the verification result and use it for account access and security checks.

When you sign in from a phone or tablet, we may receive browser, device, language, and session signals. We use them to maintain the login session, identify unusual access, and investigate account events, rather than to inspect unrelated content on your device.

Yes. Contact us through the support route linked to your account and describe the record you want to access or correct. We verify the request against your profile before discussing private data, and the available action depends on local law.

A DANA or QRIS event can create a reference, amount, timestamp, and status connected with your account. We use those details to match the transaction state and answer a support question. We do not treat the payment rail as permission to collect unrelated data.

We retain account, security, and payment records for the period needed for the stated service purpose, dispute handling, security work, or legal duties. After that need ends, our process removes or de-identifies the record where applicable.

Use the support contact path inside your account area and include the email or phone detail linked to your profile. You can ask about access, correction, cookies, retention, or deletion. Do not send your password or complete payment credentials.