Reference

Privacy at berkah123 – How We Protect You

Your account, payment details and personal information are central to how we operate.

Account security firstClear data handlingYour withdrawal rightsTransparent retention rules
berkah123 Privacy at berkah123 – How We Protect You
REACH US ANYTIME

Privacy Questions – How to Contact Us

Our support team handles privacy requests in Indonesian and English during operating hours.

Live Chat Open the chat widget in your account lobby from 08:00 to 23:00 Jakarta time…
Email Support Send privacy questions to our support inbox.
Account Settings Log into berkah123, tap your profile icon and select Privacy Preferences.
DATA SECURITY DETAIL

How We Keep Your Information Safe

Encryption protects your login and payment data whenever you connect to berkah123. We use SSL technology on all pages so your DANA, OVO, GoPay and QRIS transactions are secure in transit.

Encryption Standard

All connections to berkah123 use 256-bit SSL encryption. DANA, OVO, GoPay and QRIS transactions are encrypted before they reach our payment gateway.

Device Verification

New logins from unrecognised devices trigger a verification step. We text or email you a code to confirm it's you. Log out from other devices anytime in your account settings.

Payment Privacy

We never store your full card or DANA balance data. Only encrypted payment tokens are kept on file for faster checkout on future deposits.

Data Retention

Account data stays on file while you're active. After closure, we keep it for two years to settle disputes, then delete it. Depends on local law for any longer hold.

Access Your Data

Request a copy of everything berkah123 holds about you — account details, payment history, game activity. We compile and email it within five business days.

Cookies & Tracking

We use cookies to keep you logged in, remember your language and detect suspicious activity. You can disable non-essential cookies in your browser settings.

Privacy Questions You're Likely Asking

Real questions from our Indonesia players about how we handle data, account access and your rights.

Yes. Request account closure in your settings or contact our support team. We delete your profile data, game history and payment methods immediately. Deposit and withdrawal records are kept for two years to comply with local law, then removed. Your email can be reused for a new account after closure.

We store only an encrypted token, not your full payment credentials. The token is deleted when you remove the payment method from your account. After account closure, all payment tokens are erased. You may need to re-add your payment method if you reopen an account later.

Yes, we track deposits, withdrawals, bets and session history for your account statement and security. Log into berkah123, tap your account menu and select Transaction History. You can download a full record of deposits, payouts and dates for your records.

Only you, our support team and our fraud-prevention team (when investigating unusual activity) can access your account. Your payment processor (DANA, OVO, GoPay, QRIS or your bank) sees only the transaction details needed to process the transfer. We don't share your data with third-party marketers or game studios.

If berkah123 is acquired or merges with another operator, your data may transfer to the new owner. We would notify you by email at least 30 days before such a change. You can request deletion before the transfer takes effect, or close your account to prevent the transfer.

We record your IP address and general region for fraud detection and to ensure where local law permits plays. We don't track your precise location or sell location data. You can view your login history and the regions from which your account was accessed in your security settings.

Contact our support team immediately via live chat or email. Describe what data you believe was exposed or misused. We investigate within 24 hours and notify you of findings. If a breach is confirmed, we inform affected users and comply with local data protection notifications where required.