Reference

Open resep4d Privacy Policy Before Account Access

resep4d Privacy Policy explains how we collect, use, protect and retain details connected with your account, device and payment activity.

Clear data purposesWallet record handlingCookie choicesAccount access requests
Browse Our Lobby Read FAQ
resep4d Open resep4d Privacy Policy Before Account Access
PRIVACY HELP

Check Your Data Request Through Account Support

If a privacy question affects your account, we give you a clear route to contact us without sharing sensitive details in an open message. Start with the account support path and include the phone or account identifier used during registration, plus the subject of your request. We may ask you to complete an account check before discussing records, changing contact details or confirming a deletion request. This protects your account when a login or wallet status stalls, including activity linked with GoPay, QRIS or a bank transfer.

Team online

Account data request

Ask us to identify the personal details held for your account, explain why a category is used, or provide a copy where the request is permitted. Include your registered phone detail so we can locate the correct account without exposing another person’s records.

Correction path

If your phone detail, name or account record needs correction, contact account support and describe the specific change. We may request an account verification step before editing the record, especially when the change could affect wallet status, payment receipts or access to the lobby.

Privacy contact

For questions about cookies, retention, account security or a data request, use the support route connected to your account. Keep payment receipts and status references private; we use them to investigate DANA, OVO, GoPay, QRIS and bank transfer records safely.

DATA PRACTICES

Browse Our Data Handling Steps With Clarity

We handle privacy through practical account controls rather than treating every record the same way. Registration details support account access, device signals help identify unusual login behaviour, and payment references help reconcile…

Data collection

We collect details you enter during account opening, the phone verification result, login events, device information and payment references. We do not need your wallet PIN for a receipt check. DANA, OVO, GoPay, QRIS, bank transfer and virtual account entries are used to match transaction status.

Cookie controls

Cookies may keep your session active, remember a language or device setting, and help us trace a technical error between login and the lobby. You can adjust cookie controls in your browser, although limiting them may affect account access or require you to sign in again.

Account security

Phone verification comes before account access, and we use login and device signals to detect activity that does not match your usual pattern. Never send a password, wallet PIN or one-time code in a support message. Contact us if your account details change unexpectedly.

Retention periods

We keep account, security and payment records only for the period needed for the stated purpose, dispute handling or a legal duty. A closed account may still have transaction references retained when required. We remove or de-identify records when the applicable retention reason ends.

Third-party handling

Payment and technical partners may process the details needed to confirm a wallet or transfer status. Their role is limited to the transaction or service task involved. We do not ask you to post payment credentials in chat, and we use receipt references instead of wallet secrets.

Change requests

You can request access, correction or deletion of eligible personal details through account support. Tell us which record you mean and how we can reach you through the registered account route. We may verify ownership first, and the result depends on local law and any retention duty.

Find Answers About Privacy Policy Access

These Privacy Policy answers address the account and payment questions we expect from customers in Indonesia. They explain what we collect, why phone verification matters, how cookies work, and how to request a change without sending private credentials. If your question concerns a specific receipt or login event, use the account support route and keep the reference available.

It covers personal details used for account creation, phone verification, login security, device operation, cookies, payment references, support requests and retention. It also explains how we handle records connected with DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity.

Phone verification helps us confirm that the person requesting account access controls the registered contact route. It also supports account recovery and security checks. We record the verification result and related event, but you should not send a one-time code or wallet PIN to support.

Yes. The policy covers payment references and status details needed to reconcile DANA, OVO, GoPay or QRIS activity with your account. For bank transfer and virtual account payments, we may retain the route and receipt reference while avoiding collection of your banking password.

Use the account support route and state that you want a copy of your personal data. Provide the registered phone detail or account identifier, then complete any ownership check we request. We will assess the request under local requirements and explain any material restriction.

You can request a correction through account support by naming the exact field that is wrong and supplying the replacement detail. We may verify your account before making the change, particularly when it affects phone access, wallet status, payment receipts or security records.

Retention depends on the record and its purpose. Account and device details support access and security, while transaction references may be kept for reconciliation, disputes or legal duties. When no valid reason remains, we remove or de-identify the record where local law permits.

You may ask for removal of eligible personal details through account support. We first verify the request and check whether a record must remain for security, payment reconciliation, dispute handling or a legal duty. We then explain what can be removed and what must remain.

Related Pages

resep4d Indonesia Live Blackjack Salon FAQ Manado Live Table Access guide