Reference

burger303 Privacy Policy For Indonesia

Clear account-data handling sits beside DANA, OVO, GoPay and QRIS payment choices, so you can understand what happens before opening your burger303 account.

DATA USECOOKIE CONTROLACCOUNT REQUESTSINDONESIA ACCESS
burger303 burger303 Privacy Policy For Indonesia
CONTACT PATHS

Where To Ask About Your Data

A clear contact route helps when your Privacy Policy question concerns a login record, wallet reference or device entry.

Account contact Use the support contact inside your logged-in account to ask about collected data, a phone-verification record or a correction request. We may ask for an account detail that confirms ownership, but we will not ask you to reveal a wallet password in the message.
Payment records For a Privacy Policy question tied to DANA, OVO, GoPay or QRIS, include the payment reference and date shown in your receipt. Bank transfer and virtual account questions should include the matching reference so we can locate the correct account record.
Login concerns If a device entry or phone-verification result looks unfamiliar, use the same logged-in support route and describe the sign-in step affected. We can review the account record, explain the security action and tell you what further confirmation is needed.
DATA PRACTICE

Six Controls Behind Account Data

We keep the Privacy Policy practical by linking each data use to an account action you can recognise.

Account records

We use the account details you submit to create and maintain your login route. Phone verification can connect an access request to the correct account, while a correction request gives us a clear place to check spelling, contact details or other account fields.

Payment matching

A DANA, OVO, GoPay or QRIS reference helps us match a transaction to your account without needing your wallet password. Bank transfer and virtual account references serve the same reconciliation purpose when a receipt or status question reaches support.

Device signals

Your browser and device may provide sign-in signals such as session details or a device identifier. We use them to investigate unusual account access and explain a security check; they are not a request for files stored on your phone.

Cookie choices

Cookies can keep an account session working between the login page and the lobby. You can manage or clear them through your browser controls, although removing session cookies may require you to sign in again before viewing account areas.

Retention checks

We retain account, security and payment references only while they serve an operational, security or legal purpose. When a record no longer has a valid purpose, our process calls for deletion or anonymisation rather than keeping it without a reason.

Change requests

To request a copy, correction or explanation of your personal data, contact us through the logged-in account route. Tell us which record concerns you, and we may verify account ownership before making a change or disclosing account-linked data.

Privacy Policy Answers For Your Account

These Privacy Policy answers focus on the account steps Indonesian customers ask about most often. You can use the logged-in contact route for a case-specific response, especially when your question involves phone verification, a DANA or QRIS receipt, a device signal or an account correction.

It covers account details, phone verification, login and device signals, cookies, payment references and support contacts. It also explains why we use those records, how long operational needs may require retention, and how you can ask for a copy, correction or explanation through your account contact route.

Phone verification helps connect an account-access request with the person who controls the account. We may use its result when checking a login concern or a data request. It does not mean we need your DANA, OVO, GoPay or QRIS wallet password.

Yes. The policy covers the payment references we receive to match DANA and QRIS activity with your account, along with OVO, GoPay, bank transfer and virtual account references. The relevant bank or wallet provider handles its own processing under its separate terms.

Open the support contact shown inside your logged-in account and ask for an account-data copy or explanation. Describe the record you want, such as phone verification, a device entry or a payment reference. We may confirm account ownership before releasing account-linked data.

You can request a correction through the logged-in account contact path. Name the field that needs changing and provide the accurate replacement. We may check ownership and supporting account details first, then confirm whether the record was updated, retained for a reason or needs further clarification.

Cookies can preserve a session between account login and account pages, so the browser can recognise an active sign-in. You can clear or manage them in your browser settings. Clearing session cookies may sign you out, while other cookie choices may affect page behaviour.

Yes. Account access and eligibility depends on local law, and our policy applies where local law permits. A request may therefore need a local-law check before we provide access, make a deletion change or continue processing a particular account or payment record.