See your sprint's velocity, forecast, and flow — inside Azure DevOps

Open Azure DevOps. Click "Agile Analytics" in any project's sidebar. See your last 6 sprints' velocity, cycle time, and a Monte Carlo delivery forecast on one screen — in under 60 seconds, with no PAT, no setup, no data export.

What you'll see in your first minute. After install, Agile Analytics adds a sidebar entry to every project in your organisation. Click it once. The hub reads your existing sprint history through your ADO session and renders the Dashboard view above — velocity, burndown, WIP, and delivery grade — for the active sprint. No configuration screen first. If you've never set up a workflow mapping, the hub auto-discovers your column states; you can adjust later.

★★★★★ "The graphs and charts are easy to read and understand and can be shown to any company member without having to give any further explanation. I would recommend for any team size."

"Even for a small team (we have 5 devs and a Scrum Master) this gives us quick and easy access to progress and planning. There is a great support team who actively engage with us and respond very quickly to our feedback, suggestions and ideas." — Mark Pickering, Azure DevOps Marketplace review

Your work-item data never leaves your Azure DevOps tenant

Every analytics view runs in your browser, against the Azure DevOps REST API, using your existing ADO session. Sprint contents, work-item titles, PRs, code, comments, attachments, customer PII — none of it is sent to a Baytek server.

This is structurally different from SaaS analytics platforms (Jellyfish, LinearB, Plandek, Allstacks, Athenian) that require you to grant a PAT or OAuth scope and pipe your ADO data into their warehouse. Agile Analytics installs as an Azure DevOps Marketplace extension — it lives in your tenant, your admin controls it, and your security team can audit it through the Marketplace publisher record.

What Baytek does receive: an org ID, the extension version, and operational event names (e.g. "sprint view opened", "error observed") — no titles, no content, no PII. Used to fix bugs and bill seats. Full detail in our Privacy Policy.

Four read-only ADO scopes. vso.project, vso.work, vso.graph, vso.build. No vso.code. No vso.analytics. No write scopes. The extension cannot modify your work items.

Where to find it after install

Agile Analytics adds a new entry to the left sidebar of every Azure DevOps project in your organisation — directly under the project name, alongside Boards, Repos, Pipelines. If you've just installed and don't see it yet, refresh the project page once. The extension is organisation-wide, so it shows up in every project automatically — you do not need to install it per project.

Most installers never come back to this listing — they go straight to Azure DevOps. If a teammate installed Agile Analytics for your team and you're trying to find it: open any project in your organisation, then look in the left sidebar for Agile Analytics.

At a glance

• What it is. A sprint-intelligence and flow-analytics hub embedded in Azure DevOps Services. 30+ analytics views, delivered as a single project hub extension.
• Built for. Engineering managers, agile coaches, scrum masters, and product owners running 1–50+ Scrum, Kanban, or SAFe teams in Azure DevOps Services. Useful from a single team to enterprise rollouts.
• Pricing. Annual per-seat tiers. Team — $300/year (2 seats) · Business — $1,200/year (6 seats) · Premium — $2,000/year (unlimited seats). Each licence covers one Azure DevOps organisation. Every plan includes every feature. 30-day free trial activates automatically on install — no credit card, extended on request.
• Security & privacy. All analytics run in your browser against the Azure DevOps REST API using your existing ADO session. Your work-item data never leaves your Azure DevOps tenant. Baytek's backend stores only licence records and lightweight install telemetry — never work-item content.
• Compliance. WCAG 2.1 AA accessibility achieved (verified by an axe-core regression suite in CI on every release). SOC 2 Type 1 evidence collection in progress. GDPR-aligned data handling — see Privacy Policy.
• Permissions. Four read-only Azure DevOps scopes: vso.project, vso.work, vso.graph, vso.build. No vso.code, no vso.analytics, no write scopes. The extension cannot modify your work items.
• Quality bar. Every release passes 500+ automated tests (vitest unit + Playwright E2E + 5-view accessibility regression baseline + visual regression baseline) before publication. TypeScript strict mode end-to-end.
• Infrastructure required. None. No Azure Function, no database, no service connection, no PAT. Install, map workflow states once, done.
• Where it runs. Azure DevOps Services (cloud). Azure DevOps Server (on-premises) is not supported in this version.
• Publisher. Baytek. Support and feature requests: ado-analytics.baytekdev.com/support

The Gap It Fills

