Reference

Privacy Policy for Your rekap 2d Account

Our Privacy Policy explains how we collect, use and protect details connected with your rekap 2d account, device and wallet activity.

Account dataWallet referencesDevice controlsPolicy requests
Explore Our Lobby Read FAQ
rekap 2d Privacy Policy for Your rekap 2d Account
ASK ABOUT DATA

Get Help With a Privacy Policy Request

A clear contact route matters when your account record does not look right. Open the support path from your account and tell us whether your request concerns phone verification, a wallet reference, device access or a correction to personal details. Include the email or phone detail attached to the account, but do not send a password or full payment credentials. We use the same account check before discussing a request, so help remains tied to the correct profile. When access is available where local law permits, this route also handles questions about the Privacy Policy.

Team online

Account request

Use the support contact shown inside your account when you want to ask about stored profile details. We check the account path first, then explain what can be corrected, what may need retention for a transaction record and what further detail is needed.

Wallet clarification

If a DANA, OVO, GoPay or QRIS reference appears unfamiliar, send the transaction date and the visible status rather than your wallet PIN. We can compare the account record with the payment reference while keeping private credential details out of the request.

Device access

For a sign-in concern on mobile or desktop, describe the device path and the account step where the issue occurs. We may ask you to complete phone verification again, helping us separate a genuine request from an unapproved attempt to change data.

SIX DATA PROMISES

What We Do With Personal Details

Our handling process follows the practical steps behind your account rather than treating privacy as a banner on the page.

Collection

We collect details you provide during account opening, including contact data used for phone verification. We also receive operational signals such as sign-in time, device path and wallet status so we can connect a request to the correct profile.

Use

We use personal details to provide account access, answer support requests, check unusual sign-in activity and match payment references. A QRIS or bank transfer status is used for that transaction purpose, not as a reason to inspect unrelated account activity.

Cookies

Cookies can preserve your login state and help us recognise a device during account checks. Browser settings let you remove or restrict them, but switching them off may require you to repeat verification before reaching account areas.

Security

We protect account access by limiting sensitive changes to the verified account path. If a request involves a phone number, wallet reference or device change, we may ask for an additional account step before making the change.

Retention

We retain records for as long as they support the account, security, support or transaction purpose described here, subject to applicable requirements. When a record no longer serves that purpose, our handling process moves toward deletion or removal from active use.

Your request

You can ask us to access, correct or clarify personal details connected with your account through the support route shown after sign-in. We may verify ownership first, and we explain any limit when a record must remain for a transaction or security reason.

Privacy Policy Answers for Indonesia

These Privacy Policy answers focus on the account questions you are most likely to ask before opening or using rekap 2d from Indonesia. We explain the data connected with phone verification, mobile access, wallet references and requests for changes in plain terms. Where a legal or eligibility question depends on location, access depends on local law and applies where local law permits. If your situation is not covered, use the account support path without sending passwords or wallet PINs.

It covers personal details linked to your account, phone verification, device access, support requests and payment references such as DANA, OVO, GoPay and QRIS. It also explains cookies, security checks, retention and how to ask us to access or correct a record.

Phone verification helps us connect account access and sensitive changes to you rather than to an unapproved device. We may request it when you open an account, recover access or change details connected with wallet status or payment records.

You should never send us a wallet PIN or password through support. Our Privacy Policy covers payment references and status details needed to match an account transaction, such as a QRIS or bank transfer record, not your private payment credentials.

Yes. Use the support contact shown in your account and identify the detail that needs correction. We verify the account before changing it, and we explain if a transaction or security record must remain rather than being edited or removed immediately.

We may use sign-in, device and browser signals to preserve your account path, detect unusual access and support verification. A mobile visit from Semarang follows the same policy controls as desktop access, with eligibility depending on local law.

We keep records while they serve account access, payment matching, support, security or an applicable operational requirement. After that purpose ends, the record can move out of active use or toward deletion, subject to any requirement that still applies.

Start with the support route inside your account and state whether you need access, correction, clarification or deletion. Include only the account detail needed to locate your request. We may ask for phone verification before discussing personal data or changing access.

Related Pages

rekap 2d Indonesia FAQ Access guide About Us rekap 2d Casino