When an enterprise team evaluates a new Azure DevOps extension, the security and procurement review often requires a detailed explanation of what data the extension accesses, where it is stored, and whether anything leaves the tenant. The new Data & Privacy view in Agile Analytics provides that information inside the product itself — no separate document required.
Five Trust Badges
The view leads with five trust badges that summarise the extension's data posture:
- No external data transmission — no data is sent to Baytek servers or any third-party backend
- No backend server — there is no publisher-hosted analytics infrastructure
- Read-only ADO access — the extension never writes to your work items or project data
- Settings stored in ADO only — extension configuration is stored in your ADO organisation's extension data storage
- No third-party analytics — no tracking, telemetry, or analytics SDKs embedded in the extension
ADO Permissions
The extension requests three OAuth scopes, all read-only:
- vso.work — read work items, queries, boards, and iteration paths
- vso.project — read project and team metadata
- vso.graph — read user and group membership for Access Control
Data Inventory
The Data & Privacy view lists every category of data the extension reads:
- Work items: title, type, state, area path, iteration path, story points, created and resolved dates
- State history: every state transition event for each work item
- Sprints and iterations: dates, names, and team assignments
- Teams and projects: names, member lists (for Access Control)
How to Use This in a Procurement Review
Instead of preparing a separate trust document or data processing agreement summary, point procurement reviewers directly to the Data & Privacy tab in the extension. The view is accessible to all users without Admin access. For organisations with formal DPA requirements, combine this tab with the security page on this website for a complete evaluation package.