Azure DevOps has powerful raw data but no built-in answers for the questions that actually matter in sprint planning and retros:

• "When will we be done?" — Monte Carlo simulation on your actual throughput history
• "What should we commit to next sprint?" — Next Sprint Planning combines capacity, Monte Carlo on the team's last 6 sprints, cycle-time per bucket, backlog risk scan, and historical commitment reliability into a single recommendation
• "How much can we realistically commit this sprint?" — Sprint Capacity: velocity-adjusted commitment, factoring in each member's days off
• "Why is this sprint struggling?" — Commitment reliability, scope churn, and carryover rates in one view
• "Which team needs attention?" — Cross-team health grid with configurable goals and auto-generated coaching prompts
• "How long does work actually take?" — Cycle time scatterplot with P50/P85 percentile lines
• "Are we flowing or are we stuck?" — Flow efficiency, lead time, and WIP trends over rolling windows
• "Where does our engineering time actually go?" — Investment Allocation: completed work classified into features vs. bugs vs. maintenance per team, plus an unplanned-work share
• "Are our engineers actually using AI tools?" — Company-wide GitHub Copilot adoption dashboard

Agile Analytics answers all of these — without leaving Azure DevOps.

Who Is This For

Views at a Glance

Sprint Health

Flow Analytics

Delivery & Investment

Portfolio

Agile Coach

AI Governance

Dashboard Widgets

Companion tiles are available in the Azure DevOps widget catalog under the "Agile Analytics" category. The analytics themselves live in the hub — a tile that cannot reach your data says so and points you there.

Tools

How It Compares

This is positioning, not a benchmark — every team's setup is different. The point is that Agile Analytics fills the analytics layer that ADO ships without, with no data-pipeline work and a flat org price.

Pricing & Licensing

30-day free trial — no credit card. Annual plans from $300/year after. The Marketplace install gives you the full extension, fully unlocked with no limitations, for 30 days — and we extend the trial on request if you need longer to evaluate. To keep using it past your trial, an Azure DevOps organisation admin activates a paid plan below. There is no "free forever" tier; we tell you this up front so the end of your trial isn't a surprise.

Three plans, every feature included on each:

• Team — $300/year · 2 seats included. Right for a small Scrum team or a pilot rollout.
• Business — $1,200/year · 6 seats included. Right for a full delivery team running Scrum or Kanban.
• Premium — $2,000/year · unlimited seats. Best for a whole org, multiple teams, or a security-reviewed enterprise rollout.

All plans are billed annually — a 12-month subscription. Each licence covers a single Azure DevOps organisation; if you run more than one organisation, contact us for multi-organisation pricing. You can upgrade to a higher plan at any time — the unused value of your current plan is credited toward the new one, so you only pay the difference.

A seat is an assigned place on your plan. Your extension admin assigns people in Configuration → Access Control; assigned users — admins included — each hold one seat, and seats can be swapped at any time by removing someone and assigning someone else. You can never be billed for more than your plan: when every seat is taken, new assignments are refused until you free one or upgrade, and everyone else still sees the Dashboard with a one-click way to request a seat from your admin. During a trial there are no seats — everyone in your organisation has full access.

30-day free trial activates automatically on install — no credit card required. During the trial every user in your org has full access.

Install from the Azure Marketplace and your trial starts automatically. When you are ready to subscribe, visit https://ado-analytics.baytekdev.com/pricing/. After payment, Baytek emails your licence key and an org admin activates it in Settings → License inside the extension.

Not ready to commit? Schedule a 15-min call — procurement question, security review, missing feature, pricing for an unusual team size. No slides.

Support & Feature Requests: Questions, bugs, rollout help, or missing features? Start here: https://ado-analytics.baytekdev.com/support/

Security, Privacy & Compliance

Where your work-item data lives. Every analytics view runs in your browser against the Azure DevOps REST API, authenticated by your existing ADO session — the same session ADO Boards uses to render your work-item list. Baytek does not see, request, or store your work-item content, sprint data, AI prompts, or any user identifiers from your tenant.

What Baytek's backend handles.

