Perabet: Privacy Policy and Data Protection
Reference text for the page /privacy/. Where the received material did not confirm an essential piece of data, the point was marked as pending review.
Talk about privacy1. What this page covers
This policy explains how Perabet handles information in registration, login, browsing, support, promotions, responsible gaming, deposits, withdrawals, and mobile site use areas. The focus is transparency. When a fact was not confirmed in the current input, it appears as pending validation and not as a definitive promise.
The content applies to the web environment identified by Perabet and to the routes already published on the site. The pages of terms, cookies and contact help complete the reading.
2. What data may appear in the site flow
In account and operation areas, data provided by the user themselves may appear, such as profile information, access history, support request, and movements linked to balance, deposit, withdrawal, and promotions. The exact collection depends on the screen used and what the user chooses to send.
No sufficient input was presented to confirm mandatory collection of CPF, identity document, date of birth, full address, or banking data outside the payment context. For this reason, these points remain unconfirmed in this version.
3. What Perabet uses this information for
The data provided on the site may serve to create and maintain an account, identify the user, allow login, record deposit and withdrawal operations, respond to contact requests, manage campaigns, personalize visible areas, and meet the service's own operational requirements.
They may also be used for fraud prevention, account security, access control, and site usage analysis. If there are new purposes, they need a real basis in the platform's operation. Hidden use is not presumed, nor collection beyond what is necessary.
4. Legal bases: what can be stated now
Without the complete original policy, it is not correct to assign a specific legal basis to each operation as if everything were settled. In an environment like this, LGPD bases may vary between consent, performance of a contract, preliminary procedures, compliance with a legal or regulatory obligation, and legitimate interest, depending on the concrete task.
Where the basis has still not been proven, the correct record is simple: pending review. This avoids treating assumption as if it were final legal text.
5. PIX, balance, deposit and withdrawal
The shared navigation shows areas linked to Balance, Deposit, Withdrawal and PIX routes. The values visible in the technical material do not authorize concluding how payment is processed, which intermediaries receive data, or how long financial records are kept.
If the user provides a PIX key, name, amount, or transaction reference, these elements may circulate within the payment flow. What does not exist in the current input is confirmation about detailed retention, sharing with specific institutions, or internal financial storage rules.
6. Information security
7. Data subject rights under the LGPD
When there is an applicable legal basis, the data subject may request confirmation of processing, access, correction, anonymization, blocking, deletion of unnecessary or improperly processed data, portability when applicable, information about sharing, and review of automated decisions, within the limits of the LGPD.
The right to deletion is not absolute. There are legal exceptions that may require temporary retention or preservation due to a regulatory obligation. For this reason, removal requests need to be assessed case by case.
To request privacy support, use the official channel published in /contato/ and also follow the guidance in /faq/.
8. Cookies and similar technologies
The site has its own cookies page. That is where the categories actually used should be listed, such as technical, session, preference, performance, or advertising cookies, if any. Without the specific policy, it is not safe to state a consent manager that has not been proven.
If the browser or device blocks cookies, parts of the site may lose functions. The exact effect depends on the technology actually implemented on the platform.
9. Sharing with third parties
10. Storage, retention, and deletion
The input received did not include a fixed retention period. Therefore, the correct wording is this: the data remains for as long as necessary to fulfill the stated purpose, meet legal obligations, and resolve operational, administrative, or security issues, as applicable to the specific case.
When there is no longer a valid reason to keep the information, deletion or anonymization must follow what is technically possible and legally required. If mandatory retention exists, it must be stated in the final policy.
11. International transfer
There is no documentary confirmation, in this input, of international data transfer, destination country, or protection mechanism. Without this proof, the text must not invent cloud, external server, contractual clause, or technical standard.
If processing occurs outside Brazil, the final version needs to indicate where the data goes, why it goes there, and which legal measures support the flow.
12. Minors
The site was described as an environment for adults. This means access must follow the service’s own rules and applicable law. No automatic blocking or age-verification mechanism was presented that we can state as completed.
If misuse by a minor is detected, the responsible team will need to handle the case based on the platform’s effective rules and current law.
13. Updates to this policy
This page must show the current version and the actual update date. Since this data was not confirmed in the current material, the date remains pending review. Whenever there is a relevant change in collection, use, sharing, or contact, the policy needs to be revised.
The user should check the page at important moments, especially before sending data, making a deposit, withdrawing amounts, or opening a support ticket.
14. Quick FAQ
What data does Perabet confirm in registration?
The input received confirms at least one flow with +55 phone number, password, and password confirmation. Other fields may exist, but they were not proven here. Therefore, it is not correct to claim mandatory collection of documents, address, or banking data without seeing the corresponding official screen.
What happens to my PIX data?
The site shows PIX, deposit, and withdrawal areas, so data sent in this flow may be used to carry out the operation. What was not confirmed is the name of the financial intermediary, the retention period, and the detailed policy for recording these transactions.
Can I request access or correction?
Yes, when there is a legal basis and enough identification to locate the record. The published path for this type of request is the site’s official contact channel. Support may require validation to avoid delivering information to unauthorized third parties.
Are the cookies described elsewhere?
Yes. There is a dedicated page at /cookies/. It should concentrate the real explanation of the categories used, the purpose, and the management options, without relying on generic promises that are not confirmed in the Perabet environment.
15. Visual records of the original content
Without images provided in the input, this version does not add external visual resources. If the project has official screenshots of the page, they should be inserted only with the source already approved by the site.
If any point on this page is still without documentary confirmation, it must be treated as pending review before final publication. The effective version needs to reflect only what Perabet actually does in the site environment.