Reference

Privacy Policy For Clearer Account Access

dewi567 Privacy Policy explains what we collect when you create an account, verify your phone, browse Auto Roulette Live or use DANA and QRIS.

Account clarityWallet contextMobile sessionLocal-law access
dewi567 Privacy Policy For Clearer Account Access
CONTACT ROUTES

Get Privacy Help Near Account Access

A clear contact route matters when you need a copy of your data or want a correction made.

Account request Use the privacy contact route beside account help to ask what personal data we hold. Include your registered phone number and the specific request, while leaving out passwords, wallet PINs and complete bank details.
Wallet record For a DANA, OVO, GoPay or QRIS record, share the transaction reference and date rather than private wallet credentials. We use those details to locate the receipt status connected with your account.
Access difficulty If a privacy request is blocked by a login or phone verification issue, tell us which device path failed. We can direct the request through account help without asking you to publish personal details in a game or lobby message.
HANDLING DETAILS

Your Device And Wallet Data Choices

Privacy choices should be practical, so we explain how account records, browser signals and payment references move through ordinary account activity.

Account records

We use your registered phone number and verification result to connect you with the right account. If those details change, contact us before creating another account so we can assess a correction without mixing two identity records.

Cookies and sessions

Cookies and device signals can record a login session, language choice and security event. Clearing browser storage may sign you out or require phone verification again; it does not automatically erase records that must remain for an open request.

Payment matching

A DANA, OVO, GoPay or QRIS reference helps us match a receipt to your account. We use the reference and status rather than asking for your wallet PIN, and we can check a stalled cashier record from that identifier.

Account security

Phone verification and session checks help us distinguish your account access from an unfamiliar device. Never send a password or wallet credential in a support message; we will use account questions and transaction references instead.

Retention choices

We retain records only for the period needed for account security, payment matching, dispute handling or a legal requirement. Your request can ask which category remains and the reason, including records linked to bank transfer or virtual account activity.

Request changes

You can ask us to access, correct or remove eligible personal data through the privacy contact route. State the requested action and account phone number; we may verify ownership before changing a record or confirming that removal is possible.

Privacy Policy Answers For Your Account

These Privacy Policy answers address the account questions you may have before using the Indonesian access path. We focus on the records created by phone verification, mobile browsing, wallet matching and support contact, rather than describing unrelated lobby functions. If your question is not listed, use the privacy contact route with the smallest useful set of account details. Eligibility and access depends on local law.

The dewi567 Privacy Policy covers account details, phone verification, device and browser signals, cookies, support messages and payment references. It explains why we use each category, how long records may remain and how you can request access, correction or removal where that action is available.

No wallet PIN should be sent to us through account help or a privacy request. For DANA and QRIS checks, we use a transaction reference, status and related account details to match a receipt without asking you to disclose private wallet credentials.

Phone verification connects an account request to the person who controls the registered number and helps us respond to data requests safely. It may be requested again after browser storage is cleared or when an unfamiliar device creates a new session.

Yes. Send an access request through the privacy contact route and include your registered phone number plus the categories you want checked, such as account, device, cookie or payment records. We may verify ownership before releasing personal data connected with your account.

Tell us which field is wrong and provide the relevant account phone number or transaction reference. For DANA, OVO, GoPay, QRIS, bank transfer or virtual account records, the date and reference help us locate the entry before we assess the correction.

Submit a removal request through the privacy contact route and identify the account record concerned. We assess whether the data can be removed or must remain for security, payment matching, dispute handling or a legal requirement, then explain the result.

A mobile browser may create cookies, session identifiers and security signals that help maintain account access. Clearing storage can sign you out and trigger phone verification again, while records needed for a privacy request or payment check may remain for their stated purpose.