Privacy Policy • 21bet.plus

21bet: Privacy Policy and Data Protection

This page explains how the domain 21bet.plus handles personal data in the web environment identified as /privacidade/. The text below was structured for quick reading, with a focus on transparency, LGPD, and the practical use of the site. Where verifiable facts were missing, the point was marked for review.

Controller Not informed in the data received — field pending validation.
Privacy contact Not confirmed in the material sent. Use only the official channel already published on the site.
Update Date not provided in the current input. It is recommended to insert the effective version.
Scope Site, account, support, promotions, cookies, PIX, and navigation areas of the domain.

Short reading for those who want to get straight to the point

The site brings together entry routes, game areas, promotions, FAQ, and contact. In operations such as registration, account access, deposits via PIX, withdrawals, VIP, rebate, and campaigns, some personal data may be processed for authentication, account operation, fraud prevention, support, and compliance with legal obligations.

You should not assume automatic collection of CPF, bank details, date of birth, or documents without a basis in the actual form. What counts here is what was actually confirmed. What did not appear in the material remains pending.

LGPD Personal data Cookies Data subject rights Account security PIX

Useful site routes

The pages below help the user understand the operation and locate additional information without leaving the domain.

What this policy covers

The policy exists to explain, in plain language, which data enters the site flow, why it is used, and with whom it may be shared. It also organizes what happens in cases of registration, browsing, coupon use, sending a message to support, PIX operations, and access to internal account areas.

It does not replace the Terms of Use. The two pages work together: the terms deal with the rules of the experience, while the privacy policy deals with data processing.

Important review point: the received input did not confirm the controller, the data protection officer, the effective date, or the payment providers. These items need to be filled in with the official text before final publication.

Which personal data may be collected

The site form and routes indicate use of +55 for phone number, password, and password confirmation during registration. From there, handling may vary depending on whether the user logs in, deposits, withdraws, participates in campaigns, or contacts support.

Category Verified or plausible examples in the site flow Typical purpose Status in the material
Registration and login Phone number with +55, password, password confirmation, account identifiers Create account, authenticate access, recover session, prevent unauthorized access Partially confirmed
Account and operation Profile, balance, deposit, withdrawal, transaction history Run account features and track transactions Confirmed as a product area
PIX and payments PIX-1 to PIX-4 flows, amounts shown between R$ 10 and R$ 50.000 Process deposit or withdrawal and validate the operation Confirmed as interface
Promotions and VIP Participation in bonus, rebate, referral, seven VIP levels, and associated benefits Manage eligibility, unlock benefits, and record offer usage Confirmed as a business feature
Support and contact Messages sent to the official channel, support records, reply to the user Respond to requests and resolve incidents Dependent on the official channel
Technical data IP, date/time, browser, device, cookies, and logs Security, auditing, stability, and usage analysis Not detailed in the input

If there is collection of CPF, identity document, proof of ownership, PIX key, address, or email, this must appear explicitly in the form or in the official policy. Without that confirmation, it should not be invented.

How the data is used in practice

1

Log in and authenticate

Phone number, password, and technical signals help open the account, maintain access, and reduce unauthorized login attempts.

2

Operate balance and PIX

Deposit, withdrawal, and movement require operational validation. The system needs to record the request and status.

3

Serve and audit

Support messages, campaign history, and logs can be used to resolve tickets and review inconsistencies.

Most common cases

  • create and manage the account;
  • unlock internal features, such as balance, withdrawal, and profile;
  • process promotions, bonus, rebate, VIP, and referrals;
  • comply with legal, regulatory, or fraud-prevention requirements;
  • respond to requests on the official support channel.

Legal bases for processing

Not every use of data depends on consent. In account operations and security, other bases may apply. When the purpose is unknown or not yet confirmed in the official text, the passage should be marked for review.

Processing Potentially applicable legal basis Note
Registration and authentication Performance of a contract or pre-contractual procedures Depends on the final policy and the actual account creation flow.
User support Performance of contract and legitimate interest, as applicable It is necessary to align with the support channel used.
PIX and financial operations Performance of contract, legal/regulatory obligation, and fraud prevention The payment provider was not mentioned in the material received.
Promotions, bonuses, and VIP Performance of contract, legitimate interest, or consent, depending on the campaign The offer and opt-in need to be described precisely.
Cookies and measurement Consent for non-essential cookies, if there is a banner or manager A preferences panel was not proven in the input.
It is not correct to declare “LGPD fully complied with” without document review. The final text needs to reflect the real operation, the real vendors, and the real governance of the domain.

Information security, retention, and deletion

The material sent did not confirm measures such as specific encryption, 2FA, backup policy, or profile-based access control. Therefore, it is only safe to state that the site must adopt technical and organizational measures compatible with the risk of processing.

