Reference

dewi567 Privacy Policy And Your Account

dewi567 Privacy Policy explains what we collect when you create an account, complete phone verification, browse Speed Blackjack or use a wallet option.

Account dataWallet recordsCookie choicesPhone verification
dewi567 dewi567 Privacy Policy And Your Account
REQUEST HELP DIRECTLY

Privacy Questions Get A Clear Route

A clear support route helps you ask about Privacy Policy without sending wallet credentials or repeating your account history. Use the support path shown after login and include the email or phone number linked to your account, plus the request you want handled. If access is stalled, we can first confirm the account step and phone verification status, then direct a privacy request to the right internal queue. We answer policy requests through the available account support route.

Team online

Policy request

Ask how our Privacy Policy applies to your account data, cookie choices or lobby activity. Include your account contact detail so we can match the request without asking for a DANA, OVO or GoPay password.

Wallet data check

If a QRIS, bank transfer or virtual account reference looks incorrect, send the transaction reference through the account support path. We use it to locate the record while keeping your wallet login details outside our request.

Access privacy check

When phone verification or login blocks a request, tell us the device path you used, such as mobile browser or desktop. We can separate an access problem from a Privacy Policy request before responding.

HANDLING YOUR DETAILS

What We Do With Account Data

We handle account data for defined operational reasons: providing the requested account area, checking phone verification, recording wallet status and protecting access.

Collection points

We collect details when you open an account, confirm your phone, sign in, contact support or select a payment route. Records connected with Speed Blackjack, Rocket Crash or other lobby activity are kept for account and security purposes.

Cookie controls

Cookies support sign-in continuity and selected settings on your mobile browser or desktop. You can remove or block them through browser controls, although a cleared session may require phone verification before account access returns.

Wallet separation

DANA, OVO, GoPay and QRIS status records help us match a payment event to the correct account. We do not need your wallet password, PIN or private wallet credentials to check a reference.

Account security

We use login events, device signals and phone verification to identify unusual access. If your device changes, we may ask for an account step before discussing records connected with Mega Fishing or other activity.

Retention purpose

We keep account, payment-reference and support records only while they serve service delivery, security, dispute handling or a legal duty. When a record no longer has a valid purpose, our processes mark it for removal.

Your request path

You can ask for access, correction or deletion by using the support path shown in your account area. We may verify the request with your linked phone or email before changing or releasing personal data.

Privacy Policy Answers For Your Account

These Privacy Policy answers address the account, device and payment questions we hear most often from people in Indonesia. They explain what to send, what we check and when local rules affect a request, so you can decide how to proceed before opening or using your account.

It covers account details, phone verification, login events, cookies, device signals, support messages and payment references from DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity.

Phone verification helps us confirm account ownership before access or a data request is completed. If you change devices or lose access, we may use the linked phone detail for an additional check.

No. We record the selected payment route, reference and status needed to match an account action. We do not ask for or require your DANA, OVO, GoPay or QRIS password or PIN.

Use the support path shown in your account area and ask for an account-data copy. Include your linked phone or email, then complete any ownership check we request before records are released.

Yes. Send a correction request through the account support path and identify the field that is wrong. We may confirm your phone verification before changing contact details or account records.

Cookies can keep your mobile-browser session active and retain selected settings. Clearing them through browser controls may sign you out, so the next visit can require login and phone verification again.

Yes. Access and eligibility depends on local law. Where local law permits, we handle access, correction or deletion requests; security, fraud prevention and legal record duties may limit the response.