1. Who the controller is and how to reach us
- Controller: Falafy, an independent project maintained by Erick Torres. [TO BE FILLED IN BY THE OWNER: full name or company name, CPF/CNPJ (Brazilian taxpayer ID) and mailing address of the controller]
- Data protection officer (DPO, "encarregado"): [TO BE FILLED IN BY THE OWNER: name of the DPO and a dedicated email, for example privacidade@falafy.com.br]. Until that email is published, requests about personal data can be made through the "Suporte Falafy" contact inside the app.
- Authority: if you are not satisfied with our answer, you can file a complaint with the Autoridade Nacional de Proteção de Dados (ANPD, Brazil's National Data Protection Authority).
2. What data we process
Data you provide
- Sign-up: email, username, display name, password and date of birth. The password is stored only as an argon2 hash, never in plain text. Anyone joining a meeting by code can use a quick account, with only a name and date of birth, without an email or password. Your date of birth is used to enforce the minimum age and the protections for users under 18 (section 9); it does not appear on your profile and cannot be changed in the app after sign-up.
- Acceptance of the terms: the version of the Terms of use and of this policy that you accepted, and the date you accepted it.
- Reports: when you report a message or a person, we keep the reason, the details you wrote and a copy of the text of the reported message.
- Profile (optional): photo, bio, pronouns, colors, frame, custom status, profile links, time zone and working hours, if you choose to fill them in.
- Content: text messages, voice messages, attachments (images, videos and files), reactions, polls, events, notes, stories and the servers, channels and roles you create.
- Relationships: friends list, friend requests, blocks and membership in servers and conversations.
- Donations (optional): if you donate, we store the amount, the date and the payer name shown on the Pix. Only the team sees that name; it never appears on your profile or on the Supporters wall, it is included in your data export once the donation is linked to your account, and it is deleted when you delete your account or ask us to. With Pix with automatic confirmation (when enabled), the payment is processed by Stripe or AbacatePay, which receive the payment data under their own policies. Your @, photo and tier only appear on the Supporters wall if you turn that option on.
- Purchases and subscriptions (optional): if you subscribe to a plan (such as Falafy+), boost a server or buy an item from the Falafy Shop, we store the product, the amount, the date, the payment method (card or Pix), the payment status and the transaction code at the payment intermediary. Card payments are made on Stripe's page, which receives the card details and your email: Falafy never receives or stores the card number. The apps distributed through Google Play and the App Store don't sell anything inside the app; what your account already has still applies in them.
- Audio sample (optional): if you tap "Send audio sample" during a call to report a sound problem, the app records a few seconds of your microphone (as it was captured and as it was sent) and sends it to the team for analysis. It only records when you press the button, and the sample is deleted automatically after 7 days.
- Voice study (optional, temporary): while the study is open (the end date shows in the app; the first one runs until 2026-11-06), you can agree to help improve Falafy's voice in Settings > Voice and video or in the invite inside a call. With your consent, during calls the app records short clips (8 seconds) of your voice only while you talk, in two versions (the plain microphone and how it is sent), at most one pair every 10 minutes and 12 a day, with technical measurements (volume, clipping, voice profile, app version, system and microphone type, never the device name). It never records other people or while you are muted, and it is not offered to anyone under 18. We keep when you agreed, declined or turned it off. Clips are deleted automatically after 7 days and the consent ends with the study. You can turn it off anytime on the same screen, and anything already sent is deleted right away. Legal basis: consent (LGPD art. 7, I).
Data generated by use
- Sessions: device name, creation date, last use and expiry of each session, so you can see and end where you are signed in.
- Account security: the two-factor authentication secret (encrypted with AES-256-GCM), backup codes (hash only) and attempt counters.
- Password reset: when you use "Forgot my password", we store only the hash of the link's code, which is valid for 30 minutes and works once.
- IP address: used on the spot, in memory, to limit login attempts and excessive requests (abuse protection). At sign-up we also store a salted hash of the IP, used to prevent fraud in the invite program. In addition, we keep the access logs required by the Marco Civil da Internet (IP, port, date and time of each login, session renewal and app connection) for 6 months; see section 6.
- Presence and activity: your status (online, away, etc.) is kept in memory while you are connected. "Playing X" is only enabled if you turn the option on and is not stored in the database.
- Push notifications: if you allow notifications in the browser or in the desktop app, we store the technical subscription address (endpoint and keys) provided by the browser. In the Android app, we store the device token generated by Google's Firebase Cloud Messaging.
- Security log: security events on your account (sign-in on a new device, password or email change, turning on two-factor authentication), with a summary of the device and the approximate region, without the IP address. You can see this log in Settings, and each event is deleted after 180 days.
- Call diagnostics: during voice calls, the app sends technical measurements of audio quality (packet loss, delay, audio processing performance, microphone events) so the team can understand sound problems. It does not include the audio of the conversation, device names or the IP address, and it is deleted automatically after 7 days.
- Preferences: notification, privacy, appearance and layout settings, including the weekly email summary, which is only sent if you turn it on.
- Signup origin: when you create your account, we store where you came to Falafy from (the link's UTM parameters, the referring site, the first page you visited and the invite, referral or friend code you used, if any), which kind of app the account was created in and, if you answer it, your answer to the optional question "How did you hear about Falafy?". We use this only for internal growth statistics; it is included in your data export and deleted when you delete your account.
- App usage data: to understand where Falafy can improve, we record app usage events, such as opening the app, joining or leaving a call, starting a screen share, completing signup or seeing an error message. These records contain only the event type, technical codes and time ranges, the platform and the app version, linked to your account. They do not include the content of your messages, your e-mail or your IP address. They are accessed only by the Falafy team and deleted automatically after 90 days. You can turn this collection off at any time in Settings > Privacy & safety > "Help improve Falafy with usage data"; when you turn it off, the events already recorded for your account are deleted. For accounts of users under 18, the collection starts off.
Device permissions
The apps only use each device feature when you use the function tied to it, and you can deny or revoke the permission in the system settings:
- Microphone: voice calls and voice messages.
- Camera: video calls and photos you send.
- Photos and files: only the items you choose to send, and to save the images you download to your gallery.
- Screen capture: only when you start a screen share; on Android, the system shows a notice while it is active.
- Notifications, Bluetooth and background running: message alerts, Bluetooth headsets and keeping the call active with the screen off.
What we don't collect
- We don't use third-party analytics tools, ad pixels or trackers on the website or in the app. App usage data (above) stays on Falafy's own servers only.
- We don't sell data and we don't show ads.
- We don't record voice or video calls or screen shares on the server (the only exception is the audio sample you decide to send yourself, above). Clips, when you turn the feature on, stay only on your computer.
- Noise suppression runs on your device; the audio is not sent to an external service.
- We don't ask for your phone number, your phone's contact list, your location or an ID document.
3. What we use it for and on which legal basis
| Purpose | Data | Legal basis (LGPD, art. 7) |
|---|---|---|
| Create and maintain your account and provide the service (messages, voice, servers) | Sign-up, profile, content, relationships, sessions, preferences | Performance of a contract (item V) |
| Protect accounts and the service against abuse, spam and fraud | IP (in memory), hash of the sign-up IP, login and 2FA attempts, account security log, server audit log | Legitimate interest (item IX) |
| Send push notifications | Browser push subscription or device token | Consent (item I), given through the browser or system permission and revocable at any time |
| Process purchases and subscriptions | Purchase data and email (sent to the payment intermediary) | Performance of a contract (item V) and compliance with a legal obligation (item II), for tax records |
| Diagnose audio problems in calls | Call diagnostics; audio sample, when you send one | Legitimate interest (item IX) for diagnostics; consent (item I) for the sample, given by pressing the button |
| Show "Playing X" | Game name and start time | Consent (item I), option off by default |
| Enforce the minimum age and protect children and adolescents | Date of birth | Compliance with a legal obligation (item II; ECA Digital, Law 15.211/2025) and the best interests of children and adolescents (LGPD, art. 14) |
| Keep application access logs | IP, source port, date and time of logins, session renewals and connections | Compliance with a legal obligation (item II; Marco Civil, art. 15) |
| Record your acceptance of the terms and of this policy | Accepted version and date | Performance of a contract (item V) and regular exercise of rights (item VI) |
| Receive and review reports | Report, reported message and accounts involved | Legitimate interest (item IX) and compliance with a legal obligation (item II) |
| Comply with legal obligations and court orders | The data needed in each case | Compliance with a legal or regulatory obligation (item II) and regular exercise of rights (item VI) |
| Growth statistics (where new signups come from) | Signup origin and the optional answer to "How did you hear about Falafy?" | Legitimate interest (item IX); answering is optional and can be skipped |
| Understand how the app is used to improve the product (funnel, retention, errors) | App usage data | Legitimate interest (item IX), with an option to turn it off |
What the Falafy team sees to run the service
To keep the service running and moderate abuse, the Falafy team sees aggregate data and usage metadata: which servers exist, with their name, owner, number of members and channels; who is online, on which kind of app and since when; and who is in which voice channel, with an indication of streaming or camera on. This view never shows the content of messages or private conversations and does not allow joining, listening to or watching calls and streams. Every time the team looks at this data it is logged. Legal basis: legitimate interest (item IX).
4. Who we share it with
We don't sell or rent data. Some third-party services are involved in running the service:
- Hosting: Falafy's server (the API, the PostgreSQL database, uploaded files, the LiveKit voice and video server and the TURN server that helps calls get through restricted networks) runs on a server rented from Hostinger, in Brazil. Backups are kept on servers of our own or rented ones, also in Brazil. When many people are in calls, some voice rooms may go through a second server of our own. Voice, video and streams go through these servers only to reach the other participants and are not recorded.
- Transactional e-mails: service e-mails, such as the password reset link, the e-mail confirmation, the notice that your password was changed and the weekly summary (if you turn it on), are sent by Falafy's own e-mail server (Postal). No third-party service receives your e-mail address for this. We do not send marketing e-mails.
- Payments: Stripe processes card payments and may process Pix; AbacatePay may process Pix. Each of them receives only what is needed for the payment (amount, e-mail and the details you type on its page) and handles that data under its own policy. Falafy receives the payment confirmation, never the card number.
- Push notifications: your browser's push service (for example Google, Mozilla, Apple or Microsoft) or, in the Android app, Google's Firebase Cloud Messaging, receives the notification to deliver it to your device. You can hide notification content per device.
- Bots and third-party apps: server administrators can add bots created by other people. A bot only sees what the permissions given to it on that server allow (for example, the messages in the channels it has access to). When you authorize an app to use your account, the authorization screen shows what it will receive (such as your username, your email or the list of your servers). What the bot or the app does with this data is the responsibility of whoever created it, under its own policy.
- GIFs: GIF searches and images go through a proxy run by Falafy; the provider (KLIPY) sees the search term and Falafy's server, not your IP or your account.
- Link previews: when a message contains a link, Falafy's server fetches the page to build the preview; the visited site sees Falafy's server, not you. You can turn previews off.
- Watch Together (YouTube): the video plays in the YouTube player (youtube-nocookie.com), loaded directly on your device; Google receives your IP and the player's technical data, under its own policy.
- Website fonts: falafy.com.br pages load fonts from Google Fonts, which exposes your IP to Google.
- Other users: what you post in servers and conversations is visible to the people in them, according to the permissions.
- Authorities: upon a court order or a valid legal request.
Some of these services (push, YouTube, Google Fonts, Stripe) may process data outside Brazil. This international transfer takes place to provide the service you requested, under art. 33 of the LGPD.
5. How long we keep it
- Account and profile: for as long as the account exists.
- Account deletion: when you delete your account, we erase your email, profile, photo, friendships, server memberships, sessions, 2FA, push subscriptions, security log, call diagnostics and audio samples, notes, stories, badges, favorites and preferences. By default, the messages you sent in servers and conversations remain so as not to break the history of the other participants, but they appear as from "Removed user". On the deletion screen you can tick "Also delete all the messages I sent" to have them deleted together with the account; the attachments of those messages are removed from the server within 24 hours.
- Purchases and payments: the record of each payment is kept for the period required by tax and accounting obligations and to handle disputes and refunds. If you delete your account, it is no longer linked to it.
- Access logs (Marco Civil): 6 months, even after the account is deleted (the law requires it), and automatically deleted after that.
- Reports: [TO BE FILLED IN BY THE OWNER: retention period for reports, for example as long as needed for moderation and up to 5 years for defense in legal proceedings]
- Messages and attachments: until you delete them, until the server or channel is deleted, or until moderation removes them.
- Stories: 24 hours.
- Sessions: up to 30 days without use or until you end them.
- Data export file: available for download for 24 hours.
- Security log: 180 days.
- Call diagnostics and audio samples: 7 days.
- App usage data: 90 days, then deleted automatically. If you turn the collection off or delete your account, your account's events are deleted right away.
- Server technical logs: errors and warnings only, with no record of each request, kept for as long as needed for troubleshooting.
6. Access logs (Marco Civil da Internet)
Art. 15 of the Marco Civil da Internet (Brazil's Internet Civil Rights Framework, Law 12.965/2014) requires application providers organized as for-profit legal entities to keep access logs (date, time and IP) for 6 months, confidentially and in a secure environment. Falafy already keeps these logs. [TO BE FILLED IN BY THE OWNER: confirm with legal advice whether the project falls under art. 15]
- What we keep: the IP address and source port, the date and time (with time zone, in UTC) and the account and session of each login, session renewal and app connection to the server. We do not log each message or page you open.
- For how long: 6 months. A daily routine automatically deletes older logs. Authorities may require, by court order, that a specific log be kept for longer (art. 15, § 2).
- Security and confidentiality: the IP is encrypted (AES-256-GCM) in the database, does not appear on any screen of the app or in the API, and can only be read on the server by the person responsible, with every lookup logged (Decree 8.771/2016, art. 13).
- When we hand them over: only upon a court order or a request from an authority with legal power to demand this data (arts. 10 and 22 of the Marco Civil).
7. Your rights
Under art. 18 of the LGPD (Lei Geral de Proteção de Dados, Brazil's General Data Protection Law, Law 13.709/2018), you can request: confirmation that we process your data; access; correction; anonymization, blocking or deletion of unnecessary data or data processed in breach of the law; portability; deletion of data processed based on consent; information about who we share it with; information about the possibility of not consenting; and withdrawal of consent. You can also object to processing based on legitimate interest.
- Directly in the app: in Settings you can edit your profile; in Settings > Privacy & safety you can export a copy of your data (a ZIP file with your profile, the messages you sent, friendships, servers, sessions, acceptance of the terms and the reports you made, up to 3 requests per day), end sessions, turn off notifications, link previews and "Playing X", and delete your account (with the option to delete your messages too).
- How to delete your account: in the app (desktop, mobile or the web version), go to Settings > Privacy & safety > Delete account and confirm. If you own servers, transfer or delete them first. Deletion takes effect right away for the data listed in section 5. If you can't sign in to your account, ask for deletion through the DPO contact.
- Other requests: through the DPO contact above or through "Suporte Falafy" in the app. We reply within 15 days.
8. Security
We use transport encryption (HTTPS/TLS) on the website, in the app, in the API and in calls; calls in direct messages and group conversations are end-to-end encrypted when every device in the call supports it; passwords hashed with argon2; optional two-factor authentication; and session control. End-to-end encryption for messages is still in development: today messages are stored on Falafy's server without that kind of encryption. No system is infallible; in the event of a security incident posing a relevant risk, we will notify those affected and the ANPD, as the LGPD requires. More details in Security and privacy.
9. Children and adolescents
Falafy is not directed at children. You must be at least 13 years old to create an account. [TO BE FILLED IN BY THE OWNER: confirm the minimum age with legal advice; if it changes, also adjust MIN_SIGNUP_AGE on the server]
- How we check today: sign-up asks for your date of birth without saying beforehand what the minimum age is; an answer below it ends the sign-up and blocks new attempts from that device and that network for 24 hours; the date cannot be changed in the app afterwards; and anyone can report an account that seems to belong to someone under the minimum age, which is then reviewed by the team. [TO BE FILLED IN BY THE OWNER: the ECA Digital (Brazil's Digital Statute of Children and Adolescents, Law 15.211/2025) requires reliable age verification mechanisms, and self-declaration alone is not enough; describe here the additional mechanism adopted after legal and technical review]
- Protections for users under 18: the account starts with direct messages from friends only, friend requests from friends of friends only, bio, stats, activity and local time visible to friends only, images and videos from non-friends always blurred (including in servers), and the profile hidden from username searches by strangers. Direct messages and friend requests cannot be opened up to everyone. Falafy does not show ads or build advertising profiles of anyone. App usage data collection also starts off.
- Parents and guardians: [TO BE FILLED IN BY THE OWNER: parental supervision mechanism and linking of accounts of users under 16 to a parent or guardian's account, as required by the ECA Digital] Parents or guardians who identify a child's account, or who want to request the deletion of the account of a teenager in their care, can contact the DPO or Suporte Falafy.
10. Cookies and local storage
The website and the app do not use tracking or advertising cookies. We only use what is strictly necessary for the service to work, so we don't ask for consent for it; we just let you know:
- Web version (falafy.com.br/app): a session cookie called
falafy_rt(HttpOnly, Secure, SameSite=Strict, valid for up to 30 days) that keeps you signed in, and the browser's local storage for preferences, drafts and whether you have already seen the storage notice. - Windows, macOS and Linux apps: the session token is stored protected by the operating system, and preferences and drafts in the app's local storage.
- Android and iPhone apps: the session token is kept in the system's secure storage (Android Keystore or iOS Keychain), and preferences and drafts in the app's local storage.
- Visit origin: the site and the web version keep the first page you visited, the referring site and the link's UTM parameters in the browser's local storage, only until you create an account (then it is sent once and removed from the browser) or for up to 90 days. It is not a third-party tracker and is not shared with anyone.
Clearing the app's or the browser's data, or signing out, removes this information.
11. Changes to this policy
When this policy changes in a relevant way, we will let you know in the app before the change takes effect: the app shows the new version and asks you to accept it to continue. The date of the last update is at the top of the page, and the version you accepted is shown in Settings > About.
See also: Privacy policy · Terms of use · Security and privacy