What is included in processing
Registration data, account use, browsing, support, and interactions linked to site areas may be processed according to the actual operation.
This page explains how 365bet handles personal data in the site environment, with a focus on registration, account access, browsing, support, promotions, cookies, and routes linked to PIX and gaming areas. Where the received material did not provide enough confirmation, the excerpt is marked for review.
Registration data, account use, browsing, support, and interactions linked to site areas may be processed according to the actual operation.
Automatic collection of CPF, bank details, documents, or date of birth is not inferred without a basis in the form or confirmed flow.
Registration, contact, FAQ, terms, cookies, promotions, and gaming pages help explain the context of use and support for the data subject.
Controller, privacy contact, retention, sharing, and international transfers need validation before becoming a formal promise.
The available material shows access routes, gaming areas, promotions, FAQ, app, contact, and institutional pages. This helps describe the site’s function, but it does not replace confirmation of the legal and operational facts required by the LGPD.
| Purpose | Practical examples on the site | Compliance note |
|---|---|---|
| Registration and authentication | Account creation, login, access confirmation, and session security. | The exact fields depend on the confirmed form. |
| Account operation | Profile, balance, deposit, withdrawal, VIP, rebate, and activity tracking. | Use only what was verified in the real screens and flows. |
| Support | Contact, FAQ, answers to questions, and handling of the data subject's requests. | The official channel must be the only one used for formal requests. |
| Promotions and communications | Campaigns, bonuses, promotions, and operational notices. | Legal basis and opt-out need to be confirmed case by case. |
| Security and fraud prevention | Account protection, integrity checks, and analysis of suspicious events. | Do not state unverified measures as a closed standard. |
The LGPD allows different processing activities to use different legal bases. For a valid policy, each purpose needs to point to the correct basis. In the material received, not all bases were confirmed. Therefore, the text must record what is validated and mark the rest as pending review.
In general, registration and account operation may involve contract performance or preliminary procedures; support and regulatory obligations may depend on legal compliance; promotional communications and certain cookies may require consent, when applicable. This needs to be aligned with the site's real flow.
The environment shows references to PIX-1, PIX-2, PIX-3, and PIX-4, as well as deposit navigation with amounts displayed between R$ 10 and R$ 50.000 and shortcuts for balance, deposit, and withdrawal. These elements describe the user experience, but do not authorize assuming who processes the payment, where the data are stored, or how long they are kept.
If there is a payment intermediary, antifraud service, or external validation, this must be included in the policy with the correct third-party name and its real function. Without that confirmation, the text must keep the field under review.
No specific technical measures were provided in this input that would allow promising full encryption, 2FA, regular backups, or any closed security standard. These statements must not be included without validation.
The LGPD guarantees the data subject, as applicable, confirmation of processing, access, correction, anonymization, blocking or deletion of unnecessary data or data processed in noncompliance, portability when applicable, information about sharing, revocation of consent, and review of automated decisions, if any.
Deletion is not absolute. Retention may occur when there is a legal or regulatory obligation, regular exercise of rights, or other situations permitted by law. The request must follow the official contact channel confirmed by the site.
Cookies can serve different functions: basic operation, remembering preferences, browsing analysis, and, when there is a valid basis, campaign support. The cookie policy should detail categories, duration, providers, and management methods.
Here, the text can only state that the site has a dedicated cookies area. There is no basis in this input to declare a specific manager, partner list, or consent panel with features that were not confirmed.
Sharing with third parties should only appear in the policy if the third party and purpose have been verified: for example, hosting, technical analysis, support, payment, fraud prevention, or compliance with a legal obligation. Without this, the description needs to remain conservative.
The same applies to retention and deletion. Without a confirmed period, use the logic of operational necessity, legal obligation, and defense of rights, without inventing days, months, or years.
International transfer also requires proof. If there is storage or access outside Brazil, the policy needs to indicate the scenario and the corresponding contractual or legal basis. At this time, that point remains pending.
The site has an app route and navigation adapted for smaller screens. That does not mean, by itself, that there is a native app with camera, location, or contacts permissions. If the experience is only mobile web or PWA, the text must say exactly that.
Any device permission needs to be described objectively and tied to the real function. Without confirmation, access to sensors, files, or notifications should not be listed as a standard requirement.
The site is described as an environment for adults. The policy should reinforce that use is restricted to adults under the applicable legislation in Brazil and that, if there is suspicion of improper registration, the official channel must be contacted for review.
Changes in operation, features, partners, or legal requirements may require a review of the text. The published version must include the effective update date and, when there is a relevant change, inform the user through a reasonable means within the site or the contact channel.
The material received did not confirm a name, email, or data protection officer. Therefore, the privacy contact should follow only the official channel already published on the domain.
The material confirms use of +55 phone number, password, and password confirmation in the registration flow. Other fields, such as CPF, date of birth, or document, cannot be assumed without direct verification of the actual form.
The data may be used to create and authenticate an account, operate areas such as balance, deposit, and withdrawal, respond to support, organize promotions, and support technical functions of the site. Each purpose must be aligned with the correct legal basis.
Yes. The site has its own cookie route. It should detail categories, duration, purpose, and, when confirmed, providers and management method. This page only points out the existence of that area.
Yes. The LGPD provides for access, correction, confirmation of processing, and other rights, as applicable. The request must follow the official contact channel disclosed on the site and may require identity validation.
Not always. Deletion may be limited by legal obligation, defense of rights, or other situations allowed by the LGPD. The request is reviewed case by case, without a promise of absolute deletion.
No. The presence of PIX and deposit screens shows the user journey, not the final destination of the data. To state storage, sharing, or retention, it is necessary to confirm the actual flows and the third parties involved.
Use the site's official contact channel. If there is an FAQ page or terms with specific instructions, follow that path. Do not send sensitive data through unconfirmed channels.
Without confirmed image resources in this input, the policy remains focused on the text and legal organization. If the original page has institutional images, they may be kept only when the file and context are truly part of the published page.
Transparency here is not a slogan. It is saying what the site actually does, what still needs to be confirmed, and which channel the user should use when they want to exercise their rights.
Separate whether the request is for access, correction, deletion, support, or a cookie question.
Send the message only through the contact published on the site, without unconfirmed external shortcuts.
If necessary, confirm minimum data to avoid improper access to the user's request.
Some requests may depend on legal obligation, security, retention, or technical review.