Reference

betchase Privacy Policy for Your Account Data

Our Privacy Policy shows how we handle the account details, DANA and QRIS payment references, and device signals connected with your betchase access.

Account clarityWallet recordsCookie choicesContact path
betchase betchase Privacy Policy for Your Account Data
CONTACT YOUR WAY

Three Routes for Privacy Questions

A privacy question should not get lost beside a wallet query, so we keep the contact route close to your account and payment records.

Account support route Open the support path from your signed-in account when you need a copy, correction, or explanation under the Privacy Policy. Include your registered phone reference, never your password.
Payment record check For DANA, OVO, GoPay, QRIS, or bank transfer questions, share the receipt reference and date only. We use those details to trace the record while limiting extra wallet data.
Access request If you cannot sign in, state that your request concerns the Privacy Policy and provide the account phone reference. We may ask for a verification step before discussing personal records.
DATA HANDLING DETAILS

Cookies, Devices and Account Records

We handle privacy through practical account controls rather than broad promises. A phone verification step helps us confirm who is asking about a record, while device and browser details help us investigate…

Account details

We collect details needed to create and maintain your account, including your contact reference and sign-in activity. The Privacy Policy explains why each category is used and when it may be removed.

Phone verification

Before we discuss sensitive account records, we may use the phone verification step linked to your account. This reduces the chance of sending personal details to the wrong person.

Device signals

Browser type, device markers, and session activity can help us spot unusual access or restore a interrupted login path. We use these signals for account security, not for unrelated profiling.

Cookie control

Cookies help keep a signed-in session working as you move from account pages to wallet status. You can manage or clear them in your browser, although some account functions may then need another sign-in.

Retention period

We keep personal records only while they support account administration, payment tracing, security checks, disputes, or legal duties. A deletion request may not remove records that we must retain.

Change requests

Ask us to access, correct, or discuss your personal data through the support route connected to your account. We may verify your phone reference before making a change.

Privacy Policy Answers for Indonesia

These Privacy Policy answers cover the searches we hear most often before account access. They explain the data connected with sign-in, local wallet records, cookies, device use, retention, and contact requests. If your situation is not listed, use the account support route and describe the specific record or account step involved.

It covers account details, phone verification, sign-in activity, device and browser signals, cookies, support messages, and payment references linked to DANA, OVO, GoPay, QRIS, bank transfer, or a virtual account.

We use the phone reference to create or verify account access and to confirm identity before discussing personal records. This Privacy Policy step helps prevent another person from receiving your account details.

Yes. It covers the payment reference, status, date, and related account record needed to trace DANA or QRIS activity. We do not need your wallet password for a support check.

You can ask for access through the signed-in support route. Mention the Privacy Policy request and the account phone reference; we may complete a verification step before releasing personal records.

Cookies can keep your browser session active while you move between account and wallet pages. You can clear or manage them in browser settings, though doing so may require another sign-in.

We retain records for account administration, payment tracing, security checks, disputes, and legal duties. The required period depends on the record, and some deletion requests cannot remove required records.

Use the support route shown in your account and describe the item that needs correction. Include a receipt reference only when relevant, and do not send your password or complete wallet credentials.