1. Licensing. When an org admin activates a paid licence, the backend issues a signed activation token. Subsequent validation calls confirm the token is still valid. Stored: organisation name, plan tier, expiry date, activation token. No work-item data.
2. Install telemetry. A lightweight ping on first install and on subsequent loads (organisation name, ADO org id, extension version, event type, timestamp) lets us count active orgs and detect outages or regressions. No work-item data.
3. Anonymous usage telemetry (added in v6.4.0, opt-out at Configuration → Privacy). A small allow-listed set of events — view navigation, configuration completion, trial-day milestones, feature use — recorded against the ADO organisation ID. Each event carries an enum-valued name and a small structured properties payload. Never includes work-item content, user names, project / team / sprint names, AI prompt content, or webhook URLs. The exact event allow-list is documented in the Privacy Policy.
4. Optional trial nurture emails. If a trial admin opts in by entering their email in the trial reminder card, Baytek sends a Day 7 onboarding email, a Day 14 mid-trial check-in, and Day 23 / Day 28 trial-end reminders. Opt-in only.
5. Exec Report scheduled digests (added in v6.26.1, only if you schedule one). When you schedule an Exec Report email digest, Baytek's backend relays the email on your chosen schedule. Recipients confirm by email before anything is sent (double opt-in), and every email carries a one-click unsubscribe link. Stored: the subscription record (recipient email address, schedule, confirmation status). Report content is never stored on our servers.

Sub-processors.

• Stripe — payment processing for licence purchases.
• Firebase App Hosting — the ado-analytics.baytekdev.com marketing and licence-management site only. The extension itself does not depend on Firebase.
• Zoho Mail — transactional email (licence keys, support replies).

Sub-processors are listed in the Privacy Policy and the compliance/ working evidence record.

Compliance posture.

• Accessibility. WCAG 2.1 AA achieved as of v6.2.4. Every release runs a 5-baseline axe-core regression suite in CI; new violations fail the gate before publication. The single accepted exception is page-has-heading-one, which is structurally inappropriate for an iframe-embedded extension whose host page (Azure DevOps) owns the page-level h1 — adding our own would create competing top-level headings in the user's accessible heading tree.
• SOC 2 Type 1. Evidence collection in progress. Working documentation maintained internally; ask via support for status updates.
• GDPR. Personal data processed by Baytek is limited to the licence record and install telemetry above. Customers acting as data controllers can request deletion via support.

Settings storage. All extension configuration (workflow mapping, WIP limits, AI provider keys, access control, user preferences) is stored at organisation scope in Microsoft's Azure DevOps Extension Data Service — Microsoft-managed infrastructure that Baytek systems do not access. Configuration survives extension upgrades and is removed by Microsoft on uninstall.

Engineering quality bar. Releases are gated through 500+ automated tests:

• Unit tests (vitest) — exercise every analytics calculation against real-ADO captures and synthetic fixtures across all four Microsoft stock processes (Agile, Scrum, CMMI, Basic) plus arbitrary custom processes.
• End-to-end tests (Playwright) — validate the hub shell, navigation, configuration save persistence, trial flows, accessibility, and visual regression baselines.
• Accessibility regression suite — axe-core runs against five baseline views on every release; new WCAG 2.1 AA violations fail the gate.
• Visual regression baselines — five baseline screenshots gated for unintended UI drift.

A failure in any layer stops the release from being packaged.

What's New in Version 6.40

v6.40.0 — Your sprint burnup reads true, and more of the product speaks your language (August 2026)

Sprint Burnup: the Ideal line now paces your whole sprint. It runs from zero to your full sprint scope across the sprint, which is the standard burnup convention. Before, it paced only the work committed on day one — so if your team took on more work mid-sprint, the Ideal line sat below your Scope line and a team that had delivered everything could still read as behind.

Aging lane labels now work when you have renamed your workflow states. The short labels on the Multi-Team Aging cards were matched against the default state names, so if your team calls its states something else, those labels did not appear. They now follow your states whatever you have called them.

More of the product follows your language. Around ninety further labels are now translated across all six languages: the Retro Snapshot image export (which stayed English even when the card beside it was translated), dashboard widget names in the Customize panel, the item-type scope notes, the feature quarter table, team benchmark columns, and a number of error messages. Two smaller fixes for anyone not working in English: the access-request button now correctly reads "Access requested" after you request access, and the quarter table's first column aligns correctly in every language.

What's New in Version 6.39

v6.39.2 — Finishing touches from the 6.39.1 review (August 2026)

Two small corrections that were prepared alongside 6.39.1 and complete it: the dashboard's "(so far)" throughput label now meets accessibility contrast in both themes, and the Cumulative Flow diagram no longer shows an empty chart in the rare case where Azure DevOps returns work items without their iteration path — those items now count as sprint members instead of silently disappearing.

