SignalOS
Placeholder — pending legal review. This is a factual, code-grounded list of real third parties SignalOS can send data to, not a binding contractual commitment. A real Data Processing Agreement needs a licensed attorney to formalize the terms under which each of these operates.

Subprocessors

Version 1.0.0 — effective 2026-08-28. This list changes only when a real new integration ships in the product; each change gets a new version.

AI answer-measurement engines

Each of these can be disabled per client, for a client whose contract or data-processing requirements rule a specific engine out — a signed-in agency user finds this under Diagnose → Context → AI Engines on any client.

SubprocessorPurposeData sharedActive
Anthropic (Claude)Measures how this AI engine describes a brand in answer text; also powers in-app AI-assisted analysis features.The query text being measured, and any content an analysis feature is run against (e.g. crawled page text, customer-voice text).when configured
OpenAI (ChatGPT)Measures how this AI engine describes a brand in answer text.The query text being measured.when configured
Perplexity AIMeasures how this AI engine describes a brand in answer text.The query text being measured.when configured
Google (Gemini, AI Overviews / AI Mode)Measures how these AI engines describe a brand in answer text.The query text being measured.when configured
xAI (Grok)Measures how this AI engine describes a brand in answer text.The query text being measured.when configured
Microsoft (Copilot / Bing)Measures how this AI engine describes a brand in answer text.The query text being measured.when configured

Optional data connectors

Opt-in by construction: none of these is contacted until an organization completes that provider’s own OAuth or API-key connection for a specific client.

SubprocessorPurposeData sharedActive
MozBacklink/domain-authority data for SEO analysis.Domain names being analyzed.when configured
Google (Search Console, Analytics 4)Search performance and site-analytics data.OAuth-scoped read access to the connected property's search/analytics data.when configured
SalesforceCRM data for buyer-journey and pipeline context.OAuth-scoped read access to the connected CRM objects.when configured
HubSpotCRM data for buyer-journey and pipeline context.OAuth-scoped read access to the connected CRM objects.when configured
WordPress / Contentful / ShopifyCMS content for content-intelligence analysis.API-key-scoped read access to the connected site's content.when configured

Operational subprocessors

SubprocessorPurposeData sharedActive
StripePayment processing and billing.Billing contact details and payment method — SignalOS itself never stores card numbers.when configured
ResendTransactional email delivery (invites, password resets, alert notifications, scheduled report delivery).Recipient email address and message content.when configured
Cloud object storage (S3-compatible)Stores generated exports, report PDFs, and uploaded assets.The file being stored.when configured

Not yet stated here

The hosting/infrastructure provider running this deployment is an operational choice made outside this codebase and isn’t named here — whoever operates a real deployment should add it. Per-subprocessor data-processing terms, SCCs/international-transfer mechanisms, and a formal change-notification process for this list all require real legal drafting — see /legal/data-processing.