In practice, it is common to keep records for a period compatible with operations, support, anti-fraud, and legal requirements. If there is a retention obligation, it takes precedence over an immediate deletion request. The data subject may request deletion when the legal basis allows it, but not everything can be removed right away.

  • keep the password in a private environment;
  • always check the domain before entering data;
  • avoid resending receipts through unofficial channels;
  • use trusted devices for PIX and login.

Data subject rights under the LGPD

The user may request confirmation of processing, access, correction, anonymization, blocking, deletion when applicable, portability within the limits of the law, information about sharing, and review of automated decisions, if any exist.

It is also possible to withdraw consent when that basis was used. This does not automatically erase data that must be kept due to legal obligation, fraud prevention, or defense in legal proceedings.

A

Identify the request

Explain whether you want access, correction, deletion, information about sharing, or withdrawal of consent.

B

Use the official channel

The request must follow the contact actually published on the institutional page or in the support area.

C

Wait for analysis

Some data may require identity validation and review of legal obligations before any final response.

Cookies and similar technologies

Browsing the domain may use cookies, pixels, or technical records to remember the session, measure stability, and understand usage. The input did not confirm a consent manager, so the final text must reflect what actually appears on the page /cookies/.

  • Essential: allow login, browsing, and session maintenance;
  • Operational: help with account, balance, withdrawal, and internal routes;
  • Analytical: measure accessed pages and performance, if enabled;
  • Marketing: may be used in campaigns and promotions, if there is a basis and proper notice.

If the visitor wants to review preferences, the cookies page should centralize that guidance. Without that panel, the user needs clear instructions in the text itself.

Data sharing with third parties

The material sent did not list specific providers. Therefore, it is not correct to name payment, hosting, analytics, or anti-fraud companies without proof. What can be said is that sharing, when it occurs, usually serves to process payment, maintain infrastructure, provide support, or comply with the law.

If the user uses PIX, the journey may involve institutions participating in the payment arrangement. If there is an external communication tool, it must also be disclosed. All of this needs to appear concretely in the final text.

Do not use the phrase “we do not sell data” as an automatic formula. Include it only if the official policy really addresses this point and in a verifiable way.

Storage, retention, and international transfer

The retention period was not stated in the material received. The actual text must indicate how long each data group is kept or what criterion defines deletion. Without this, the reader is left without a practical reference.

There was also no confirmation of international transfer. If there are servers, tools, or vendors outside Brazil, the policy must state the flow and the basis used for that transfer, with the appropriate protection.

Minors, policy changes, and contact

Protection of minors

If the site is not intended for minors, this must be stated expressly. If there is accidental collection, the review procedure needs to be described in the official text, without promising automatic blocking that does not exist.

Changes to this policy

This page may be updated to reflect changes in product, vendors, payment methods, support, or legal requirements. The effective date must appear in the published version.

Privacy contact

Use only the contact channel that is actually confirmed for the domain. If there is a specific support or contact page, it must guide the submission of privacy requests. When there is a data protection officer, the name and official channel need to be included based on documentary evidence.

Frequently Asked Questions

What data does the site actually ask for during sign-up?

Based on what was confirmed in the material, the sign-up flow uses a phone number in +55 format, password, and password confirmation. Other fields, such as CPF or date of birth, should not be assumed unless they appear in the actual form.

What can be used for deposit and withdrawal?

The interface shows operations related to balance, deposit, withdrawal, and PIX, including value ranges displayed between R$ 10 and R$ 50.000. This describes the site journey, but it does not authorize inventing which institutions process the money.

Do user data go into promotions and VIP?

They may, if the offer mechanics require eligibility, usage history, or participation in campaigns. The final text must say which data are used for each bonus, rebate, referral, or VIP level.

Can I request access to or correction of my data?

Yes. The LGPD provides for access, correction, and other similar requests. The request must follow the official channel published by the domain and may require identity confirmation before a response.

Are all cookies mandatory?

Not necessarily. In general, essential cookies keep the session and access active. Analytics or marketing cookies depend on what was actually installed and on the notice shown to the user.

Does the deletion request erase everything immediately?

No. Deletion may be limited by legal obligation, defense of rights, fraud prevention, or minimum record retention. What can be removed immediately must be defined case by case.

How do I contact privacy support?

Use the domain's official contact page or the channel indicated in support. Without this confirmed information, it is not correct to publish an invented email or phone number in the policy.

Does the site handle data on mobile the same way?

Processing on mobile follows the same logic as the site, but there may be differences if there is an app, PWA, or native permissions. Since this detail was not confirmed, the final text should separate mobile web from app, if necessary.

Here is the version for final review

This structure prioritizes clarity, LGPD, and quick reading. Before publishing, confirm the controller, the official privacy contact, the update date, the vendors involved in PIX and cookies, and the actual retention periods. Without this check, the page remains an operational draft.

Domain version: 21bet.plus/privacidade/ · Language: pt-BR · Scope: site, account, payments, support, and cookies.