Privacy Policy
Version 3 · in force since October 12, 2026
This policy explains which personal data FlyeeClub processes, why, and what your rights are. It follows the Brazilian General Data Protection Law (LGPD, Law 13,709/2018).
1. Who the controller is
The controller is the legal entity that operates FlyeeClub, named in the site footer and on the tax document of each purchase. Privacy requests are received through the channels on the contact page.
2. What data we process
- Account: name, e-mail and password (stored encrypted). If you sign in with Google or GitHub, we receive your name, e-mail and profile picture.
- Profile: the segment you declare, the AI assistant you use, your language and time zone.
- Billing: for purchases in Brazilian reais, tax ID (CPF or CNPJ), postal code, address number and phone. Card details stay with the payment processor and never reach our servers.
- Devices: for each machine connected through the flyee CLI, the name you gave it, the operating system, the AI assistant, the CLI and harness versions, and the list of installed tools with their versions.
- Usage: events such as "tool installed", "tool executed" or "update done", with the tool name and version. We do not collect the content of what you do: no code, no prompts, no files, no AI responses.
- Access: date, IP address and browser of each sign-in, for your security.
- Origin: the page and campaign through which you arrived (link parameters).
- Waitlist and news: e-mail and, if provided, name, segment and language of people who sign up without an account.
3. Why we use it and on what legal basis
- Performing the contract: creating and keeping your account, delivering the tools and their updates, processing payments and providing support.
- Legal obligation: issuing and keeping tax documents.
- Legitimate interest: protecting the account and the service against fraud and abuse, and measuring in aggregate how the club is used (by segment, assistant and language) to decide what to build. You may object to this use through the contact channels.
- Consent: sending news by e-mail to those who asked for it, and using analytics and advertising cookies on the site and in the dashboard. Consent can be withdrawn at any time.
4. Who we share it with
Only with providers required for the service to work, under contract and with limited access: Supabase (database, authentication and files), Vercel (hosting), Asaas and Stripe (payments and tax documents), Resend (e-mail delivery), Inngest (scheduled jobs), Google (YouTube, where the lessons are hosted, and Google Analytics) and Meta (ad measurement).
For internal analysis, the operator may query aggregate platform data with the help of an AI provider (Anthropic or Google), without that data being used to train models, under those providers' terms.
We do not sell personal data.
5. International transfers
Some of these providers process data outside Brazil, mainly in the United States. In those cases we adopt the contractual safeguards required by the LGPD.
6. How long we keep it
- Account, profile and device data: while the account exists.
- Usage events: 13 months in detailed form. After that, only totals with no identification.
- Tax documents and payment records: for the period the law requires.
- A waitlist sign-up that was never confirmed: 7 days. After an unsubscribe request: 6 months, to make sure the request is respected.
7. Your rights
You may ask for confirmation of processing, access, correction, portability, anonymization, deletion, information about sharing and withdrawal of consent, and you may complain to the Brazilian data protection authority (ANPD). Deleting the account also erases its history, except for what the law requires us to keep.
8. Security
Each account is isolated in the database, traffic is encrypted, staff access is limited and logged, and an account can use two-step verification. We store only the cryptographic digest of tokens, never the token.
9. Support access
To solve a problem you reported, the team may access your account for a limited time. That access requires a reason, is recorded in your sign-in history as support access, and cannot change credentials, accept terms or act on your behalf.
10. Cookies
The use of cookies is described in the Cookie Policy.
11. Changes
Each version of this policy is numbered and dated. A material change is announced by e-mail or in the dashboard before it takes effect.