Privacy Policy
Last updated: March 2025 · Publisher: analytics-baytek
Agile Analytics is a Visual Studio Marketplace extension that operates entirely within your Azure DevOps organization. This policy explains what data the extension accesses, how it is stored, and your rights as a user.
1. Data We Access
Work Items, Sprints & Board Data
The extension reads work item fields (title, state, story points, dates, assignee, tags), sprint iteration data, and board column state. This data is used exclusively to render analytics views within the Azure DevOps hub. It is never transmitted to publisher-hosted servers.
Team & Project Metadata
The extension reads project and team metadata (names, IDs, iteration paths, area paths) required to scope analytics to the selected team and sprint.
PR & Git Metadata (User Metrics only)
When the User Metrics view is enabled, the extension reads pull request metadata (PR ID, author, reviewer, completion date, repository). Raw code content is never accessed.
User Directory (Access Control only)
When the Access Control feature is enabled and an administrator searches for users to assign roles, the extension queries the Azure DevOps identity directory. Only display names and UPNs are read. Results are used solely for role assignment and are not stored externally.
Git & Build Metadata (Background Monitor only)
When the Background Monitor feature is set up, the extension creates and manages an Azure Pipeline definition in your organization. It reads pipeline run metadata (status, duration) to display monitor health. No source code is accessed.
2. Data Storage
All configuration data, role assignments, and cached metrics produced by the extension are stored exclusively in the Azure DevOps Extension Data Service — a Microsoft-managed, tenant-scoped storage layer. Data stored here is subject to Microsoft's Azure DevOps data residency and retention policies. The publisher has no ability to access or export this data.
3. Telemetry & Analytics
The extension does not collect any telemetry, usage analytics, crash reports, or diagnostic data. No events, page views, or user identifiers are sent to the publisher or any third-party analytics service.
4. External Data Transfers
Data is transferred outside your Azure DevOps tenant only in two explicit, user-initiated scenarios:
- AI Assistant (opt-in): When you enable the AI Sprint Assistant and configure an external AI provider (Azure OpenAI, Anthropic Claude, or OpenAI), sprint summary data is sent to the provider API endpoint you configure. You control which provider is used and supply your own API key. Data handling is governed by the provider's own privacy policy.
- Webhook Notifications (opt-in): If you configure an outbound webhook URL for Background Monitor alerts, alert payload data (WIP breach details, project name, team name) is sent to the URL you supply.
In all other cases, all processing occurs within your ADO tenant. No data is sent to the publisher.
5. Third-Party Services
The extension does not integrate with any third-party services by default. All optional integrations (AI providers, webhooks) are explicitly configured by you and require your own credentials or endpoint URLs.
6. Data Retention & Deletion
Configuration data stored in the ADO Extension Data Service is retained as long as the extension is installed. If you uninstall the extension from your organization, all extension data stored in the ADO Extension Data Service is deleted in accordance with Microsoft's retention schedule (typically within 30 days of uninstall).
7. Children's Privacy
This extension is designed for professional use in software development organizations. It is not directed at individuals under the age of 16, and we do not knowingly collect any personal data from minors.
8. Changes to This Policy
We may update this Privacy Policy as the extension's features evolve. Material changes will be noted in the extension's Marketplace changelog. Continued use of the extension after changes are posted constitutes acceptance of the updated policy.
9. Contact
If you have questions or concerns about this Privacy Policy, please open an issue at: