Reference

warteg55 Privacy Policy For Clear Account Control

Our Privacy Policy explains what we collect when you open a warteg55 account, use the mobile lobby in Bandung, or check wallet status through DANA and QRIS.

Account dataWallet recordsCookie choicesAccess requests
warteg55 warteg55 Privacy Policy For Clear Account Control
CONTACT ROUTES

Three Ways To Ask About Privacy Policy

A clear contact path helps when you need an answer about your Privacy Policy rights, account record or wallet reference. Start from the support route shown after sign-in, and include the phone number linked to your account without sending a password or one-time code. If access is blocked, use the contact route displayed on the account access screen so we can connect the request to the correct record.

Team online

Signed-in support

Open the support path inside your account and choose a Privacy Policy request. Add your registered phone number and the exact issue, such as a correction request or a question about a QRIS record.

Access-screen help

If you cannot complete phone verification, use the contact route shown on the access screen. We can explain the next account step without asking you to share your password, verification code or full wallet credentials.

Payment record query

For a DANA, OVO, GoPay, QRIS, bank transfer or virtual account question, include the reference visible in your cashier history. We use that detail to locate the relevant record and respond about its handling.

DATA PRACTICES

Six Privacy Controls We Keep Visible

Privacy Policy choices matter most when they match the way your account actually works. We separate sign-in records from payment references, limit account access through phone verification, and use cookies for defined…

Collection

We collect account details you submit, phone verification results, support messages and technical sign-in data. Payment references from DANA, OVO, GoPay and QRIS may be linked to your account so a status question can be checked.

Cookie settings

Cookies can keep your sign-in choice, protect account sessions and show whether a policy page loads correctly. You can manage cookie behaviour through your browser, although turning some cookies off may affect access steps.

Account security

Phone verification helps us connect account access to the registered contact detail. Never send us your password or one-time code; when a security question needs checking, we use the account path rather than requesting those secrets.

Retention

We keep records only for the operational, security or dispute purpose that requires them, including a payment reference or sign-in event. When that purpose ends, records are removed or anonymised according to our retention process.

Data changes

Where local law permits, you can ask us to correct inaccurate account details or explain how a record is used. Include the registered phone number and the specific field or event so we can avoid changing the wrong record.

Policy contact

Privacy Policy questions go through the signed-in support path or the contact route on the access screen. We may ask for account-matching details, but we will not ask for your password, one-time code or complete wallet credentials.

Privacy Policy Answers For warteg55 Accounts

These Privacy Policy answers focus on the account actions you are most likely to question before opening an account or while using the lobby. They explain how we connect phone verification, cookies, activity records and local wallet references, while keeping requests tied to the correct account and the rules that apply where you live.

The warteg55 Privacy Policy covers account details, phone verification, sign-in activity, cookies, support messages and payment references. It can also apply to records connected with titles such as Aviator Quick Arena when those records are linked to your account.

Yes. Privacy Policy handling can include the reference, amount status and account link needed to check DANA or QRIS activity. The same approach can apply to OVO, GoPay, bank transfer and virtual account references shown in your account history.

Use the signed-in support path and identify the registered phone number, then ask for the account data connected with your request. If you cannot sign in, use the contact route on the access screen; access depends on local law.

Where local law permits, you can request a correction to inaccurate account details or ask us to clarify a specific record. Tell us which field or event is wrong and provide the registered phone number so we can match the request safely.

Cookies may remember a sign-in preference, support account-session security and show whether a policy page works on your device. Browser settings can limit cookies, but some account access steps may not work correctly when required cookies are blocked.

We retain a record for the operational, security or dispute reason that requires it, including a wallet reference or phone verification event. After that reason ends, we remove or anonymise the record through our retention process.

Start with the support path inside your account, or use the contact route shown on the access screen if sign-in is unavailable. Include a clear request and matching account detail, but never send your password or one-time code.