v6.39.1 — Sprint Burnup: the Scope line follows your actual sprint (August 2026)

If your sprint grew and the team completed more items than it originally committed, the Sprint Burnup could draw the Completed line above the Scope line. That was a drawing error, not a data error: 6.39.0 made the committed figure honestly reflect day one of the sprint, and the Scope line was mistakenly still capped at that number. The Scope line now follows the sprint's actual item count, "remaining" is scope minus done, and the committed figure keeps showing what was planned on day one. Error messages across the dashboards also now appear in all six languages. Thank you to the customer who reported the chart within a day of 6.39.0 going live.

v6.39.0 — Accuracy across every dashboard, and more of your language (August 2026)

This release carries the accuracy work that began in 6.38 through the rest of the product. Cycle-time percentiles no longer round up to the slower item, DORA figures state exactly what they count, and Monte Carlo forecasts run from a fixed as-of date and leave out runs that never finish rather than quietly skewing the result. Flow figures now agree between the summary and the detail, and item age, aging zones, investment allocation, the executive report and team health are each measured on the same basis they display. Membership is resolved as of each point in time, so a person who joined or left mid-sprint is counted only for the days they were actually on the team. Several figures will read differently than before — lower in most cases — because they are now the true ones; nothing about how your teams work has changed.

The extension also speaks more of your language. The seat and setup screens, the sidebar and dashboard chrome, the widget titles and the forecast prompts now appear in Spanish, Portuguese, Italian, German and French alongside English, following the language your Azure DevOps profile is set to. Nothing you have configured changes — only the words do.

What's New in Version 6.38

v6.38.0 — Seats you assign, and numbers you can trust (August 2026)

Team and Business plans now manage access with assigned seats. Your extension admin assigns people in Configuration → Access Control; assigned users — admins included — each hold one seat, and seats can be swapped at any time. When every seat is taken, the next assignment is simply refused until you free one or upgrade — so you can never be billed for more than your plan, and nobody who already holds a seat is ever cut off. Colleagues without a seat still see the Dashboard, every view stays visible in the navigation, and Access Control names your admin so requesting a seat takes one click. Premium plans and trials have nothing to manage: everyone in the organisation is in, now confirmed by the server on every load so a stored setting can never lock a licensed team out.

This release also makes the analytics more honest. Time-in-stage and flow efficiency now stop the clock when an item is completed rather than at the end of the sprint, commitment is measured at the end of every sprint's first day for every team alike, and SLE breach status always agrees with the numbers on screen. Some figures will read lower than before — they are now the true ones.

Why Teams Choose Agile Analytics

No infrastructure — ever Everything runs in the browser against your live ADO data. No Azure Function, no database, no service connection to configure. Install, claim admin access, map your workflow states once, and it works across your entire organization.

Sprint Capacity + Monte Carlo together Plan with capacity-adjusted commitments, then validate with a 10,000-run Monte Carlo forecast. The two views are designed to be used together before every sprint.

WIP alerts that actually reach you Set WIP limits per team, connect a Teams or Slack webhook, and get notified the moment a team goes over — with a direct link to their active sprint taskboard.

Background Monitor — alerts without the browser open Configuration generates the Azure Pipeline YAML for you. Your admin adds it to a repo, sets a cron schedule, and WIP alerts run automatically — even when nobody has ADO open. Zero external infrastructure, runs entirely within your tenant.

Retro-ready in one click Copy any sprint summary in one click, or open the new Exec Report as a print-ready PDF for stakeholders. Paste it into your retro without formatting work.

Role-based access control Built-in Admin/User role system with ADO directory search. Keep it open to all project users, or switch to assigned-users-only mode for controlled rollouts.

Dark mode Full dark theme — persisted per user, toggled with one click.

Getting Started in Under 2 Minutes

Step 1 — Install Open the Marketplace listing and install the extension into your Azure DevOps Services organization.

Step 2 — Open Navigate to any project → find Agile Analytics in the left navigation bar under your project name.

Step 3 — Claim Admin Access (Required) An Azure DevOps Project Administrator or Organization Administrator must go to Tools → Configuration → Access Control and click Claim Admin Access.

Step 4 — Configure Workflow Mapping (Required) Go to Tools → Configuration → Workflow Mapping and map your board states to analytics flow stages. This is what makes cycle time and flow metrics accurate for your process.

Step 5 — Select your team and explore Use the team selector in the top-left corner, then browse views using the top navigation.

