Reference

berkah303 Privacy Policy for Your Account

Our Privacy Policy explains how berkah303 handles your account details, phone verification, device signals and wallet records when you use our Indonesia service.

Account dataWallet recordsCookie choicesRequest support

Browse Our Lobby Read FAQ

How DANA And QRIS Data Is Used

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

Our Privacy Policy covers details you provide when opening an account, including your phone number, login credentials and verification responses. We also receive operational records when you select DANA, OVO, GoPay, QRIS, bank transfer or a virtual account, such as a reference number, amount, status and

1
timing; we do not need your wallet password. Device type, browser settings, IP-related signals and cookie identifiers can help us recognise an active session, reduce repeated login checks and investigate unusual access. Account activity may include the lobby title you open, such as Super Sic Bo
2
or Rocket Crash, when that record is needed for service support or security. We retain records for the period needed for account administration, dispute handling, security checks and legal duties. Where local law permits, you may request details about stored data, correction or deletion, subject to
3
identity checks and records we must retain.

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

CONTACT PATHS

Privacy Help Beside Your Account

A clear contact path matters when you want to ask what we store or why a wallet status appears in your account.

DATA PRACTICES

How berkah303 Handles Account Data

We apply this Privacy Policy through everyday account controls rather than broad promises. Phone verification connects a request to the correct account, while session checks help us separate your active device from…

Collection

We collect the account details you submit, verification results, transaction references and technical session data needed to provide account access and investigate a reported problem.

Cookies

Cookies may remember login state, browser preferences and security signals. You can remove or restrict them through your browser, although some account steps may then ask again.

Account security

Phone verification and device checks help us assess account access. Never send a wallet password or one-time code in a privacy request, even when asking about a receipt.

Retention

We keep account, payment-reference and security records only as long as needed for service administration, dispute checks, fraud prevention and duties required by local law.

Correction requests

You can ask us to correct inaccurate account details. Include the registered phone number and the specific field to change so we can verify ownership before editing.

Deletion requests

You may ask whether eligible data can be deleted. Some records may remain when retention is needed for security, dispute handling or legal duties where local law permits.

Privacy Policy Answers For berkah303

These Privacy Policy answers address the account questions you are most likely to have before opening access. We explain the practical records connected with phone verification, wallet receipts, cookies and device sessions, so you can decide what to submit and how to contact us. If a request concerns another person’s account, we cannot discuss it without suitable authority.

It covers account details, phone verification, device and browser signals, cookies, lobby activity needed for support, and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual accounts.

We use your phone number to create and verify the account, connect a privacy request to the correct record and help identify unusual access. We do not treat it as permission to request your wallet password.

No. Our payment records can include a reference, status, amount and timing for DANA or QRIS activity, but a wallet password is not needed for receipt checks or account support.

Use the account help path and state that you want a data copy. Provide your registered phone number and request details; we verify account ownership before sharing eligible records where local law permits.

Yes. Send the registered phone number, identify the inaccurate field and describe the correction. We review the request against the account record, then explain any reason a field must remain unchanged.

Retention depends on the record type and the reason it exists. Account, receipt and security records remain while needed for administration, dispute checks, security work or duties required by local law.

Cookies can remember login state and browser preferences, while some security cookies help assess a session. You can restrict them in your browser, but account access may then require repeated verification.

berkah303 Privacy Policy for Your Account

Privacy Help Beside Your Account

How berkah303 Handles Account Data

Collection

Cookies

Account security

Retention

Correction requests

Deletion requests

Privacy Policy Answers For berkah303

01 What does the berkah303 Privacy Policy cover?

02 Why does berkah303 need my phone number?

03 Does the Privacy Policy store my DANA or QRIS password?

04 How can I request a copy of my berkah303 data?

05 Can I ask berkah303 to correct my account data?

06 How long does berkah303 keep Privacy Policy records?

07 Do cookies affect my Privacy Policy choices?

Related Pages