Reference

Privacy Policy for bewok4d Accounts

Our Privacy Policy explains how we handle the details connected to your bewok4d account, from phone verification to DANA and QRIS payment records.

Clear data purposesWallet record handlingAccount access choicesContact for data requests

Explore Our Lobby Read FAQ

What We Collect During Account Use

bewok4d Service availability depends on jurisdiction. Users are responsible for checking local law before access.

Our Privacy Policy covers data supplied when you create an account, complete phone verification, sign in, contact support, or request a wallet transaction. This can include your name, phone number, login records, device and browser signals, account activity, and payment references linked to DANA, OVO, GoPay,

1
QRIS, bank transfer, or a virtual account. We use these records to provide account access, check transaction status, protect the account from misuse, and respond to your requests. We do not treat a wallet reference as permission to access your wallet balance. Some records can be
2
shared with the payment provider or banking rail needed to process a requested transaction. Access and eligibility depend on local law. We may update this policy when our data practices change, with the current wording kept on this page.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

DATA HELP PATH

Where To Ask About Your Data

A clear support path helps when a Privacy Policy question meets an account or wallet issue. Sign in first when you can, then use the support route connected to your bewok4d account so we can match the request with the correct phone verification record. Include the relevant transaction reference, such as a QRIS or bank transfer reference, but never send a password or wallet PIN. We can explain data use, access requests, corrections, and payment-status records.

Team online

Account data request

Ask us to identify the personal details connected to your account, explain their purpose, or help you understand a phone verification record before you continue using the account.

Wallet record query

For DANA, OVO, GoPay, QRIS, bank transfer, or virtual account records, provide the transaction reference so we can trace the relevant status without asking for your wallet PIN.

Correction request

If your phone number or account detail is inaccurate, contact us through the account support path. We may ask for an account step that confirms the request belongs to you.

SIX PRIVACY CONTROLS

Six Controls Behind Our Privacy Policy

We apply the Privacy Policy across the account journey rather than only at sign-up. Our handling covers collection, access, device signals, cookies, security checks, retention, and requests to…

Purpose-based collection

We collect account details needed for sign-in, phone verification, support, security checks, and requested transactions.

Device and cookie use

Your browser or phone may send device signals and cookies that keep an account session working, remember basic settings, and…

Account security

Phone verification connects account access to a confirmed contact detail.

Payment record separation

A payment reference helps us match a requested deposit or withdrawal status, but it does not give us access to…

Retention decisions

We retain records only for the period needed for the stated account, security, transaction, dispute, or legal purpose.

Changes and contact

You can ask what personal data we hold, request a correction, or ask about deletion where local law permits.

Privacy Policy Questions From Indonesia

These Privacy Policy answers address the account and payment questions we hear most often from Indonesian customers. They explain the practical steps for checking data, changing details, understanding device records, and contacting us without exposing passwords or wallet credentials.

It covers account details, phone verification, sign-in activity, device and cookie signals, support requests, and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer, or virtual account use.

We use your phone number for account access, phone verification, security checks, and support matching. If the number is wrong, request a correction through the account support path.

Yes. The Privacy Policy covers QRIS references and status records created for a requested transaction. We do not need your QRIS wallet PIN, and we do not treat a reference as wallet access.

You can ask us to explain or identify personal data connected to your account. We may confirm your phone verification or another account step before responding, where local law permits.

Use the support route linked to your account and describe the incorrect detail, such as a phone number. We may request account confirmation before changing the record.

Device and browser signals can keep your session working and help us identify unusual sign-in activity. Cookies may also remember basic settings, with controls available in your browser.

We keep records for the time needed for account service, security, transaction checks, disputes, or legal duties. Retention depends on the record and applicable local requirements.

Privacy Policy for bewok4d Accounts

Where To Ask About Your Data

Account data request

Wallet record query

Correction request

Six Controls Behind Our Privacy Policy

Purpose-based collection

Device and cookie use

Account security

Payment record separation

Retention decisions

Changes and contact

Privacy Policy Questions From Indonesia

01 What does the bewok4d Privacy Policy cover?

02 How does bewok4d use my phone number?

03 Does the Privacy Policy cover QRIS payments?

04 Can I request my data from bewok4d?

05 How can I correct account data?

06 Why does the Privacy Policy mention my device?

07 How long does bewok4d keep my records?

Related Pages