Reference

Privacy Policy for Your Account

Our Privacy Policy shows how dewazeus33 handles the details you provide before you enter the lobby, including account records, phone verification and wallet activity.

Account dataCookie choicesWallet recordsContact path
dewazeus33 Privacy Policy for Your Account
PRIVACY CONTACTS

Where To Ask About Your Data

A clear account route helps when you want to ask about the Privacy Policy, correct a phone number or check a wallet record.

Account data request Use the signed-in account support route to ask what personal details we hold.
Correction request If your phone number, account label or contact detail is wrong, tell us which…
Wallet record check For a payment reference that looks incomplete, send the date, rail and status shown…
DATA SAFEGUARDS

How We Protect Account Data

Privacy is handled through the same account steps you already use: phone verification before access, session checks on mobile browsers and restricted handling of wallet references.

Account security

Phone verification helps connect an account request to the correct contact detail before access is granted. We also review login time, device and session signals when an account step looks unusual, while avoiding collection of unrelated files from your phone.

Mobile browsing

When you use a mobile browser from Denpasar or another Indonesian location, we may process browser type, session time and network signals to keep the page working. We do not treat ordinary lobby browsing as permission to inspect your photos, messages or other apps.

Cookie controls

Cookies can preserve a signed-in session, remember a language or help us see whether an account page loaded. You can manage browser cookie settings, but blocking essential cookies may interrupt phone verification, wallet status checks or a return to the lobby.

Payment references

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference lets us match a wallet request with the correct account. We use the reference and status supplied for that request rather than seeking access to your wider banking or wallet history.

Retention choices

We keep account, security and transaction records only for operational, dispute-handling or legal needs that apply to the service. When a record is no longer needed, we remove it or separate it from direct account identifiers where the applicable rule allows.

Change or removal

You can ask us to correct, access or remove eligible personal details through the privacy contact path in your account area. Include the request type and account label; we may verify ownership before acting, and some records may need to remain for a stated legal reason.

Privacy Policy Questions From Indonesia

These Privacy Policy answers cover the account actions people commonly ask about before opening access. We explain the practical path for data requests, cookies, phone verification and local wallet records, so you know what to include when contacting us. If a request concerns eligibility or access, the result depends on local law and the details linked to your account.

The Privacy Policy covers account details, phone verification, login and device signals, cookies, support messages and payment references. It explains why we use those records, how we protect them, how long they may remain and how you can ask for access or correction.

Open the support route inside your signed-in account and request an account data copy. Include your account label and a useful date range. We may verify ownership through the phone verification step before locating records or sending a response.

Yes. The Privacy Policy covers payment references and status connected with DANA, QRIS, OVO, GoPay, bank transfer and virtual account requests. We use those details to match an account transaction and resolve status questions, not to inspect unrelated wallet activity.

You can ask us to correct an inaccurate account label, phone number or contact detail through the privacy contact path. State the field and the correction needed. We may confirm account ownership first, particularly before changing a detail used for access.

Cookies can keep your signed-in session available, remember a selected setting and show whether an account page loaded correctly. Browser controls can block them, but essential cookie restrictions may interrupt phone verification, wallet status checks or a return to the lobby.

We retain account, security and transaction records for the period needed to operate the account, answer disputes or meet an applicable legal need. After that period, we remove or separate direct identifiers where local rules allow the change.

Use the privacy contact path shown in your account area or on the account access page where local law permits. Share your account label, request type and relevant reference, but never send a password, full wallet credential or unrelated personal files.