This page explains, in plain language, how 26bet may process personal data on the site 26bet, in the account area, in promotions, in support, and in the published navigation routes. When a point does not have verifiable basis in the received material, it is marked as pending validation.
The focus here is transparency. There is no generic promise of full compliance, nor any assumption about fields, partners, or retention that have not been confirmed.
The structure below was designed for quick reading. First come the practical points. Then come the legal basis, sharing, retention, cookies, data subject rights, and contact.
What can happen on the site depends on the actual use of the account, support, and published areas.
When accessing public pages, basic technical navigation data may be processed, such as device information, access logs, and interactions with pages. The received material does not confirm a closed list of cookies or analytics tools; therefore, any additional detail should be checked on the cookies page.
The platform context indicates use of +55 phone, password and password confirmation in the registration form. This does not authorize concluding that CPF, date of birth, or ID document are required fields. If these data appear in another form, the valid rule is the one from the actual form shown to the user.
The confirmed areas of Profile, Balance, Deposit, and Withdrawal show that the account may involve internal financial operations and use of PIX. What was not confirmed in the source should not be presumed: neither the storage of banking data, nor the retention method, nor who receives each piece of information.
In campaigns, bonuses, rebate, VIP, invitation, and support, 26bet may need to use account data and interaction history to communicate rules, validate participation, or respond to requests. The exact use depends on the mechanics published in each campaign and the official contact channel.
| Category | Confirmed or possible examples | Note |
|---|---|---|
| Registration | Phone number with +55 area code, password, and password confirmation | CPF, ID document, or date of birth should not be presumed without a real form. |
| Account and use | Profile, balance, deposit, withdrawal, interaction history | The level of detail in the history depends on what the platform actually records. |
| Financial operation | Data related to PIX and internal transactions | No confirmation was found of the receiving institution, wallet, or bank account. |
| Communication | Requests sent to support, contact for promotions, or account notices | The official channel must be the one published on the site. |
| Technical | Access data, browsing data, and cookies, when applicable | The exact list needs to be checked in the cookie policy. |
The confirmed registration uses a Brazilian phone number as the entry element.
There is a deposit and withdrawal flow with reference to PIX in the account areas.
Profile, Balance, Deposit, and Withdrawal appear as functional parts of the operation.
Fields, partners, deadlines, and unconfirmed measures remain pending.
The LGPD requires an appropriate basis for each purpose. In the received material, some bases can be inferred prudently, but others were not confirmed. Therefore, the correct reading is this: the legal basis must follow the real purpose, not the other way around.
| Purpose | Likely legal basis | Status |
|---|---|---|
| Account creation and maintenance | Performance of a contract or preliminary procedures | Compatible with the described operation |
| Support and assistance | Performance of a contract, legitimate interest, or compliance with an obligation | Depends on the specific case |
| Promotions and commercial communications | Consent or legitimate interest, depending on the mechanics | Pending validation by campaign |
| Fraud prevention and operational security | Legitimate interest, legal compliance, or credit protection, when applicable | Not detailed in the source |
| Legal and regulatory requests | Compliance with a legal or regulatory obligation | Applicable when there is a formal request |
The platform material confirms the existence of deposit and withdrawal flows with reference to PIX, as well as interface amounts displayed in operational areas. This does not mean that 26bet stores complete bank details, nor that all payment data is handled the same way.
If there is integration with intermediaries, a payment institution, or another partner, the name of those parties must be stated explicitly in the final policy. Without that, the point remains under review.
There is not enough basis to state specific measures such as full encryption, 2FA, automatic backups, or exclusive access controls. What can be said with confidence is that the user also has an active role: use a strong password, avoid suspicious links, check the official domain, and do not share access codes.
The data subject may request confirmation of processing, access, correction, anonymization, blocking, deletion where applicable, portability when applicable, information about sharing, and revocation of consent. Some requests may be subject to legal, regulatory, or evidence-preservation limits.
To exercise a right, use the official channel published at Contact or check the guidance at FAQ.
This page does not invent cookie categories. What is safely indicated is that the topic should be read together with the specific cookie page. That is where purposes, types, any consent management, and third parties involved, if any, should be listed.
Access: Cookie Policy.
No verifiable list of third parties was provided. So do not assume partnerships with payment processors, analytics, hosting, or anti-fraud providers. Sharing should only be described when there is factual basis, a defined purpose, and an identified recipient.
The retention period was not provided. Therefore, the final text needs to be adjusted to the real rule of the operation: keep it for as long as necessary for the purpose, compliance with a legal obligation, defense in legal proceedings, or the regular exercise of rights, whenever applicable.
When deletion is possible, it must respect legal exceptions and records that need to be preserved.
There is not enough evidence to state an international transfer of data. If 26bet uses infrastructure, vendors, or services outside Brazil, this must be described clearly, including the transfer basis and the safeguard adopted.
The site is aimed at adults. This does not replace the age check required by the registration flow and the service use rules. If there is processing of minors' data by mistake, the case must follow the applicable internal process and Brazilian law.
This policy may be revised when there is a change in flow, tool, partner, or legal requirement. The valid version is the one published on this page, with an update date that needs to be inserted in the final document when confirmed.
Use only the official channel already published on the site. If there is a data protection officer, email address, or specific form, they must appear here without guessing. In the absence of that confirmation, the text should remain pending validation.
Useful page: /contato/
What was confirmed in the material is the use of a phone number with +55 area code, password, and password confirmation. There is no basis to state mandatory collection of CPF, date of birth, or document without seeing the actual form.
Yes, the account environment shows references to deposits and withdrawals with PIX. However, the final text should not assume how the data is stored, nor which partners are involved, if that is not explicitly stated in an official document.
No. This page refers to the specific cookie content, because the list and purposes must be described where they were actually defined. The official link is at /cookies/.
Yes. The LGPD provides these rights, and the request must follow the official contact channel. Some requests may have legal limits, especially when there is a retention obligation or defense of rights.
It is only correct to say that when the third party is identified in the official material. Since that detail has not been confirmed here, sharing remains a point to validate before final publication.
If anything on this page does not match what you saw on the site, use the official contact. It is the right path for review, information requests, or clarification about data processing.
