Reference

berkah99 Privacy Policy For Your Account Data

Our Privacy Policy explains what berkah99 records when you open an account, verify your phone, use DANA or QRIS, and access the lobby from a device.

Account recordsWallet activityCookie choicesSecurity checks
berkah99 berkah99 Privacy Policy For Your Account Data
CONTACT PATHS

Where Privacy Requests Reach Our Team

A clear contact route helps you act on this Privacy Policy without sending sensitive credentials into an unverified channel.

Account access Use the signed-in account support path when you want to ask about stored phone…
Wallet record For DANA, OVO, GoPay or QRIS questions, send the visible reference and status from…
Correction request Tell us which personal detail needs changing and why.
DATA PRACTICES

How We Apply This Privacy Policy

We apply this Privacy Policy to the records needed for account access, payment matching and security review, rather than treating every device signal as a permanent profile.

Account details

We may store your phone number, verification result and account activity so we can connect the correct person with the…

Payment matching

A DANA, OVO, GoPay or QRIS reference can be kept with the related account record to check whether a payment…

Device signals

Your browser and device may provide sign-in time, session details and basic technical signals.

Cookies

Cookies can remember a session and selected page settings on mobile or desktop.

Retention

We retain account and payment records only as long as needed for access checks, status questions, security work or a…

Account security

Never send us your password, wallet PIN or complete security code.

Privacy Policy Answers For Your Account

These Privacy Policy answers cover the searches we hear most often before account access: what we collect, why a phone check appears, how wallet records are matched and how you can ask for a change. If your situation is not listed, use the signed-in support path and describe the exact record or cookie setting you want us to examine.

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

Phone verification helps connect account access with the correct person and helps us investigate an unfamiliar sign-in. We record the verification result, not your private wallet PIN or password.

Yes. The Privacy Policy covers the QRIS reference and status attached to your account when you use that route. Send only the visible reference if you ask support to check a payment record.

Start from the signed-in account support path, identify the detail that is wrong and explain the requested correction. We may use a phone check before changing records linked to your access.

We keep records for the period needed for account access, payment matching, security checks, support questions or a legal requirement. Support can explain the retention category for a specific record.

Yes. Clear cookies through your mobile or desktop browser settings. The next visit may ask you to sign in again, and a phone verification step may be required to reconnect access.

Access and eligibility depends on local law. Where local law permits, you can ask our support path how the policy applies to your account, device records and payment references.