This page explains, in a straightforward way, how 50win handles personal data on the site 50win and in the public and account areas available in /, /app/, /bonus/, /cassino-ao-vivo/, /sports/, /jogos-de-mesa/, /slot/, /promocoes/, /faq/ and /contato/.
In the received materials, there is confirmation of use of +55 for registration, password, password confirmation, balance areas, deposit, withdrawal, VIP, rebate, promotions, and payment routes via PIX. Other fields only go here when they are confirmed in the official material.
First come the data that the input actually shows: login with +55, password, password confirmation, account access, balance, deposit, withdrawal, PIX, campaigns, and game areas. This avoids guessing and keeps the reading faithful to what exists on the site.
Each use of data needs a clear reason: create an account, authenticate access, process payment, respond to contact, comply with legal obligations, prevent abuse, and run promotions when applicable. A generic purpose does not solve it.
Not everything depends on consent. In account operations, security, fraud prevention, and compliance with obligations, other LGPD bases may apply. When the input did not provide the exact basis, the point remains pending review.
The list below includes only what could be confirmed in the context sent. Where there is a gap, the text indicates review.
| Category | Examples confirmed or suggested by the flow | Status |
|---|---|---|
| Registration and access | +55, password, password confirmation, account identification | Confirmed in the received material |
| Account and operation | Balance, deposit, withdrawal, VIP, rebate, platform usage history | Confirmed as a product area |
| Payment | PIX flow, amounts shown in the deposit, operation record | Confirmed as functionality |
| Support and communication | Messages sent through the official form, contact via internal channel | Pending detailing |
| Technical and navigation | Cookies, IP, device type, pages visited, usage events | Pending specific validation |
| Sensitive data or documents | CPF, document, bank, date of birth, biometrics | Not presumed; only with proof in the actual form |
Allow registration, login, access recovery, and maintenance of the user's session.
Display balance, process deposit and withdrawal, and organize areas such as VIP, rebate, and promotions.
Reduce misuse, fraud, unauthorized access, and attempts to manipulate the account.
Respond to requests sent through official channels and follow up on account-related requests.
Without the full formal text, this section must be read as technical draft. The use below indicates the basis that normally applies to the type of processing, but the final confirmation depends on the official notice from 50win.
| Processing | Likely legal basis | Note |
|---|---|---|
| Account creation and management | Performance of a contract or preliminary procedures | Depends on the registration flow actually used |
| Authentication and security | Legitimate interest, performance of a contract, or legal obligation, as applicable | Should not be limited to consent |
| Deposit, withdrawal, and PIX | Performance of a contract and compliance with a legal/regulatory obligation, if applicable | Financial operation requires document validation |
| Support and communication | Performance of a contract and legitimate interest | When the request comes from the data subject |
| Marketing and promotions | Consent or legitimate interest, depending on the channel and internal rule | Must be described in the official text |
| Retention and legal obligations | Compliance with a legal or regulatory obligation | Final deadline was not provided in the material |
The received material shows screens and references to PIX-1 to PIX-4, as well as fields for Deposit, Balance and Withdrawal, with values displayed in the input flow. This confirms the presence of the payment journey, but does not allow us to conclude who the recipient is, where the data is stored, or for how long.
If 50win processes payment information, the official text must clearly state: which data passes through the flow, which partner is involved, whether there is additional validation, and what the retention period is. Without this, the policy is incomplete.
This text does not promise unverified measures. Only practices that can be supported by the received material and the visible operation of the site are included here.
No sufficient input was provided to assert 2FA, full encryption, periodic backup, restricted access policy, or any other specific technical control.
The data subject may request confirmation of processing, access, correction, anonymization, blocking, deletion of unnecessary data or data processed in noncompliance, portability when applicable, information about sharing, and review of automated decisions, within the limits of the law.
They may also withdraw consent when that is the basis used. This does not automatically erase records that must be kept due to legal obligation, fraud prevention, regular exercise of rights, or another hypothesis provided for in the LGPD.
The cookie policy needs to go hand in hand with this page. When the site uses cookies, the notice must explain purpose, duration, categories, and any third-party participation. 50win keeps the specific page at /cookies/.
Without additional technical confirmation, this version does not invent a consent manager, a banner with non-functional buttons, or a supplier list. If the operation uses analytics, advertising, or login sessions, that must appear in the dedicated cookie document.
Sharing may occur with providers that help operate the site, process payments, verify identity, host services, measure usage, and comply with legal obligations. The final text needs to name the actual types of recipients, without promising “we never share” when that has not been confirmed.
If there is a PIX, antifraud, analytics, or external support partner, the policy must point out its role. If there is no confirmation, the field remains pending.
The retention period was not informed in the inputs. Therefore, this version does not create a number, month, or “fixed period.” The correct wording is that the data is retained for the time necessary for the stated purpose, for legal compliance, abuse prevention, and defense in proceedings, according to the applicable basis.
When deletion is possible, it must respect legal exceptions and operational requirements. A data subject request does not require immediate deletion of everything.
There is not enough evidence in the submitted material to state an international transfer or the mechanism used for it. If 50win uses hosting, analytics, anti-fraud protection, or support outside Brazil, that information needs to appear objectively and separately.
The site content is aimed at an adult audience in Brazil. If a minor tries to use the platform, the final policy must indicate how 50win handles this situation within the law and the internal rules already approved. Without an official basis, no automatic blocking or instant deletion is promised.
The correct version must include the update date and how changes will be published. Since that date was not provided in the input, it remains pending insertion. When there is a revision, the page must be replaced with the text actually in force.
Use only the official channel published by 50win at /contato/. If there is a data protection officer, the name and contact method must be shown in the official document. Since this was not validated in the data received, there is no invented email, phone number, or DPO here.
When 50win updates this policy with verified data, the page must reflect what is actually processed, by whom, for what purpose, and on what legal basis. Good transparency does not depend on volume; it depends on precision.
Contact · FAQ · Terms · Cookies · Responsible gaming
This text was assembled from what is confirmed in the received inputs. Items without documentary proof remain pending review.
