Meetily

Users retain complete ownership of all input data. Meeting audio, prompts, and files are processed locally on user devices with no transmission to external servers.

Users own all AI-generated outputs including transcripts and summaries. The vendor claims no rights to user-generated content and all outputs remain on user infrastructure.

The vendor explicitly states they do not use customer data to train AI models. All processing is local and no data is collected for model improvement.

Users have complete control over data retention and deletion since all data is stored locally. Users can delete data at any time and set their own retention policies.

No third-party data sharing occurs as all processing is local. The vendor has no access to user data and cannot share what they don't possess.

Users have complete opt-out control. Optional analytics are opt-in only and can be disabled. Since processing is local, users control all data collection decisions.

The tool is designed for GDPR and HIPAA compliance through local processing architecture. While not certified by third parties, the local-first design inherently satisfies most regulatory requirements.

As an open-source tool (MIT license), the entire codebase is auditable. Users can inspect exactly how the AI processes data and can integrate their own models.

Security is user-managed since it's self-hosted. The vendor provides hardening guidance but users control their own security. No breach history mentioned, and local processing eliminates cloud breach risks.

No meaningful difference in data handling between free Community Edition and Pro Edition. Both use the same local processing architecture. Pro adds support and enterprise features but not different privacy terms.

The vendor has no access to user inputs or outputs unless explicitly granted for support purposes. Even then, access is time-limited and handled as confidential information.

No government data requests or litigation mentioned. The local processing architecture makes government data requests impossible as the vendor has no user data to provide.

The vendor collects no PII or SPI from meetings. Optional analytics may include anonymized usage patterns but no personal or sensitive data. All meeting content stays local.