Reference

Open resepwin Privacy Policy With Clarity

Our Privacy Policy explains how resepwin handles the details connected to your account, phone verification, device and wallet activity.

Account dataWallet recordsCookie choicesYour privacy requests
resepwin Open resepwin Privacy Policy With Clarity
ASK OUR TEAM

Contact Us About Privacy Policy

A clear contact path helps you act on the Privacy Policy without guessing which team to reach. Send your request through the account support route and include the email or phone detail attached to your profile, plus the issue you want checked. We use those details to locate the right record, while payment references and device details help us investigate wallet or sign-in questions.

Team online

Account request

Ask us to access, correct or explain personal data linked to your account. Include your registered phone detail so we can verify the request before discussing account records.

Wallet query

For DANA, OVO, GoPay or QRIS questions, provide the transaction reference and date. We can compare the wallet status with the account record without requesting your wallet PIN.

Login concern

If a mobile browser shows an unexpected sign-in or cookie result, tell us the device path and approximate time. We can check session records and explain the next privacy step.

DATA HANDLING

See How We Handle Account Data

Privacy work is part of each account step, from phone verification before access to a payment status check after a wallet request.

Account collection

We collect the details you submit for an account and phone verification, along with sign-in records needed to recognise your session. We use them to provide account access and respond to privacy requests.

Mobile signals

A mobile browser can send device type, browser version, IP-related signals and session events. These details help protect access and diagnose a cookie or login problem without reading unrelated device content.

Cookie choices

Cookies can keep your session available and remember selected settings. You can manage browser controls, although removing necessary cookies may require another sign-in before the account path works.

Game activity

Opening Limbo, Rocket Crash or Super Bingo may create activity records tied to your account. We use these records for account operation, security checks, dispute handling and a clear request history.

Payment records

A wallet or bank reference helps us match a payment status to your account. We do not need your DANA, OVO, GoPay or QRIS PIN to complete that record check.

Retention requests

You can ask why a record is held, request a correction or ask whether deletion is available. We may retain limited records when needed for a dispute, security matter or legal duty.

Find Privacy Policy Answers Quickly

These Privacy Policy answers address the searches we hear most often before account access. They cover the data connected to resepwin, mobile sessions, local wallets, deletion requests and the verification needed before we disclose account details. If your case is not covered, use the account support path with the relevant reference.

It covers account details, phone verification, device and session signals, cookies, game activity, payment references, retention and requests to access or correct data connected to your resepwin account.

No. Our Privacy Policy allows us to record a payment reference and status for DANA or QRIS reconciliation, but your wallet PIN is not needed for that account record.

We may use browser, device and session signals to maintain sign-in, identify unusual access and investigate a cookie issue. We do not use this process to read unrelated files on your phone.

Yes. Contact us through the account support route and identify your registered phone or email detail. We verify the requester first, then explain which account records can be provided.

You can request a correction or ask whether deletion is available. Some payment, security or dispute records may need to remain for an operational or legal reason.

We keep payment references only as long as needed for account operation, reconciliation, disputes and legal duties. When a record is no longer needed, we remove or anonymise it.

Yes. Any access or eligibility question depends on local law. We assess privacy requests under the rules that apply to your account and may explain why a specific record cannot be released.