Reference

Privacy Policy for Your mega158 Account

Your Privacy Policy at mega158 explains how we handle account data, DANA, OVO, GoPay and QRIS records, cookies, and device checks before you enter Speed Baccarat, Plinko, or…

DANA data scopeOVO wallet recordsGoPay account checksQRIS privacy logsCookie choices
mega158 Privacy Policy for Your mega158 Account
CONTACT PATHS

Ask Us About Privacy Requests

Privacy questions should reach the team that can see your account trail without asking you to repeat sensitive data in public chat.

Live chat privacy queue Message us through live chat from 09:00 to 01:00 WIB. We confirm your username, last login range, and request type before passing a privacy case to the account team.
WhatsApp account check Use WhatsApp when you need a quick privacy status check for DANA, OVO, GoPay, or QRIS records. Send only masked references, then wait for our identity prompt.
Email privacy request Email works for correction, access, and deletion requests that need written follow-up. We aim to reply within 24 hours and may ask you to confirm Account > Profile details.
DATA HANDLING

Privacy Controls for Speed Baccarat Sessions

Our Privacy Policy is written around the data we actually touch: account setup, wallet activity, device access, cookie use, and support contact history.

Account data we request

During account creation, we ask for the details needed to identify you, secure your login, and connect wallet records. Keep your phone and email current through Account > Profile.

Payment privacy checks

DANA, OVO, GoPay, and QRIS records are used to match deposits, withdrawals, failed attempts, and disputes. We use masked references where possible inside support notes.

Cookie and device signals

Cookies help remember language, session status, and security prompts. You can clear them in your browser, but the next login may ask for a fresh account check.

Login safety path

From Account > Security > Devices, check active sessions and remove access you do not recognise. We may record IP range, browser type, and timestamp for risk checks.

Retention and deletion

We keep data only as long as needed for account operation, wallet disputes, security checks, and legal duties. Deletion requests are assessed against open wallet or security matters.

Changes to this policy

When we update this Privacy Policy, we refresh the page date and keep the wording tied to current account, cookie, payment, and support handling practices.

Privacy Questions Before You Open Account

These answers focus on practical privacy choices before and after you open your account. If your case involves a wallet record, device alert, or correction request, contact us with the channel, date range, and masked reference so we can locate the right account trail.

We collect the details needed to create and protect your account, such as username, password, phone, email, and payment references. We also record login time, device type, and cookie status.

We keep wallet records to match deposits, withdrawals, failed payment attempts, and privacy disputes. Support may use masked references, payment rail names, and time windows to locate your case.

Yes. Contact live chat, WhatsApp, or email using the phone or email linked to your account. We may ask you to confirm Account > Profile details before changing personal data.

Cookies remember session status, language choice, and security prompts. If you clear them through your browser, you can still access your account, but we may ask for another login check.

Open Account > Security > Devices after login. You can remove sessions you do not recognise, then contact us if the same device or IP range returns without your action.

We share data only where needed for payment processing, account security, technical hosting, support handling, or legal duties. We do not sell your personal data to advertising lists.

Send a deletion request through email or live chat with your linked contact details. We check open wallet issues, security records, and legal duties before confirming what can be removed.