Optional Visit Tools → Configuration to set WIP limits, add Teams/Slack webhook alerts, configure the Background Monitor, and run Readiness checks.

Complete Access Control claim and Workflow Mapping before broad rollout for correct analytics behavior.

Access Control

Agile Analytics includes a lightweight built-in role system — no Azure DevOps group configuration required.

1. An Azure DevOps Project Administrator or Organization Administrator visits Configuration → Access Control and clicks Claim Admin Access
2. Admin chooses whether the extension is open to All project users or restricted to Assigned users only
3. Admin adds users by searching the ADO directory and assigning them Admin or User roles
4. Admin configures which views are visible to User-role members
5. Admins always see every view regardless of settings

Settings are stored at organization scope in Azure DevOps Extension Data Service — one configuration shared across all users in the org.

Notification Alerts

Connect to Microsoft Teams or Slack to receive automatic alerts. Seven configurable triggers:

Sprint Health

• Commitment Reliability Low — fires when reliability drops below your threshold
• Scope Churn Exceeded — fires when mid-sprint scope changes exceed your churn threshold
• Carryover Risk — fires when carry-over share is too high
• Sprint End Summary — one-time digest at sprint end

Flow & WIP

• WIP Over Limit — fires when any team exceeds its WIP limit; links directly to their active sprint taskboard
• Stale In-Progress Items — fires when items have been in-progress for more than 5 days

Digest

• Weekly Sprint Digest — once-per-week summary of sprint health and flow status

Configure in Tools → Configuration → Notifications. Paste your webhook URL, select triggers, and save.

In-session vs Background: Alerts above fire when a user has the extension open. For automated alerts without the browser open, use the Background Monitor.

Background Monitor — Alerts Without the Browser Open

Configuration → WIP Settings generates a YAML file for your Azure Pipeline. After your admin adds that file to a repo and creates the pipeline, it runs on your chosen cron schedule, checks WIP limits, and posts to Teams or Slack automatically.

• Zero external infrastructure — runs entirely within your ADO organization
• No PAT required — uses Azure Pipeline's built-in service account
• Fully auditable — YAML file is committed to your repo; inspect or modify anytime

Permissions Explained

We request only what we use. No vso.code, no vso.analytics, no write permissions.

Requirements

• Azure DevOps Services (cloud) — any tier
• Project Contributor access or higher
• Modern browser (Edge, Chrome, Firefox)
• Azure DevOps Server (on-premises) — not supported in this version

FAQ

Does this extension store my data anywhere? Your Azure DevOps work item content, sprint data, and AI prompts stay in your browser and your ADO tenant — Baytek never sees them. The only data on Baytek systems is your licence record (organisation name, plan, expiry, activation token) and a lightweight install/heartbeat ping (organisation name, extension version, timestamp) so we can count active installs and detect outages. Settings, workflow mappings, AI API keys, and access control are stored in your org's Azure DevOps Extension Data Service — Microsoft-managed infrastructure that Baytek does not access. Full details in the Privacy Policy.

Will my settings be lost when the extension updates? No. All settings (WIP limits, workflow mappings, notification webhooks, AI configuration, access control, user preferences) are stored using the ADO Extension Data Service key-value API, which is version-agnostic. Upgrading never resets your configuration.

Does it slow down Azure DevOps? No. The extension makes the same REST API calls you would make manually — one view at a time, only when you navigate to it. No background polling, no persistent connections.

Why do I see no data on Cycle Time, Flow Metrics, or Flow Efficiency? These views require completed sprints with items in a Done/Closed/Resolved state. As of v6.1.0 your project's custom state names are auto-discovered — open Configuration → Workflow Mapping and assign each of your states to a stage (In Progress / Test / Review / Done). The Cycle Time preview panel under each mapping shows exactly which states will count.

How does Sprint Capacity work? Sprint Capacity reads the capacity your team sets in Azure DevOps Boards (the days/hours per member per sprint). It calculates each member's available working days after personal and team-wide days off, computes effective team capacity as a percentage, and multiplies your average velocity by that percentage to suggest a realistic sprint commitment. If capacity hasn't been set in ADO Boards, the view will prompt you to add it there first.

Do I need to configure anything before rollout? Yes. An admin should claim admin access (Configuration → Access Control) and complete workflow mapping (Configuration → Workflow Mapping) before rolling out to the team.

