Security & Data
QA Inspector connects information from the systems where development work already happens. That makes how it handles that information important.
The product is designed around a simple principle: keep information when persistence provides a necessary, lasting function—not simply because QA Inspector encountered it.
Current tickets, documentation, conversations, and analysis context are generally retrieved for the work being viewed rather than permanently collected as a second copy of the project.
Settings, workspace preferences, layouts, and work intentionally created or edited by the user may persist so QA Inspector can preserve the experience and work the user expects to keep.
QA Inspector may identify findings and available next steps, but meaningful actions and supported cross-system delivery remain user initiated.
How Information Is Handled
QA Inspector can work with information such as Jira tickets, connected Jira work, Confluence documentation, Slack context, files, images, and other supported sources when those sources are relevant to the work being inspected.
As users move between work, QA Inspector generally replaces or retrieves the context needed for the new work instead of maintaining a permanent archive of every ticket, page, or conversation it has encountered.
Product settings, layout and workspace preferences, access-related information, and content intentionally created or edited by a user may be retained when persistence is necessary for the feature to work.
QA Inspector is designed to work with the systems that already contain project information rather than requiring teams to recreate all of that information inside another project-management repository.
Historical Analytics
Understanding whether development conditions are improving requires information across time. Historical Analytics & Impact functionality is being designed to preserve limited information needed for that purpose.
Historical measurements can support trends, changes in work conditions, time-savings analysis, and other measurements that cannot be produced from a single moment in time.
The goal is purposeful retention for measurable product functionality—not retaining full copies of project information simply because QA Inspector processed it.
User Control
QA Inspector can analyze information, surface discrepancies, identify risks, and present supported resolution opportunities without treating those findings as permission to change the underlying work.
Transparency Matters
QA Inspector will continue to evolve as additional integrations, analytics, and capabilities are introduced. Data-handling practices and public documentation will evolve with the product so users can understand what information a feature needs and why it needs it.
For the formal description of Kluso Labs data practices, review the Privacy Policy.