Rujukan Laman

Your Data Policy in 5 Minutes

Before you open an account, this Privacy Policy shows how your beeg24 data is collected, used, stored, and protected across the lobby, wallet, cookies, and support contact points.

Malaysia account dataCookie choicesTouch 'n Go recordsSupport privacy
beeg24 Your Data Policy in 5 Minutes
CONTACT ROUTES

3 Ways to Reach Privacy Support

If you want to ask about this policy, correct account data, or raise a privacy concern, contact us through the route that matches your request.

Live Chat Privacy Help Use the chat panel when you need quick privacy help tied to your account, cookies, login alerts, or payment references. We may move complex requests to email so written records stay clear.
Email Data Request Send a privacy request by email when you want access, correction, deletion, or a copy of account records. Include your account name, contact number, and the change you want us to check.
Wallet Record Check For payment privacy questions, share the relevant Touch 'n Go, GrabPay, Boost dan FPX reference. We compare your request with wallet records before replying with the data we can confirm.
DATA CARE

6 Privacy Controls We Use

Privacy work is handled inside our account, wallet, and support operations, not as a separate promise outside the site.

Account Data Use

We use account data to create your login, manage wallet balances, keep session history readable, and answer support cases. Data collected for one purpose is not reused without a lawful or service-related reason.

Cookie Settings

Cookies help keep you signed in, remember language choices, and detect repeated failed logins. You can adjust browser settings, but some account and wallet pages may not work correctly without key cookies.

Payment Privacy

Touch 'n Go, GrabPay, Boost dan FPX records are stored with transaction references, status checks, and wallet results. We use them for matching payments, resolving disputes, and checking withdrawal requests.

Security Checks

Login records, device signals, and account changes help us spot access that does not match your normal pattern. If we need to confirm identity, we ask only for details relevant to the check.

Retention Periods

We keep records for service needs, legal duties, payment checks, and support history. When a record is no longer needed, we aim to delete it or remove direct identifiers where practical.

Change Requests

You can ask us to correct account data, review stored records, or explain how a data point is used. Some payment and security records may need to stay for audit or dispute reasons.

7 Privacy Questions Before You Join

These answers focus on how your data is handled when you open an account, browse the lobby, use cookies, make payments, or contact support. If your question needs account-specific checking, contact us from the same phone or email linked to your account so we can protect your records before replying.

We collect details needed to create and protect your account, such as login identifiers, contact details, wallet activity, device signals, and support messages. We also keep session records needed for account history and dispute checks.

We use payment records to match deposits, verify withdrawals, check transaction status, and handle wallet disputes. Your payment reference is linked to your account record so support can trace the issue without asking repeatedly.

Yes. Contact us with the account details you want corrected or removed. Some records, such as payment references or security logs, may need to remain for legal duties, audit checks, or unresolved disputes.

Cookies help keep your login active, remember device settings, and support basic security checks. Some session data may show which lobby pages you used, so we can keep account records accurate and detect unusual access.

Access is limited to team members and service providers who need the data for support, payment checks, security, or site operation. They receive only the data needed for their task and must handle it carefully.

Retention depends on the record type. Account records, payment references, support messages, and security logs are kept while needed for service, legal duties, disputes, or safety checks, then deleted or anonymised where practical.

Access and eligibility depend on local law and are available where local law permits. If a rule affects your account area, we may need to adjust access, retain required records, or ask for verification.