rivalo: Privacy Policy and Data Protection
This page explains, in a straightforward way, how the site rivalo handles personal data in the web environment identified as Rivalo. The text below was organized for quick reading, with a focus on LGPD, transparency, and practical use of the site. Where verifiable facts were missing, the point was marked as pending review.
Short reading for those who want to get straight to the point
The site brings together navigation areas, game pages, bonuses, 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, abuse prevention, support, and compliance with legal obligations.
CPF, bank, date of birth, or documents should not be assumed to be collected automatically without a basis in the actual form. Here, what matters is what was actually confirmed. What did not appear in the received material remains as pending.
Page shortcuts
- What this policy is
- What data may be collected
- How we use the data
- Legal bases
- Payment and PIX data
- Information security
- Data subject rights
- Cookies and similar technologies
- Sharing with third parties
- Retention and deletion
- International transfer
- Privacy on the app and mobile
- Protection of minors
- Policy changes
- Privacy contact
- FAQ
What is this Privacy Policy?
This policy explains, in simple language, how the rivalo treats personal data when you access the site, browse the public pages, create an account, enter logged-in areas, talk to support, take part in promotions, or use features related to balance, deposit, withdrawal, and related activities.
The idea here is transparency. This policy does not replace the Terms of Use, nor does it create any promise that the site has not confirmed. When there is a conflict between this text and the service’s actual operation, the effective practice and official documents must prevail, as long as they are compatible with applicable law.
What personal data may be collected?
What is included in the collection depends on the screen you use and the interaction made on the site. In an environment like rivalo, the data may vary between registration, login, support, payment, promotions, and browsing.
Registration and account data
- phone number with country code +55, when the form requires it;
- password and password confirmation;
- account identifiers and access preferences;
- data voluntarily provided in contact, support, or promotion forms.
There is no basis in the material received to state that CPF, date of birth, full address, or documents are always required. If any of these fields exist on the actual screen, they must be described accurately in the final version.
Usage and browsing data
- pages accessed, clicks, and internal routes;
- technical information from the device and browser;
- session records and security events;
- cookies and similar technologies, when applicable.
This type of data usually helps with site operation, fraud prevention, error analysis, and improving the experience. The exact level of collection depends on the domain’s actual configuration.
| Category | Examples on the site | Confirmation status |
|---|---|---|
| Registration | phone +55, password, password confirmation | Confirmed in the summary received |
| Account and operation | Profile, Balance, Deposit, Withdrawal, VIP, Rebate, Agent | Confirmed as platform context |
| Payment | flows related to PIX and deposit amounts displayed in the interface | Confirmed as usage interface |
| Support and communication | messages sent through contact and FAQ | Confirmed as an existing area |
| Sensitive documents | CPF, RG, receipts, date of birth | Pending validation; do not assume collection |
How do we use the data?
Registration and access
To create an account, identify the user, and allow secure login to the available areas.
Account operation
To maintain balance, history, deposits, withdrawals, preferences, and activities related to site use.
Support and integrity
To respond to requests, prevent abuse, investigate failures, and comply with legal or regulatory obligations, when there is a basis.
In promotional actions, processing may also occur to validate participation, avoid duplication, record eligibility, and operate campaigns published on the pages of Promotions and Bonus. If a campaign has its own rule, it must be read together with this policy and the applicable terms.
Legal bases for processing
LGPD requires each processing activity to have an appropriate basis. Since the material received did not include the full legal matrix, below is a cautious reading, without inventing a basis.
| Activity | Possible legal basis | Note |
|---|---|---|
| Account creation and maintenance | Performance of a contract or preliminary procedures | Depends on how registration works on the site |
| User support | Performance of a contract, legitimate interest, or consent, as applicable | It needs to be aligned with the channel and the type of request |
| Fraud prevention and security | Legitimate interest, compliance with a legal or regulatory obligation | It is not limited to consent |
| Promotions and communications | Consent or legitimate interest, depending on the nature of the communication | The campaign rules must make clear the basis used |
| Tax, accounting, or regulatory retention | Compliance with a legal or regulatory obligation | The period depends on the applicable obligation |
Without a confirmed basis, there is no shortcut. Consent cannot be treated as the sole basis for everything, and immediate deletion of all data also cannot be promised without considering legal exceptions.
Payment data and PIX
The site summary indicates deposit and withdrawal flows, as well as references to PIX. This shows that data processing may cover information needed to process financial operations, validate transactions, and record account history.
What was not confirmed in the material received: receiving institution, intermediaries, exact retention time, internal fields stored at each stage, and any sharing with payment partners. These points should only be described if there is documentary proof or text published on the site.
What may appear in these routes
- deposit amount chosen in the interface;
- identification of the account linked to the operation;
- status of the withdrawal or deposit request;
- minimum data needed for authentication and fraud prevention.
Information security
The site must use measures proportional to the risk of the processing. Since the input did not include the validated technical list, this page does not state specific encryption, 2FA, periodic backup, internal access policy, or any other control that has not been confirmed.
Instead of promising what has not been verified, the correct guidance is simple: use a strong password, do not share credentials, confirm the official domain before logging in, avoid links received by message, and review the access history when that function is available.
Data subject rights under the LGPD
Whenever applicable, you may request confirmation of processing, access, correction, anonymization, blocking, deletion of unnecessary or excessive data, portability, information about sharing, revocation of consent, and review of automated decisions, when they exist.
Deletion is not absolute in all cases. The site may retain data when there is a legal obligation, regular exercise of rights, fraud prevention, audit, or another hypothesis allowed by the LGPD.
Cookies and similar technologies
The site may use cookies to keep the session, remember preferences, measure usage, and help with navigation between areas such as Slot, Live casino, Table games and Sports.
No cookie inventory was provided, so this page does not invent names, periods, or providers. If the site has a specific cookies page, it should be used to detail categories, purposes, and, when available, a management mechanism.
Also see the page of Terms of Use to understand how the navigation rules connect to the rest of the service.
Sharing data with third parties
Sharing should only happen when there is operational need, legal obligation, fraud prevention, hosting, technical support, analytics tools, or partners involved in the execution of the service. The summary received did not confirm supplier names.
Possible recipients
- infrastructure and hosting providers;
- payment services and transaction validation services, if any;
- analytics and monitoring tools;
- public authorities, when required by law.
What should not be stated without proof
- that the site “does not sell data” in any scenario;
- that all partners follow the same technical standard;
- that only authorized employees access everything;
- that processing is identical on the web, app, and internal areas.
Storage, retention, and deletion
The retention period was not stated in the material received. Therefore, the published version must indicate the actual criterion adopted by the rivalo: active account time, legal obligation, audit, fraud prevention, or another objective criterion.
When the data is no longer needed and there is no retention duty, it must be deleted, anonymized, or blocked, as applicable. If there is an obligation to keep records for a certain period, this must be made clear to the data subject.
International transfer
There is no confirmation in the current input of international transfer, destination country, or protection mechanism. So, this policy cannot state this topic as certain.
If there is use of cloud, hosting outside Brazil, or global services, the final text must state the contractual basis, purpose, and applicable safeguards, always faithfully reflecting what was actually contracted.
Privacy on the app and on mobile
The site maintains a page of App, but the material received does not confirm whether there is a native app, PWA, or only mobile access through the browser. That difference matters.
- if it is a browser on mobile, cookies, session, and web usage data apply;
- if there is a native app, there may be permissions and records specific to the operating system;
- if there is a PWA, part of the behavior may follow the browser logic, with additional installation features.
The final policy needs to separate these hypotheses, but only after confirming what actually exists on the domain.
Protection of minors
The site content is aimed at adults. If there is an age restriction, it must appear clearly on the access and registration pages. No automatic blocking mechanism was reported, so it should not be described as certain.
When the site identifies use by a minor, the response must follow the law and valid internal routines, without promising a procedure that has not been documented.
Changes to this policy
This policy may be updated to reflect changes on the site, in registration flows, in the use of cookies, on payment pages, or in legal requirements. The current version must show the review date and the effective date, if any.
If the change is relevant, the ideal is to communicate it on the site itself or through a channel compatible with the user's account. There is no basis, in the material received, to promise individual notice in all cases.
Privacy contact
The official privacy channel was not confirmed in the summary received. Therefore, this page directs users to use only channels already published on the site itself, especially the page of Contact.
If the site publishes a data protection officer, privacy email, or dedicated form, that information must replace the pending text above. Do not invent contact details, do not use an old reference, and do not reuse an address from another project.
Practical tips to protect your data
Check the domain
Before typing a password or making a deposit, confirm that you are on Rivalo.
Protect your account
Use a strong password and do not share your access code, proof of payment, or credential with third parties.
Review messages
Be wary of links received by chat, email, or social networks that ask for login or payment outside the official flow.
FAQ
What data does rivalo collect during registration?
Based on the material received, the form may involve a phone number with +55, password, and password confirmation. Other fields, such as CPF, date of birth, or document, were not confirmed and should not be assumed without checking the actual screen.
Does rivalo use my data to operate account and balance?
Yes, when you create an account, access logged-in areas, check your balance, make a deposit, or request a withdrawal, the site may process data needed for authentication, transaction records, and support. The exact scope depends on the real flow published on the domain.
Does the site store PIX data?
It may store what is necessary to process the transaction, validate payment, and record history. However, the summary received did not state which fields are kept, for how long, or with which partners. These details need to be confirmed before final publication.
How does rivalo handle cookies?
The policy allows the use of cookies and similar technologies for session, browsing, preferences, and usage analysis. Since there was no technical inventory, this page does not list specific names, periods, or providers.
Can I request access to or deletion of my data?
Yes. The LGPD guarantees rights to the data subject, including access, correction, confirmation of processing, and, in certain cases, deletion. Deletion may be subject to legal exceptions, so the request will be assessed according to the applicable basis and obligation.
Does rivalo share data with third parties?
Sharing may occur with hosting, payment, support, analytics, or authority providers, when necessary. Since the providers were not listed in the summary, this version does not name partners or promise the complete absence of sharing.
Is there an official privacy contact?
The specific contact was not confirmed in the material received. Until the data is validated, use only the official channels already published on the site, especially the page of Contact.
Does this policy apply to app and mobile?
It covers the web environment described here and can be adapted to mobile, but the native app was not confirmed. If there is a proprietary app, the policy must separate what is mobile browser, PWA, or installed app.
Conclusion
The privacy page of the rivalo exists to explain how data is handled on the site, which rights the data subject may exercise, and where to ask for guidance when there is doubt. If any field is still pending — such as controller, official contact, retention, or international transfer — the ideal is to validate it before final publication.
To keep browsing, also check Terms, FAQ and Contact.