Reference

Open Your warung18 Privacy Policy

warung18 Privacy Policy explains how we use the account, wallet and device details connected with your access to our lobby.

Account detailsWallet recordsDevice accessYour privacy choices
warung18 Open Your warung18 Privacy Policy
PRIVACY SUPPORT

Ask About Account And Wallet Data

A clear support path helps when your Privacy Policy question concerns a phone check, an unfamiliar device entry or a wallet reference. Tell us the account identifier, the relevant date and the payment rail shown in your record, such as QRIS or DANA. We use those details to locate the right event without asking you to send a full password or payment secret.

Team online

Account access

For a phone verification question, contact our account support route with the affected number and the approximate access time. We can check the account event while keeping your password and one-time codes private.

Wallet status

If an OVO, GoPay or QRIS reference looks unfamiliar, share the visible reference and date through the support route. We use the account record to clarify the status without requesting your wallet PIN.

Privacy request

To ask for a copy, correction or removal assessment, identify the account and describe the exact data involved. We may need an account check before changing records or disclosing personal details.

DATA PRACTICES

Explore Your Privacy Controls On warung18

Privacy choices work best when they match the way your account is used. We separate account details from general device signals, record wallet events against the relevant account, and use security checks…

Phone verification

We use your phone verification result to connect account access with the correct account step. Keep the number current, and contact support if a verification attempt was not made by you.

Mobile browser

When you use a mobile browser, we may receive device and session signals needed to keep the login path working. These signals help identify an unusual session; they do not replace your account credentials.

Cookies

Cookies and similar browser storage can remember a session choice or help us understand an access error. Your browser settings can restrict them, although some account or Privacy Policy functions may then need another check.

Account security

We expect you to keep passwords, verification codes and wallet PINs private. If an access alert or account detail looks wrong, stop sharing credentials and use the privacy support route for an account check.

Retention

We retain account, verification and wallet-status records only for the operational, security and legal purposes described in our Privacy Policy. Retention can vary by record type and by requirements that apply where you access us.

Change requests

You can ask us to correct outdated account details or explain how a particular record is used. Include the account identifier and requested change; we may verify ownership before making an update.

Browse Privacy Policy Answers For Your Account

These Privacy Policy answers focus on the questions you may have before opening an account or while checking a wallet event. We keep each route tied to a real account step, from phone verification to a mobile-browser session, so you know what to provide when asking for help.

It covers account details, phone verification results, browser and device signals, cookies, wallet-status records and privacy requests. It also explains why we use each type of record, how retention works and how you can ask for correction or an access assessment.

Phone verification links the account access step to the correct account and helps us investigate an unusual login or duplicate request. We use the verification result for account security and support checks, and you should never share the code with another person.

Yes. The policy covers references and status events connected with DANA, OVO, GoPay and QRIS, as well as bank transfer and virtual account records. We use them to trace an account event, reconcile status and answer a specific support question.

You can request a correction when an account detail is outdated or inaccurate. Send the account identifier, the field that needs attention and the requested value through the privacy support route. We may verify account ownership before applying the change.

State that you want an access assessment, identify your account and describe the records you need, such as phone verification or a QRIS status event. We will use the request details to locate the relevant records and may ask for an ownership check.

Retention depends on the type of record and the operational, security or legal reason for keeping it. Account, verification and wallet-status records may therefore follow different periods. Our Privacy Policy describes this approach, and support can clarify a specific record.

Yes. The Privacy Policy applies to access through a mobile browser and desktop browser. A mobile session can create device, cookie and session records used for account security and troubleshooting. Access depends on local law and your available account route.