Real-time monitoring dashboard for Proxmox VE, PBS, Docker, Kubernetes, TrueNAS and vSphere. Self-hosted, with alerts for failed backups, full disks, unhealthy containers and offline nodes.
Go aialertsdashboarddockerdocker-monitoringgohomelabinfrastructure-monitoringkubernetesmonitoringmspproxmoxproxmox-backup-serverproxmox-mail-gatewayproxmox-veself-hostedtruenastypescriptvspherewebhooks
Explain where AI provider context is processed
pulse-triage[bot]6e7d584ff43e
diff --git a/docs/AI.md b/docs/AI.mdindex b2ebbcc767..fa3e24b75f 100644--- a/docs/AI.md+++ b/docs/AI.md@@ -28,7 +28,9 @@ Pulse Patrol is a **scheduled and event-triggered governed operator** that:- **Routes governed actions** through approval, entitlement, policy, verification, and audit boundaries- **Preserves operator feedback** as context for future model runs without converting it into Pulse-authored fixes-All while running entirely on your infrastructure with BYOK for complete privacy.+Pulse runs collection and orchestration on your server. **BYOK does not make+model processing local:** a hosted model receives provider-bound context. Read+[AI privacy](#privacy) before enabling Patrol or an investigation.📖 **For a deep technical dive into the Patrol runtime, see [Patrol architecture](PATROL_ARCHITECTURE.md).**@@ -871,7 +873,42 @@ Use this only in trusted environments.## Privacy-Patrol runs on your server and only sends the minimal context needed for analysis to the configured provider (when AI is enabled). Outbound usage telemetry (a rotating pseudonymous install ID, counts, feature flags, and coarse Patrol mode and governed Pulse Intelligence operations adoption flags and counters only; no hostnames, credentials, prompts, chat messages, command text, action output, token values, IP addresses, or resource identifiers in the payload) is enabled by default and can be disabled any time. See [Privacy](PRIVACY.md) for details.+**BYOK is not local-only processing.** It supplies your own provider credentials,+not a guarantee that infrastructure data stays on your server. Model processing+happens at the configured endpoint. With a hosted model, context travels directly+from a self-managed Pulse instance to that provider, not through Pulse+infrastructure.++- **Model context is not anonymous telemetry.** It can include resource names+ and addresses, monitoring state, relationships, operator notes and objectives,+ prior findings and tool results used in the run. Review the chosen provider's+ retention and training policies before enabling scheduled Patrol or an+ investigation; Pulse does not set those policies for you.+- **Redaction has a scope.** Non-local model requests apply secret filtering and+ resource-policy handling: local-only resource details are omitted or+ summarised, and known restricted identifiers are redacted. **Internal and+ Sensitive resources can still be shared with a hosted model.** These safeguards+ do not make every note or tool result anonymous. Keep credentials out of notes+ and prompts; do not treat a sensitivity label as a promise of local processing.+- **Local processing depends on the endpoint.** If context must stay within+ your network, use a trusted local model endpoint and verify that it does not+ forward requests elsewhere. BYOK or an API-compatible endpoint alone does not+ establish that. Local inference does not disable Pulse's other outbound+ connections.+- **Usage telemetry is separate.** Its enabled-by-default heartbeat contains a+ rotating pseudonymous install ID, aggregate counts and coarse flags, not model+ prompts or tool output. Turning off **Outbound usage telemetry** does not stop+ AI provider requests or delete locally retained AI history.+- **External MCP clients have their own data flow.** Review the external+ client's model provider and data-handling settings too: it can pass the Pulse+ tool results it is authorised to read to its own model, independently of+ Pulse's selected provider.++See [AI provider data](PRIVACY.md#ai-provider-data) for outbound handling and+[local history privacy](CONFIGURATION.md#handle-configuration-and-history-privately)+before sharing saved records. Do not attach prompts, run histories or raw tool+output to a public report; use only a relevant, locally reviewed and redacted+excerpt.---diff --git a/docs/PRIVACY.md b/docs/PRIVACY.mdindex d02191fcf9..f0a0329fdc 100644--- a/docs/PRIVACY.md+++ b/docs/PRIVACY.md@@ -491,6 +491,40 @@ The telemetry implementation is in [`internal/telemetry/telemetry.go`](../internPulse can make outbound connections when you enable specific features:-- **AI providers**: when AI features are configured, Pulse sends only the context required for your request to the provider you chose. This can include active Patrol objective briefs and their optional operator context when they apply to a Patrol run. Retained objective text and observer artifacts are encrypted at rest in the local organization data directory; objective text is not included in Pulse usage telemetry. A provider may return a model-authored observer proposal for an uncovered objective; Pulse encrypts that artifact with the retained objective, excludes it from public objective reads and later prompt seeds, and does not include its content in usage telemetry or audit messages. Saving an objective by itself does not call a model. Local providers stay on your network; non-local hosted providers receive provider-bound context directly from your Pulse instance. AI prompts from self-managed installs do not transit Pulse infrastructure. Before non-local model requests leave the instance, governed resource details use the same resource-policy redaction shown in Data Handling: local-only resource details are omitted from detailed prompt sections or replaced with policy-safe summaries, and known restricted resource identifiers are redacted where they appear in provider-bound context. See `docs/AI.md`.+- **AI providers**: when AI features run, Pulse sends provider-bound monitoring+ and investigation context to the configured endpoint. **BYOK is not local-only+ processing.** See [AI provider data](#ai-provider-data) and the+ [AI privacy guide](AI.md#privacy).- **Relay / Pulse Mobile**: when Pulse Mobile connections are on, Pulse connects to the configured relay endpoint so paired Pulse Mobile devices can reach this instance and receive push notifications. Relay does not provide remote access to the web UI. See Settings → Pulse Mobile. Pulse Mobile is being retired on 31 March 2027.- **Update checks**: Pulse can check for new releases/updates (for example via GitHub release metadata) depending on your deployment and configuration.++### AI provider data++A hosted model can receive resource names and addresses, monitoring state,+relationships, notes, findings and tool results used in a run. Non-local hosted+providers receive this context directly from your self-managed Pulse instance;+AI prompts do not transit Pulse infrastructure. BYOK supplies your credentials,+not a local-processing or provider-retention guarantee. Review your provider's+retention and training policies. For local processing, verify that the chosen+endpoint runs within your trusted network and does not forward requests elsewhere.++Before non-local model requests leave the instance, Pulse applies secret+filtering and resource-policy handling. Local-only resource details are omitted+from detailed prompt sections or replaced with policy-safe summaries, and known+restricted resource identifiers are redacted in provider-bound context.+**Internal and Sensitive resources can still be shared with a hosted model.**+These safeguards do not make every free-form note or tool result anonymous.++Context can include active Patrol objective briefs and their optional operator+context when they apply to a run. Retained objective text and observer artifacts+are encrypted at rest in the local organisation data directory; objective text+is not included in Pulse usage telemetry. A provider may return a model-authored+observer proposal for an uncovered objective; Pulse encrypts that artifact with+the retained objective, excludes it from public objective reads and later prompt+seeds, and does not include its content in usage telemetry or audit messages.+Saving an objective by itself does not call a model.++Turning off **Outbound usage telemetry** does not stop AI provider requests or+delete locally retained AI history. Local inference also does not disable the+other outbound connections above. See [AI privacy](AI.md#privacy), including the+separate data flow of external MCP clients, before enabling model-backed work.diff --git a/frontend-modern/public/docs/AI.md b/frontend-modern/public/docs/AI.mdindex b2ebbcc767..fa3e24b75f 100644--- a/frontend-modern/public/docs/AI.md+++ b/frontend-modern/public/docs/AI.md@@ -28,7 +28,9 @@ Pulse Patrol is a **scheduled and event-triggered governed operator** that:- **Routes governed actions** through approval, entitlement, policy, verification, and audit boundaries- **Preserves operator feedback** as context for future model runs without converting it into Pulse-authored fixes-All while running entirely on your infrastructure with BYOK for complete privacy.+Pulse runs collection and orchestration on your server. **BYOK does not make+model processing local:** a hosted model receives provider-bound context. Read+[AI privacy](#privacy) before enabling Patrol or an investigation.📖 **For a deep technical dive into the Patrol runtime, see [Patrol architecture](PATROL_ARCHITECTURE.md).**@@ -871,7 +873,42 @@ Use this only in trusted environments.## Privacy-Patrol runs on your server and only sends the minimal context needed for analysis to the configured provider (when AI is enabled). Outbound usage telemetry (a rotating pseudonymous install ID, counts, feature flags, and coarse Patrol mode and governed Pulse Intelligence operations adoption flags and counters only; no hostnames, credentials, prompts, chat messages, command text, action output, token values, IP addresses, or resource identifiers in the payload) is enabled by default and can be disabled any time. See [Privacy](PRIVACY.md) for details.+**BYOK is not local-only processing.** It supplies your own provider credentials,+not a guarantee that infrastructure data stays on your server. Model processing+happens at the configured endpoint. With a hosted model, context travels directly+from a self-managed Pulse instance to that provider, not through Pulse+infrastructure.++- **Model context is not anonymous telemetry.** It can include resource names+ and addresses, monitoring state, relationships, operator notes and objectives,+ prior findings and tool results used in the run. Review the chosen provider's+ retention and training policies before enabling scheduled Patrol or an+ investigation; Pulse does not set those policies for you.+- **Redaction has a scope.** Non-local model requests apply secret filtering and+ resource-policy handling: local-only resource details are omitted or+ summarised, and known restricted identifiers are redacted. **Internal and+ Sensitive resources can still be shared with a hosted model.** These safeguards+ do not make every note or tool result anonymous. Keep credentials out of notes+ and prompts; do not treat a sensitivity label as a promise of local processing.+- **Local processing depends on the endpoint.** If context must stay within+ your network, use a trusted local model endpoint and verify that it does not+ forward requests elsewhere. BYOK or an API-compatible endpoint alone does not+ establish that. Local inference does not disable Pulse's other outbound+ connections.+- **Usage telemetry is separate.** Its enabled-by-default heartbeat contains a+ rotating pseudonymous install ID, aggregate counts and coarse flags, not model+ prompts or tool output. Turning off **Outbound usage telemetry** does not stop+ AI provider requests or delete locally retained AI history.+- **External MCP clients have their own data flow.** Review the external+ client's model provider and data-handling settings too: it can pass the Pulse+ tool results it is authorised to read to its own model, independently of+ Pulse's selected provider.++See [AI provider data](PRIVACY.md#ai-provider-data) for outbound handling and+[local history privacy](CONFIGURATION.md#handle-configuration-and-history-privately)+before sharing saved records. Do not attach prompts, run histories or raw tool+output to a public report; use only a relevant, locally reviewed and redacted+excerpt.---diff --git a/frontend-modern/public/docs/PRIVACY.md b/frontend-modern/public/docs/PRIVACY.mdindex d02191fcf9..f0a0329fdc 100644--- a/frontend-modern/public/docs/PRIVACY.md+++ b/frontend-modern/public/docs/PRIVACY.md@@ -491,6 +491,40 @@ The telemetry implementation is in [`internal/telemetry/telemetry.go`](../internPulse can make outbound connections when you enable specific features:-- **AI providers**: when AI features are configured, Pulse sends only the context required for your request to the provider you chose. This can include active Patrol objective briefs and their optional operator context when they apply to a Patrol run. Retained objective text and observer artifacts are encrypted at rest in the local organization data directory; objective text is not included in Pulse usage telemetry. A provider may return a model-authored observer proposal for an uncovered objective; Pulse encrypts that artifact with the retained objective, excludes it from public objective reads and later prompt seeds, and does not include its content in usage telemetry or audit messages. Saving an objective by itself does not call a model. Local providers stay on your network; non-local hosted providers receive provider-bound context directly from your Pulse instance. AI prompts from self-managed installs do not transit Pulse infrastructure. Before non-local model requests leave the instance, governed resource details use the same resource-policy redaction shown in Data Handling: local-only resource details are omitted from detailed prompt sections or replaced with policy-safe summaries, and known restricted resource identifiers are redacted where they appear in provider-bound context. See `docs/AI.md`.+- **AI providers**: when AI features run, Pulse sends provider-bound monitoring+ and investigation context to the configured endpoint. **BYOK is not local-only+ processing.** See [AI provider data](#ai-provider-data) and the+ [AI privacy guide](AI.md#privacy).- **Relay / Pulse Mobile**: when Pulse Mobile connections are on, Pulse connects to the configured relay endpoint so paired Pulse Mobile devices can reach this instance and receive push notifications. Relay does not provide remote access to the web UI. See Settings → Pulse Mobile. Pulse Mobile is being retired on 31 March 2027.- **Update checks**: Pulse can check for new releases/updates (for example via GitHub release metadata) depending on your deployment and configuration.++### AI provider data++A hosted model can receive resource names and addresses, monitoring state,+relationships, notes, findings and tool results used in a run. Non-local hosted+providers receive this context directly from your self-managed Pulse instance;+AI prompts do not transit Pulse infrastructure. BYOK supplies your credentials,+not a local-processing or provider-retention guarantee. Review your provider's+retention and training policies. For local processing, verify that the chosen+endpoint runs within your trusted network and does not forward requests elsewhere.++Before non-local model requests leave the instance, Pulse applies secret+filtering and resource-policy handling. Local-only resource details are omitted+from detailed prompt sections or replaced with policy-safe summaries, and known+restricted resource identifiers are redacted in provider-bound context.+**Internal and Sensitive resources can still be shared with a hosted model.**+These safeguards do not make every free-form note or tool result anonymous.++Context can include active Patrol objective briefs and their optional operator+context when they apply to a run. Retained objective text and observer artifacts+are encrypted at rest in the local organisation data directory; objective text+is not included in Pulse usage telemetry. A provider may return a model-authored+observer proposal for an uncovered objective; Pulse encrypts that artifact with+the retained objective, excludes it from public objective reads and later prompt+seeds, and does not include its content in usage telemetry or audit messages.+Saving an objective by itself does not call a model.++Turning off **Outbound usage telemetry** does not stop AI provider requests or+delete locally retained AI history. Local inference also does not disable the+other outbound connections above. See [AI privacy](AI.md#privacy), including the+separate data flow of external MCP clients, before enabling model-backed work.diff --git a/frontend-modern/src/features/docs/__tests__/aiProviderPrivacyGuide.test.ts b/frontend-modern/src/features/docs/__tests__/aiProviderPrivacyGuide.test.tsnew file mode 100644index 0000000000..3862d74809--- /dev/null+++ b/frontend-modern/src/features/docs/__tests__/aiProviderPrivacyGuide.test.ts@@ -0,0 +1,80 @@+import { readFileSync } from 'node:fs';+import path from 'node:path';+import { describe, expect, it } from 'vitest';+import { createGuideFixture } from './guideFixture';++const read = (file: string) => readFileSync(path.resolve(process.cwd(), '..', file), 'utf8');+const article = createGuideFixture((name) => read(`frontend-modern/public/docs/${name}.md`));+const text = (element: Element) => element.textContent!.replace(/\s+/g, ' ');++describe('AI provider privacy guidance', () => {+ it('corrects the local-processing promise before the Patrol walkthrough', () => {+ const rendered = article('AI');+ expect(text(rendered)).not.toContain('BYOK for complete privacy');+ expect(text(rendered)).not.toContain('only sends the minimal context');+ const notice = [...rendered.querySelectorAll('p')].find((node) =>+ text(node).includes('BYOK does not make model processing local'),+ );+ expect(notice).toBeDefined();+ expect(text(notice!)).toContain('a hosted model receives provider-bound context');+ expect(notice!.querySelector('a')?.getAttribute('href')).toBe('#privacy');+ const patrol = rendered.querySelector('#pulse-patrol');+ expect(patrol).not.toBeNull();+ expect(notice!.compareDocumentPosition(patrol!) & Node.DOCUMENT_POSITION_FOLLOWING).toBeTruthy();+ });++ it('keeps model traffic, policy handling and usage telemetry distinct in both guides', () => {+ for (const [name, id] of [+ ['AI', 'privacy'],+ ['PRIVACY', 'ai-provider-data'],+ ]) {+ const rendered = article(name);+ const heading = rendered.querySelector(`#${id}`);+ expect(heading, name).not.toBeNull();+ const section = document.createElement('section');+ for (+ let node = heading!.nextElementSibling;+ node && !/^H[12]$/.test(node.tagName);+ node = node.nextElementSibling+ ) {+ section.appendChild(node.cloneNode(true));+ }+ const copy = text(section);+ for (const distinction of [+ 'resource names and addresses',+ 'tool results',+ 'retention and training policies',+ 'Internal and Sensitive resources can still be shared with a hosted model',+ 'do not make every',+ 'does not forward requests elsewhere',+ 'does not stop AI provider requests or delete locally retained AI history',+ ]) {+ expect(copy, name).toContain(distinction);+ }+ expect(section.querySelector('pre'), name).toBeNull();+ }+ });++ it('links the real provider and local-history boundaries without weakening restricted access', () => {+ const rendered = article('AI');+ const copy = text(rendered);+ expect(copy).toContain('known restricted identifiers are redacted');+ expect(copy).toContain('secret filtering');+ expect(copy).toContain('Keep credentials out of notes and prompts');+ expect(copy).toContain('External MCP clients have their own data flow');+ expect(copy).toContain('tool results it is authorised to read');+ expect(rendered.querySelector('a[href="/docs/PRIVACY#ai-provider-data"]')).not.toBeNull();+ expect(article('PRIVACY').querySelector('#ai-provider-data')).not.toBeNull();+ expect(+ rendered.querySelector('a[href="/docs/CONFIGURATION#handle-configuration-and-history-privately"]'),+ ).not.toBeNull();+ expect(article('CONFIGURATION').querySelector('#handle-configuration-and-history-privately')).not.toBeNull();+ expect(copy).toContain('locally reviewed and redacted excerpt');+ });++ it('ships the same two guides through Docs and the repository', () => {+ for (const name of ['AI', 'PRIVACY']) {+ expect(read(`frontend-modern/public/docs/${name}.md`)).toBe(read(`docs/${name}.md`));+ }+ });+});