Crewai Avis 2

I discovered that crewAI is collecting my data without consent. Disturbingly, I found this collection function cannot be disabled despite my numerous attempts.

It's disappointing to see companies betray the open-source community this way. In my experience, this is the most flagrant violation of open-source principles and personal data laws I've encountered. I'm shocked that companies using this haven't sued crewAI for millions yet. How can such violations go unpunished when they typically result in massive fines?

P.S. The product shows interesting potential, despite experiencing numerous technical failures and freezes. These issues clearly stem from an inappropriate tech stack, team inexperience, and bugs typical of an unpolished product.

After examining crewAI, I've identified serious privacy concerns that potential users should be aware of. The library appears to collect usage data without obtaining proper user consent, which raises significant ethical and legal questions.

The most troubling aspect is that information about data collection is poorly disclosed, appearing only as a minor note buried deep within the documentation. This lack of transparency is problematic for several reasons:

Many jurisdictions, including the EU (GDPR), California (CCPA), and various other regions, require explicit informed consent before collecting user data.

As an open-source library, users reasonably expect transparency about all functionality, especially data collection mechanisms.

The covert nature of the data collection effectively turns the library into a monitoring tool without users' knowledge or consent.

Legal and Ethical Implications
This practice potentially violates privacy regulations in multiple jurisdictions. Software that collects data without clear disclosure and consent mechanisms may face:

Regulatory penalties
Loss of user trust
Potential legal challenges
Reputational damage within the developer community
Recommendation
Organizations considering crewAI should carefully evaluate these privacy practices against their compliance requirements. Developers looking for alternatives might consider frameworks with more transparent data policies or disable any telemetry functions if possible.

The open-source community thrives on trust and transparency. Practices that undermine these principles should be addressed promptly by the development team through better disclosure and implementing proper consent mechanisms.