Reference

berkah 100 Privacy Policy For Your Account

Our Privacy Policy explains what berkah 100 collects when you open an account, use the mobile lobby, or check a wallet record through DANA, OVO, GoPay or QRIS.

Clear data purposesWallet status contextRequest path included
Explore Our Lobby Read FAQ
berkah 100 berkah 100 Privacy Policy For Your Account
CONTACT ROUTES

Get Help With A Privacy Request

A clear contact route matters when you want to ask what data we hold or correct an account detail. Our support path is also available when a phone verification record, wallet reference or payment receipt needs checking against your account. Include the phone number or account identifier used at berkah 100, the request you want handled and any relevant date. We use those details to locate the right record without asking you to send a full wallet password or private sign-in code.

Team online

Account data request

Ask our support desk to locate the account details connected with your phone verification. We can explain the category of record involved, confirm the request scope and tell you what further identity check is needed before we change or disclose account data.

Wallet record check

If a DANA, OVO, GoPay or QRIS reference appears incorrectly, send the payment date, rail name and account identifier through the support path. We compare the reference with the account record and respond without asking for your wallet PIN.

Correction request

Use the same support route to ask us to correct a contact detail or clarify how a device record is used. Describe the change plainly, and keep your login password, one-time code and wallet credentials out of the message.

DATA PRACTICES

What We Do With Account Details

Privacy work is part of the account path rather than a separate promise. We limit access to records according to the task, protect sign-in activity with account checks…

Collection at account opening

When you open an account, we collect the details needed to create and protect it, including your contact information and…

Device and browser signals

Your phone or computer may send browser, device and session signals when you sign in or move through the lobby.

Cookie choices

Cookies can retain a session choice and help us understand whether a sign-in step is working.

Account security handling

We treat phone verification results, sign-in events and support exchanges as account-security records.

Retention and removal

We keep account, payment-reference and support records for the period needed for account operation, dispute handling, security checks or local…

Changes and questions

You can ask us to explain, correct or review the personal details linked to your account through the support path.

Privacy Policy Answers For Indonesian Accounts

These Privacy Policy answers focus on the questions you may have before opening or using a berkah 100 account from Indonesia. They cover account creation, wallet references, cookies, device access, correction requests and deletion. If your question involves a specific record, use the support path with the account identifier and payment date where relevant. Access and eligibility depend on local law, so the applicable position can vary by location and circumstance.

It covers personal details used for account opening, phone verification, sign-in activity, device and browser signals, cookies, support messages and payment references. It explains why we use each category, how we protect access, how retention works and how you can request correction or clarification.

We collect the details needed to create and protect your account, including contact details and the result of the phone verification step. We may also record sign-in and device signals so we can investigate unusual access. You should provide only details needed for the account task.

Yes. The Privacy Policy covers payment references connected with DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity. We use those references to match a wallet or transfer status with your account. We do not need your wallet PIN or one-time code.

Contact our support desk with the phone number or account identifier linked to berkah 100 and state whether you want an explanation, a copy request or a correction. We may ask for an ownership check before responding or changing the relevant account detail.

Cookies can keep a session choice and help us identify whether login or phone verification is working. Browser settings let you manage them. If you remove required cookies, you may need to repeat an account check or sign in again when opening the mobile lobby.

Retention depends on why a record was collected, such as account operation, payment reconciliation, security checks, dispute handling or local requirements. When a reason ends, we follow the applicable deletion or anonymisation process where local law permits. Support can explain a specific request.

You can send a deletion request through the support path with your account identifier and the details you want addressed. We assess the request against account, security, dispute and local requirements. Where local law permits, eligible records are removed or anonymised after the check.

Related Pages

berkah 100 Indonesia FAQ mpocadh About Us Account information