Reference

Privacy Policy for warung69 Accounts

Our warung69 Privacy Policy shows what we collect when you create an account, sign in from a mobile device, or use DANA, OVO, GoPay and QRIS.

Clear data purposesWallet status recordsAccount access choices
warung69 Privacy Policy for warung69 Accounts
CONTACT ROUTES

Privacy Help Beside Account Access

A clear support path matters when your Privacy Policy question concerns a phone check, wallet reference or stored cookie.

Account data request Use the support route near your account area to ask for a copy, correction or explanation of data linked to your warung69 profile. We may ask you to complete phone verification before discussing account-specific records.
Wallet reference check For a DANA, OVO, GoPay or QRIS privacy question, provide the payment reference and date rather than private wallet credentials. We use the reference to find the matching status record and keep the request focused.
Access concern If a cookie or device signal blocks account access, tell support which browser path you used and whether the issue appeared before or after phone verification. We can separate a security check from a general policy request.
SIX DATA CONTROLS

Six Controls Across Your Account

We handle Privacy Policy duties through practical account controls rather than vague promises. Registration data supports the account record, phone verification helps confirm who is requesting access, and device signals help us…

Data collected

We may record your account name, phone number, verification result, device details, sign-in events and payment references. The Privacy Policy connects each category to a purpose, so you can see why it is needed for account administration or security.

Cookie choices

Cookies can keep a browser session stable and help recognise an unusual sign-in pattern. Clearing them may require you to sign in again and repeat phone verification. Our policy separates necessary account cookies from optional measurement functions.

Account security

We use phone verification before account access and may compare device or sign-in signals when activity looks unusual. Never share your password or wallet PIN with support. These checks protect the account record while your request is assessed.

Payment records

A DANA, OVO, GoPay or QRIS reference can show whether a transaction was received and matched to your account. Bank transfer and virtual account records serve the same reconciliation role, without giving us control of your banking credentials.

Retention period

We retain account, security and payment records only for the period needed for their stated purpose, account queries and applicable legal duties. When a record is no longer needed, our handling follows the retention process described in this Privacy Policy.

Change requests

Ask us to correct inaccurate account data or explain a stored record through the support route beside the cashier path. Include your registered phone number and request details; we verify account control before changing or disclosing personal data.

Answers About Privacy Policy Access

These Privacy Policy answers address the searches we hear most often from people preparing an account. They cover the data connected with warung69, wallet references, cookies, phone verification, retention and requests for access or correction. If your situation is specific to a payment reference or sign-in event, use the support route beside the cashier area and describe the exact record you want us to check.

It covers personal data connected with your account, including registration details, phone verification, sign-in events, device signals, cookies and payment references. It also explains our purposes, retention approach, security checks and the route for requesting access, correction or clarification.

Our Privacy Policy does not require your DANA or QRIS password for payment matching. We use a transaction reference and status to connect the wallet event with your account. Do not send a wallet PIN, password or one-time code through support.

Open the account support route beside the cashier area and state that you are making a Privacy Policy data request. Add your registered phone number, request type and relevant date. We may complete phone verification before releasing account-specific records.

Cookies can maintain a browser session, remember a sign-in preference and help detect unusual access. Clearing cookies can sign you out and require another phone verification step. The Privacy Policy explains which cookie functions support account security and access.

Yes, you can ask us to correct inaccurate account details through the support route. Tell us which field is wrong and provide the registered phone number. We verify account control first, then assess the change under the Privacy Policy and applicable local requirements.

We keep DANA, OVO, GoPay, QRIS, bank transfer and virtual account references for the period needed for reconciliation, account questions, security checks and applicable legal duties. The retention period can vary by record type, and the Privacy Policy sets the governing approach.

The Privacy Policy applies to the warung69 website and its mobile browser path when you create or access an account. Eligibility and access depends on local law. If a regional rule affects your account, support can explain the available policy route.