Privacy Policy

Last updated: .
This is a translation of the original Portuguese version.

1. Who we are and how this Policy applies

Rifa Digital (“RD”) is a software platform (SaaS) maintained by M&M Negócios Digitais Ltda., registered with the CNPJ under No. 45.784.382/0001-20, headquartered in São Bernardo do Campo/SP. RD offers technological tools for Organizers to create, publish and manage their own Campaigns, and for Contributors to make reservations and Contributions.

This Privacy Policy clearly explains which personal data RD collects, what it uses them for, with whom it shares them, how long it keeps them and how you can exercise your rights, under the General Data Protection Law (Law No. 13,709/2018 – LGPD). It applies to the Site, the dashboard, the apps and RD’s other Services and must be read together with the Terms of Use, which contain the definitions used here.

Data Protection Officer (DPO): juridico@rifa.digital.

Third-party sites and platforms accessed from RD (social networks, payment institutions, external links) have their own policies, for which RD is not responsible. We recommend reading those policies whenever you leave our Site.

2. Who decides about your data

a. RD as controller. RD is the controller of the data it collects to operate the platform: registration, age verification, payment of the publication fee, security, support and compliance with legal obligations.

b. Organizer as controller. When you make a reservation or Contribution, the data necessary for the Campaign (such as name, contact details and reserved quotas) are made available to the Organizer, who becomes the controller of those data in relation to you, independently of RD. The Organizer may only use them to carry out the Campaign (contact, delivery of Items, communication of the result) and is responsible for that use.

c. Payment Institutions. Contribution payments are made directly through the Payment Institution chosen by the Organizer, which is connected to the platform by a purely technical integration, via API, with no cooperation agreement, split or commission. The financial data processed in that payment (such as account and payer data) are controlled by that institution, according to its policy. RD does not store card data.

3. What data we collect, for what purpose and on what legal basis

  • Name, email, phone number and password. From whom: Organizer. Purpose: creating and maintaining the account, support and communications about the account. Legal basis: performance of a contract (art. 7, V).
  • CPF or CNPJ, provided voluntarily. From whom: Organizer. Purpose: marking as “Verified User” and fraud prevention. Legal basis: consent (art. 7, I).
  • Name, email, phone number and age verification data. From whom: Contributor. Purpose: recording the reservation, verifying legal age and enabling contact by the Organizer. Legal basis: legal obligation (art. 7, II) and performance of a contract.
  • Data from the second step of age verification. From whom: Contributor. Purpose: confirming legal age (second step of the double verification). Legal basis: legal obligation (art. 7, II).
  • Selfie or facial biometrics, only if adopted. From whom: Organizer. Purpose: liveness check during verification. Legal basis: specific and highlighted consent (art. 11, I).
  • Publication fee payment and invoice data. From whom: Organizer. Purpose: billing, refunds and tax obligations. Legal basis: performance of a contract and legal obligation.
  • IP address, date and time of access, device and browser. From whom: everyone. Purpose: platform security and fraud prevention. Legal basis: legal obligation (art. 7, II).
  • Usage data and preferences. From whom: everyone. Purpose: improving and personalizing the Services. Legal basis: legitimate interest (art. 7, IX).
  • Analytics and advertising cookies and identifiers from Google and Meta, pages visited, IP address and browser data. From whom: everyone who accesses the Site and the dashboard, including through the Android app. Purpose: generating usage statistics and measuring the results of RD’s own ads (Section 8, paragraph b). Legal basis: legitimate interest (art. 7, IX).
  • Registration (identifier) and publication fee payment (identifier, amount and currency), ad click identifier, IP address and browser data, email and phone number converted into a code (SHA-256 hash). From whom: Organizer. Purpose: informing Google and Meta of the registrations and the fees paid, to measure the results of RD’s own ads (Section 5, paragraph g). Legal basis: legitimate interest (art. 7, IX).
  • App instance ID, Android advertising ID, masked IP address (approximate location), sessions and screens accessed, other automatic usage events and the events of app opening, registration and publication fee payment. From whom: those who use the Android app. Purpose: generating app usage statistics and measuring the results of RD’s own ads on Google Ads (Section 8, paragraph b). Legal basis: legitimate interest (art. 7, IX).
  • Email for RD news and offers. From whom: Organizer. Purpose: RD’s own marketing communications. Legal basis: consent (art. 7, I), revocable at any time.
  • Records of reports, complaints and official letters. From whom: everyone. Purpose: moderation, defense in proceedings and responding to authorities. Legal basis: regular exercise of rights (art. 7, VI) and legal obligation.