Can I control who sees what? Yes — through the built-in Access Control. Admins can choose open access for all project users or restrict to assigned users only, and control which views regular users can see.

Does it work across multiple projects? Yes. The extension installs at organization level and is available in every project. The current plan includes unlimited teams and projects across your organization.

Is dark mode supported? Yes. Click the theme toggle in the top-right of the navigation bar. Preference is saved per user.

What happens if I uninstall? Your ADO work items, sprints, and boards are completely unaffected — this extension only reads data, never writes to work items. Extension Data (settings, preferences, access control) is deleted on uninstall.

What is AI Metrics and who can use it? AI Metrics is a company-wide AI adoption dashboard. It is included in the 30-day trial and every paid subscription. When no live AI source is connected, it shows realistic demo data so you can explore the layout. To connect a live source, go to AI Metrics → Settings (admin required) and enter credentials for GitHub Copilot or a Custom API endpoint.

What is AIIP? AIIP (AI Improvement & Intervention Panel) is an admin-only companion to AI Metrics. It surfaces automated alerts when users are at risk of disengagement (low usage, high rejection rate, sudden drop), lets admins log interventions and mark them done, celebrates milestones, and can send Teams webhook notifications per team. All actions are written to an audit log.

What are the dashboard widgets? Companion tiles in the Azure DevOps widget catalog, under the "Agile Analytics" category. The full analytics — team selection, history, and configuration — live in the Agile Analytics hub; a tile that cannot reach your data says so and points you to the hub.

Frequently Asked Questions

Does Agile Analytics need a Personal Access Token (PAT)? No. It runs in your browser using your existing Azure DevOps session and four read-only scopes. There is no PAT to create, rotate, store, or leak — and no service connection to configure.

Does my work-item data leave Azure DevOps? No. Every analytics view is computed in your browser against the Azure DevOps REST API. Sprint contents, work-item titles, code, comments, and PII are never sent to a Baytek server. This is the key difference from SaaS engineering-metrics platforms that pipe your data into their own warehouse.

How is this different from the built-in Azure DevOps dashboards and Analytics views? Azure DevOps gives you raw widgets and OData feeds — you still have to build velocity, cycle-time, flow, and forecasting reports yourself. Agile Analytics ships 30+ ready-made views — Monte Carlo forecasting, cycle-time percentiles, flow efficiency, DORA metrics, investment allocation, and sprint-capacity planning — with zero query-building.

Do I need to configure anything before I see data? No. On first open the hub auto-discovers your workflow states and renders your active sprint immediately. You can fine-tune the state-to-stage mapping later under Configuration → Workflow Mapping; a live preview shows exactly which states will count.

Which processes does it support — Scrum, Kanban, SAFe, or a custom process? All of them. It reads your team's own workflow states, so custom Azure Boards processes and renamed columns work out of the box.

Can it forecast when we'll finish? Yes. The Monte Carlo view runs thousands of simulations on your real throughput history to answer "how many will we finish?" and "when will this be done?" with P50/P85 confidence bands — no story-point estimation required.

Does it work with Azure DevOps Server (on-premises)? Not in this version — Agile Analytics supports Azure DevOps Services (cloud) only.

Is there a free trial, and how does pricing work? Yes — a 30-day free trial starts automatically on install, no credit card, and we extend it on request if you need longer to evaluate. After that it is an annual per-seat plan: Team ($300/year, 2 seats), Business ($1,200/year, 6 seats), or Premium ($2,000/year, unlimited seats) — each a 12-month subscription covering one Azure DevOps organisation. Every plan includes every feature. A seat is an assigned place your admin manages in Configuration → Access Control.

Data & Privacy

What stays in your tenant: Azure DevOps work item content, sprint data, and any AI adoption credentials you enter. Baytek never sees any of this.

What Baytek's backend receives: licence records (organisation name, plan, expiry, activation tokens), a lightweight install/heartbeat ping (organisation name, extension version, event type, timestamp), and anonymous usage events (view navigation, configuration completion, trial-day milestones — opt out at Configuration → Privacy). Plus an optional admin email if a trial admin chooses to opt in to milestone reminders.

Optional integrations: when you connect an AI adoption source or webhook notifications, requests go from your browser directly to that source (api.github.com for GitHub Copilot, or your own Custom API endpoint) or webhook URL (Microsoft Teams / Slack) — never via Baytek.

Privacy Policy  |  Terms of Service  |  Support & Feature Requests  |  Getting Started Guide