Feature Request: Granular control over content collection by feature module

[Lunara-afk]

Kiro Product

IDE

Feature Description

Currently, the "Content Collection for Service Improvement" setting is an all-or-nothing toggle. I'd like to have granular control over which feature modules' data can be collected for service improvement.

I'm comfortable sharing data from certain features (like Steering and Spec generation) to help improve them, but I'd prefer not to share data from other features (like code generation, tab completion, or chat conversations).

Proposed solution:

Provide individual toggles under the "Content Collection for Service Improvement" section for each feature module:

• Steering
• Spec generation
• Code generation
• Tab completion
• Chat / Agentic conversations
• Hooks
• MCP
• Tools

This would give users more confidence and control over what they share, and likely increase opt-in rates overall.

Use Case

As a developer working on proprietary projects, I want to contribute data from features like Steering and Spec generation to help improve Kiro, but I don't want my code snippets, chat conversations, or tab completion data to be collected. Currently I have to choose between sharing everything or nothing, so I end up opting out entirely. With per-feature toggles, I could opt in to the parts I'm comfortable with.

Additional Context

Reference: https://kiro.dev/docs/cli/privacy-and-security/data-protection/

The current settings only provide two toggles:

1. "Usage Analytics And Performance Metrics" (telemetry)
2. "Content Collection for Service Improvement" (all content)

There is no way to selectively share content by feature module (Steering, Specs, Code Generation, Tab Completion, Chat, Hooks, MCP, Tools).

[github-actions]

Thanks for opening this issue and for such a well-thought-out proposal! The idea of providing granular, per-feature toggles for content collection is a great suggestion that could help users feel more confident about opting in on their own terms. A maintainer will review this shortly — we really appreciate you taking the time to share this detailed use case and helping us make Kiro's privacy controls better for everyone! 🙌