From dd5d6b9ad1863d8a04fa35c878d66e2c6e8e6e8c Mon Sep 17 00:00:00 2001 From: rcourtman Date: Sat, 27 Jun 2026 09:47:39 +0100 Subject: [PATCH] Use product language for Patrol control telemetry disclosure --- docs/PRIVACY.md | 2 +- frontend-modern/public/docs/PRIVACY.md | 2 +- scripts/tests/test_telemetry_adoption_report.py | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/PRIVACY.md b/docs/PRIVACY.md index 90b6a2e13b..f8ce16c28f 100644 --- a/docs/PRIVACY.md +++ b/docs/PRIVACY.md @@ -141,7 +141,7 @@ Every field is listed below with the reason it exists — nothing else leaves yo - Telemetry pings are stored on the Pulse license server only for aggregate install/use analysis. - The license server stores only the same coarse telemetry fields listed above; it does not expand them into exact commercial tiers, exact API-token counts, prompts, chat messages, command text, action output, token values, or resource identifiers. -- Pulse may derive aggregate Pulse Intelligence adoption reports from those same rows, including whether an install reached Patrol issue activity, Patrol resolution, Assistant, direct external-agent, or MCP collaboration, Patrol mode starter use, paid Patrol mode cohorts, governed-action activity, approved or rejected action decisions, approved action success, Patrol-control completed-work proof, recent retention, and observed free-to-paid movement within the source window. Those reports do not add prompts, findings, resource identifiers, tool names, tool inputs, tool outputs, command payloads, action outputs, account links, or exact commercial tiers. +- Pulse may derive aggregate Pulse Intelligence adoption reports from those same rows, including whether an install reached Patrol issue activity, Patrol resolution, Assistant, direct external-agent, or MCP collaboration, Patrol mode starter use, paid Patrol mode cohorts, governed-action activity, approved or rejected action decisions, approved action success, completed Patrol control work, recent retention, and observed free-to-paid movement within the source window. Those reports do not add prompts, findings, resource identifiers, tool names, tool inputs, tool outputs, command payloads, action outputs, account links, or exact commercial tiers. - External-agent/MCP activity is stored only as a coarse adapter-origin flag plus capability-class counters: context, event stream, provisioning, operator state, findings, and action requests. - Telemetry rows older than **90 days** are purged automatically. - The license server uses client IP addresses transiently for abuse/rate limiting, but it does **not** store IP addresses in telemetry rows. diff --git a/frontend-modern/public/docs/PRIVACY.md b/frontend-modern/public/docs/PRIVACY.md index 90b6a2e13b..f8ce16c28f 100644 --- a/frontend-modern/public/docs/PRIVACY.md +++ b/frontend-modern/public/docs/PRIVACY.md @@ -141,7 +141,7 @@ Every field is listed below with the reason it exists — nothing else leaves yo - Telemetry pings are stored on the Pulse license server only for aggregate install/use analysis. - The license server stores only the same coarse telemetry fields listed above; it does not expand them into exact commercial tiers, exact API-token counts, prompts, chat messages, command text, action output, token values, or resource identifiers. -- Pulse may derive aggregate Pulse Intelligence adoption reports from those same rows, including whether an install reached Patrol issue activity, Patrol resolution, Assistant, direct external-agent, or MCP collaboration, Patrol mode starter use, paid Patrol mode cohorts, governed-action activity, approved or rejected action decisions, approved action success, Patrol-control completed-work proof, recent retention, and observed free-to-paid movement within the source window. Those reports do not add prompts, findings, resource identifiers, tool names, tool inputs, tool outputs, command payloads, action outputs, account links, or exact commercial tiers. +- Pulse may derive aggregate Pulse Intelligence adoption reports from those same rows, including whether an install reached Patrol issue activity, Patrol resolution, Assistant, direct external-agent, or MCP collaboration, Patrol mode starter use, paid Patrol mode cohorts, governed-action activity, approved or rejected action decisions, approved action success, completed Patrol control work, recent retention, and observed free-to-paid movement within the source window. Those reports do not add prompts, findings, resource identifiers, tool names, tool inputs, tool outputs, command payloads, action outputs, account links, or exact commercial tiers. - External-agent/MCP activity is stored only as a coarse adapter-origin flag plus capability-class counters: context, event stream, provisioning, operator state, findings, and action requests. - Telemetry rows older than **90 days** are purged automatically. - The license server uses client IP addresses transiently for abuse/rate limiting, but it does **not** store IP addresses in telemetry rows. diff --git a/scripts/tests/test_telemetry_adoption_report.py b/scripts/tests/test_telemetry_adoption_report.py index 1cff38589f..b5bd0123b4 100644 --- a/scripts/tests/test_telemetry_adoption_report.py +++ b/scripts/tests/test_telemetry_adoption_report.py @@ -1532,7 +1532,7 @@ class TelemetryAdoptionReportTest(unittest.TestCase): self.assertIn("Pulse Intelligence Assistant context AI calls 30d", content) self.assertIn("approved action success", content) self.assertIn("rejected action decisions", content) - self.assertIn("Patrol-control completed-work proof", content) + self.assertIn("completed Patrol control work", content) self.assertIn("observed free-to-paid movement", content) self.assertIn( "Pulse Intelligence agent/MCP route in the current 30-day telemetry window",