Reference

Privacy Policy for Your magbet Account

Our Privacy Policy shows how magbet handles the details you provide when you open an account, sign in, verify your phone or check wallet status.

Account clarityCookie choicesWallet recordsContact steps
Browse Our Lobby Read FAQ
magbet Privacy Policy for Your magbet Account
CONTACT YOUR RECORDS

Where To Ask About Your Data

A clear contact path helps when you want to understand a record rather than repeat an account step. Use the support route connected to your magbet account and include the phone number or transaction reference linked to your request. We can then locate the relevant sign-in, wallet or verification record without asking you to send unrelated details. If a receipt or status stalls for you in Jakarta or elsewhere in Indonesia, keep the original reference ready and ask specifically about privacy handling.

Team online

Account requests

Ask us to confirm which account details we hold, such as your verified phone number or sign-in record. We will use the account path to check your identity before discussing personal data, so another person cannot obtain details simply by quoting your screen name.

Wallet records

For a DANA, OVO, GoPay or QRIS record, send the payment reference and the date shown in your account. We use those details to trace the relevant status, explain what remains stored and separate a receipt question from a request to change personal data.

Policy questions

If you want to ask how cookies, device signals or retention apply to your account, contact support through the account help path. Describe the specific Privacy Policy point you need clarified, and we can route the request without collecting extra details.

SIX DATA CONTROLS

Six Controls Behind Our Data Handling

We keep the Privacy Policy practical by linking each data use to an account action you can recognise.

Account details

We use the details you submit during account creation and phone verification to create your profile, support sign-in and answer requests about that profile. We do not need extra personal details for a question that only concerns a DANA or QRIS transaction reference.

Cookies and sessions

Cookies can keep your sign-in session connected while you move between account pages and the lobby on mobile or desktop. They may also help us remember a basic preference. You can manage cookie settings through your browser, though some account functions may then need another sign-in.

Device signals

We may record limited device and connection signals around account access to detect repeated failed sign-ins or unusual sessions. This does not give us access to unrelated files on your phone. It helps us compare the session with the account step you started.

Wallet matching

A payment reference, method label and status can be retained when you check DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. We use those records to reconcile the account event and answer receipt questions, not to build unrelated marketing profiles.

Retention periods

We retain account, security and transaction records only for as long as needed for the stated service, dispute handling, account protection or applicable legal duties. When a record is no longer needed for those reasons, our handling process removes or separates it.

Changes and deletion

You can ask us to correct inaccurate account data or explain whether a deletion request can be completed. We first verify the request through your account path, then check whether a transaction, security or legal duty requires a limited record to remain.

Privacy Policy Questions Before Account Access

These Privacy Policy answers address the account questions you may have before opening access or when checking a wallet record. We keep the wording tied to actual magbet steps: phone verification, cookie settings, device sessions, payment references and support requests. If your situation is not covered, use the account contact path and identify the exact record or policy point you want us to examine.

The magbet Privacy Policy covers account details, phone verification, sign-in activity, cookies, device signals and payment references. It explains why we use each category, how it supports an account action, how retention works and how you can ask about access, correction or deletion.

Phone verification links account access to the contact detail you provide and helps us respond safely to account requests. We may use the verified number when checking a data request or unusual sign-in, but we do not treat verification as permission to collect unrelated personal details.

Yes. The Privacy Policy covers DANA, OVO, GoPay and QRIS references shown during an account transaction, along with bank transfer and virtual account details. We use these records to match status and receipts to the correct account and to handle a related support request.

Contact us through the support path connected to your magbet account and state that you want an account data request. Include the verified phone detail or another account reference we can check. We will confirm your identity before discussing the records linked to you.

Cookies can keep your account session active and remember a basic browser preference as you move between account pages. Your browser controls whether cookies are accepted. If you block them, you may need to sign in again, while the Privacy Policy still explains the related data use.

You can ask magbet to correct inaccurate account data or request deletion through the account support path. We verify the request first, then check whether a wallet record, security need or legal duty means some data must remain for a defined period.

Yes. Account access and the handling of some requests depends on local law. We apply the Privacy Policy to supported Indonesian access where local law permits, while legal duties may affect what we can disclose, change or remove from retained records.

Related Pages

magbet Indonesia Account information Sportsbook Odds Board Padang Mega Prize magbet Casino