I would want answers to all of these questions before touching an integration like this.

The underlying library it depends on is open source, but this app isn't. Presumably it's holding the codebase in state.

No website to speak of, just boilerplate text to satisfy Github's marketplace submission process.

Would be an instant no-go for any organization or individual that values their IP. Open Source - maybe.

> Where are you sending the code? Are you keeping some of it?

It does not really matter for FOSS projects. For those fearing licence laundering, don’t worry it will be done anyway for any public code.

then who pays for the capacity it runs on?

Thanks for raising this question. Currently, we're offering a free tier to gather community feedback and improve the service. We use enterprise-grade LLMs to ensure high-quality reviews while maintaining reasonable operational costs. Our focus is on building a valuable tool for developers first, and we'll be transparent about any future pricing changes.

The delay in answering this question makes me be more careful about this

Thanks for raising these important questions about data privacy and security. Let me clarify:

1. Code Processing: All code analysis happens in-memory during the PR review process. We don't permanently store any of your source code.

2. Data Retention: We only store the PR comments we generate, not the underlying code. This helps maintain a history of our suggestions while protecting your IP.

3. Privacy Focus: We take data privacy seriously and have successfully worked with both open-source and closed-source projects. We're always open to suggestions on how to further enhance our privacy measures.

If you have specific privacy requirements or suggestions, I'd be happy to discuss them.