What is covered
Registration, login, account areas, payment via PIX, support, promotions, navigation pages, and technical records linked to site use.
This page explains, in plain language, how the marsbet site handles personal data in the digital environment of the address /privacy/, what information may appear in registration, account, PIX, support, and navigation, and what rights are available to the data subject under the LGPD. When a point was not confirmed in the received material, it remains marked for review.
Registration, login, account areas, payment via PIX, support, promotions, navigation pages, and technical records linked to site use.
CPF, documents, bank details, date of birth, or any other sensitive field should not be assumed without seeing the actual form or the confirmed operation.
Confirmation, access, correction, deletion within legal limits, portability when applicable, review, and information about sharing.
Controller, privacy contact, retention, and technical measures depend on validation in the official material available for this page.
Quick reading, without excess. Each block helps you find a topic with less effort.
The policy separates registration, account use, payments, support, cookies, rights, and contact. This makes it easier to find the right information without scanning the whole page.
This page does not replace the Terms or the Cookies page. Each document covers a different part of data processing and site use.
If a piece of data, deadline, or provider did not appear in the validated material, the text does not invent it. The correct approach is to mark it as pending and review it before publishing it as the final policy.
Adult users in Brazil who want to understand how marsbet handles privacy, data protection, and formal contact channels.
The data below reflect what was confirmed in the site context. We do not expand beyond that.
| Category | Confirmed or plausible examples in the flow | Privacy note |
|---|---|---|
| Registration and access | +55 phone number, password, and password confirmation; account identification when the user logs in or recovers access. | There is no basis to claim automatic collection of CPF, document, or date of birth. |
| Profile and account | Information linked to Profile, Balance, Deposit, Withdrawal, VIP, Rebate, and Agent, according to the site flow. | The existence of the area does not prove which fields are required on each screen. |
| Payment and PIX | Operational data for deposits and withdrawals via PIX; the cited interface includes value ranges and PIX-1 to PIX-4 routes. | Storage of complete bank data or the provider's internal structure is not assumed. |
| Support and contact | Messages sent by the user, service history, and data needed to respond to requests. | The official channel must be the one published on the current site. |
| Cookies and browsing | Technical identifiers, preferences, and usage records, according to the cookies page and normal browser behavior. | Type, duration, and third-party provider need to be validated before final publication. |
The uses below follow the site flow and do not mean extra collection beyond what is necessary.
The phone number with country code +55 and access data may be used for registration, authentication, account recovery, and identity verification within the site flow.
The PIX, Balance, Deposit, and Withdrawal areas require data processing to carry out the operation, track status, and respond to discrepancies or processing failures.
Account and participation data may be used in promotions, bonuses, invitations, and internal marketing actions, always respecting the applicable legal basis and the user's choices when applicable.
Messages, access history, and technical signals help respond to support, prevent abuse, reduce fraud, and maintain operational stability.
The site may send notices about account, security, flow changes, or policy updates. There is no basis to promise a specific sending method, frequency, or channel without the official material.
The LGPD requires an appropriate legal basis for each purpose. When this is not confirmed, the text should indicate review.
| Activity | Likely or possible legal basis | Status |
|---|---|---|
| Registration and authentication | Performance of a contract or preliminary procedures related to the service; on some screens, consent may appear for specific points. | Pending formal confirmation |
| User support | Performance of the service, legitimate interest, or compliance with a legal obligation, as applicable. | Pending formal confirmation |
| PIX, balance, deposit, and withdrawal | Performance of a contract, credit protection when applicable, and compliance with legal/regulatory obligations. | Pending formal confirmation |
| Promotions and commercial communication | Consent or legitimate interest, depending on the channel and type of message. | Pending formal confirmation |
| Security, fraud, and logs | Legitimate interest, legal compliance, and system protection. | Pending formal confirmation |
Only measures that are actually verified should be included in the final version. Here, the text stays conservative.
The site should adopt controls proportional to the type of data processed. Without documentary proof, it is not correct to claim full encryption, mandatory 2FA, or any unconfirmed technical seal.
Use a strong password, do not share your access code, verify the official domain, and be wary of pages that imitate the marsbet look outside the known routes.
If browsing is done on a mobile phone, keep the system updated and review browser or app permissions, if there is an official app published in /app/.
The rights exist, but how they are exercised depends on the official channel and any legal limitations.
You may request confirmation of processing and access to personal data processed by marsbet, when there is a basis and procedure for this.
Incomplete, inaccurate, or outdated data may be corrected, subject to identity validation and internal security rules.
Deletion is not absolute. It depends on the purpose, the legal basis, and the retention cases provided for by law or regulatory obligation.
It is possible to request review of automated decisions, information about sharing, and, when applicable, objection to certain processing.
When processing depends on consent, the data subject may revoke it through the appropriate channel, without retroactive effect on acts already carried out lawfully.
The page dedicated to cookies must include types, purpose, and control. This is the general framework.
Cookies may be necessary, functional, analytical, or preference-based. The exact classification should only appear when confirmed on the specific cookies page.
In general, they help maintain sessions, remember preferences, measure usage, and understand how pages work. No management tool should be promised unless it has been verified.
If there are analytics or advertising partners, they must be clearly identified in the cookies policy or in validated technical documentation.
Without proof, there is no closed list of partners. The final text must follow what has been validated.
This may occur with service providers, payment processing, support, hosting, technical analysis, or legal requirements. The exact list must be confirmed before publishing.
Data must be kept for as long as necessary for the purpose, legal obligations, and defense of rights. No official deadline was provided to set here.
It should only be explained if there is processing outside Brazil or use of an identified foreign provider. In the absence of this proof, the item remains pending.
Behavior changes depending on whether browsing is in the browser, in the app, or in a mobile interface.
On mobile, the user accesses the same site routes and the same privacy principles continue to apply to login, account, promotions, and support.
If there is an official app in /app/, it must have a policy compatible with what it actually collects, without copying promises from the site without technical validation.
This site is aimed at an adult audience. Processing minors' data requires its own basis and flow.
When the service is aimed at an adult audience, the ideal is to block registrations incompatible with that condition and review the account flow according to the real operational rule. The existence of automatic validation must be confirmed before being stated.
Update, effective date, and history only apply with a confirmed effective date.
Use only the official channel already published on the site. If it changes, this section needs to follow.
Small habits help a lot, especially on pages with account access and payments.
Before entering your phone number, password, or PIX, make sure you are on the official site address.
Use a strong password and do not share codes or screenshots with third parties.
When using balance, deposit, or withdrawal, check the details before confirming the operation.
If a question arises about personal data, go back to the official channel of contact.
Short answers, focused on what appears on the site and what still depends on validation.
Based on the available material, the flow may involve phone number with +55, password, account data, support messages, information linked to deposits, withdrawals, PIX, and technical browsing records. CPF, document, and full banking details cannot be stated without the real form or other official proof.
Yes, registration and authentication usually depend on access and contact data. This serves to keep the account, recover login, and provide user support. The exact set of required fields should be read on the current registration screen.
These routes require data processing to process the operation, record status, and resolve inconsistencies. What can be collected depends on the actual flow. The page does not allow concluding which providers or retentions are used without additional validation.
There is no confirmed fact in the current input to state sale, commercial transfer, or any equivalent policy. The responsible text is to inform only what has been validated and, if necessary, list the real third parties that take part in the service.
Yes, you can request correction, confirmation of processing, and, where applicable, deletion. Deletion is not automatic in all cases, because the LGPD and other laws may require retention for a specific period or allow legal exceptions.
The cookie policy is at /cookies/. It should bring the types of cookies, purpose, duration, and any third parties involved. This page provides only the privacy overview.
In the received material, there is no validated email or DPO. Therefore, the indicated safe channel is the official page of contact. Any extra address must be inserted only after documentary confirmation.
Yes. If access is through the mobile browser, the same principles apply. If there is an app, the policy needs to reflect what the app actually collects and how it handles data, without copying unconfirmed hypotheses.
No original images provided in this input.
Reading this policy works best when each item is checked against the site’s real flow. If a data point, provider, or deadline has not yet been validated, the right place is review — not assumption.