You may refuse to provide data, but this may prevent registration, the publication of Campaigns or the reservation, when the data are required by law or necessary for the service. RD may anonymize data for statistics, which cease to identify you. RD does not sell personal data.

4. Children, adolescents and age verification

a. Persons under 18 years of age may not use RD, either as Organizers or as Contributors. Campaigns with a draw are prohibited for children and adolescents by Law No. 15,211/2025 (Digital Statute of Children and Adolescents – ECA Digital).

b. For this reason, RD does not accept self-declaration of age alone. Legal age is verified in two layers: (i) the user’s declaration that they are 18 years of age or older; and (ii) a second confirmation step, through an independent technical mechanism, disclosed at the time of registration or reservation. The declarations of legal age and of the truthfulness of the information, as well as the voluntary option to provide a CPF or CNPJ to become a Verified User, are made in dedicated checkboxes, with the date and time recorded.

c. The data used in the verification serve only that purpose and the prevention of fraud. They are not used for marketing or shared beyond what is necessary.

d. If RD identifies that a child or adolescent has provided data, it will block the reservation or the account and delete the data, except for what must be kept under a legal obligation.

5. With whom we share data

RD shares personal data only in the situations below, and only to the extent necessary:

a. With the Organizer of the Campaign in which you made the reservation, so that the Organizer can contact you, deliver Items and communicate the result. The Organizer may not use these data for other purposes, such as marketing, without your consent.

b. With Payment Institutions, through the technical integration via API, to process Pix or another chosen method and confirm the payment.

c. With RD’s service providers, such as hosting, email delivery, invoice issuance, customer service and identity verification, which act on RD’s behalf and may only use the data for the contracted service.

d. With public authorities, upon a court order or a request from an authority with legal competence, and to comply with a legal obligation, respecting the limits of the Brazilian Civil Rights Framework for the Internet (Marco Civil da Internet).

e. To protect rights, in judicial, administrative or arbitral proceedings, and to prevent fraud and ensure the security of Users.

f. In corporate transactions, such as a merger or sale of the company, in which case the new responsible party will be bound by this Policy.

g. With Google and Meta, to measure the results of RD’s own ads. When an Organizer registers or pays the publication fee, RD reports the registration or the payment to Google (Google Ads, Google Analytics and Firebase) and to Meta (Facebook and Instagram), through the browser, the Android app and RD’s servers. Through the servers, RD sends: to Google Ads, the fee paid (fee identifier, amount and currency, ad click identifier, if any, and your email and phone number converted into a code, via SHA-256 hash, before sending); to Meta, the registration and the fee paid, with the same email and phone number code, the IP address, the browser data and the Meta cookie identifiers used during registration or fee generation; and to Google Analytics, the registration and the fee paid, without email or phone number. The code does not show the email or the phone number, but Google and Meta can compare it with the data in their accounts to find out whether the person saw or clicked on an RD ad. RD uses these transmissions only to measure and improve its own ads. Google and Meta also process these data in accordance with their privacy policies.

h. International transfer. Google, Meta and other RD providers may process personal data outside Brazil. RD only makes this transfer in the cases permitted by art. 33 of the LGPD.

RD does not share data for third-party market research or with social networks, except for the transmission to Meta described in paragraph g, to measure the results of RD’s own ads.

6. How long we keep data

  • Campaign data (reservations, quotas, reports). Retention period: 90 days after closure. Reason: availability to the Organizer, in accordance with the Terms of Use.
  • Registration and verification data. Retention period: while the account is active and, afterwards, for a period of 90 days. Reason: performance of the contract and regular exercise of rights.
  • Ad measurement and usage statistics data (sign-up source, records of transmissions to Google and Meta, Google Analytics and Android app events). Retention period: up to 14 (fourteen) months after collection (in Google Analytics, counted from the last activity). Reason: measuring the results of RD’s ads and generating usage statistics.
  • Data subject to a request from an authority or a court order. Retention period: for the period requested. Reason: legal obligation.

When these periods end, the data are deleted or anonymized. Backup copies may remain for a limited period, until they are overwritten, protected by the same security measures. Deletion follows the periods above, except for compliance with a legal obligation or an order from a competent authority.

7. Your rights and how to exercise them

Under art. 18 of the LGPD, you may, at any time:

  • confirm whether RD processes your data and access them;
  • correct incomplete, inaccurate or outdated data;
  • request the anonymization, blocking or deletion of unnecessary data or data processed in non-compliance with the law;
  • request data portability;
  • find out with whom your data have been shared;
  • revoke consent, when it is the basis for the processing (for example, offer emails), and be informed about the consequences of not consenting;
  • object to processing carried out on the basis of legitimate interest.

How to request: through the account settings or the DPO’s email address given in Section 1. RD may confirm your identity before fulfilling the request, to protect your data, and will respond within 15 (fifteen) days. Requests about data processed by the Organizer of a Campaign must be addressed to the Organizer; RD will assist with forwarding them.

8. Security, cookies, changes and contact

a. Security. The security, integrity and confidentiality of your information are extremely important to us. RD adopts technical and administrative measures to protect data against unauthorized access, disclosure, use and alteration, and reviews these procedures periodically. No measure is infallible; in the event of a security incident that may result in relevant risk or damage, RD will notify the affected data subjects and the ANPD, in accordance with the law.

b. Cookies and measurement technologies. RD uses cookies necessary for the operation of the Site (login, security) and analytics and advertising cookies from Google (Google Analytics and Google Ads) and Meta on the pages of the Site and the dashboard, including when opened through the Android app, to generate usage statistics and measure the results of RD’s own ads (Section 5, paragraph g). You can block or delete these cookies in your browser settings; in the Android app, they are deleted when you clear the app’s data or uninstall it. Blocking cookies does not prevent the transmission by RD’s servers to Google Ads and Meta described in Section 5, paragraph g. To exercise your rights over these data, write to the DPO (Section 1); RD will assess the request and respond within 15 (fifteen) days. Organizers who install their own pixels on the pages of their Campaigns are responsible for that processing.

In the Android app, RD uses the Google Analytics for Firebase development kit (SDK), from Google. It collects the app instance ID, the Android advertising ID, the IP address in masked form (to estimate the approximate location), the sessions and screens accessed, other automatic usage events and the events of app opening, registration (with the method used: email, Google or Apple) and publication fee payment (amount, currency and fee identifier), to generate app usage statistics and measure the results of RD’s own ads on Google Ads. You can reset or delete the advertising ID at any time in the device settings, under the ads option; the path and options vary according to the manufacturer and the Android version. Deleting the advertising ID prevents its use for ads, but does not turn off the app usage statistics; to exercise your rights over these data, write to the DPO (Section 1). The iPhone (iOS) app does not use this SDK, does not load the Google and Meta advertising tags and does not send the registrations and payments made in it to Google Ads or Meta.

c. Changes. This Policy may be updated. Relevant changes will be communicated by email or by a notice in the Services and, when required by law, new consent will be requested. The date of the last update appears at the beginning of the document.

d. Contact. Questions about this Policy may be sent to the DPO through the channel already made available (Section 1) or through Support.