Subprocessors

This page lists representative subprocessors and integration partners—third parties that process data in connection with the Prometheus Signal Service. It supplements our Privacy Policy and our Terms of Service. We use written terms with subprocessors where applicable, including data processing agreements when required by law or contract.

This list is not complete. We rely on additional vendors, APIs, and regional providers over time, and social or publishing platforms may change names, APIs, or ownership. We will update this page when we add or replace material providers. If something is not named here, it may still be in use—contact us if you need specifics for procurement or compliance.

Infrastructure, hosting, and edge

Cloud, CDN, DNS, database, object storage, backup, and related services that host and deliver the Service. Examples include typical hyperscale cloud and PaaS providers (and more) depending on how and where you deploy or we operate environments.

AI and machine-learning APIs

Model and inference providers used for generation, reasoning, QA, and similar features. Examples we use or may use include:

• Anthropic (Claude) — language and automation in the Brain, factory, QA, and related pipelines;
• OpenAI — language and image-generation APIs when those features are enabled;
• and more — additional model providers, embedding services, or hosted ML APIs we add for features, evaluation, or redundancy. Each processes inputs/outputs under its own terms and our contractual safeguards where applicable.

Social media, publishing, and scheduling APIs

When you connect accounts or publish through the Service, data flows to third-party platforms and their APIs. Those companies act under their own terms and privacy policies. Platforms and products we integrate with or support in the product experience include, without limitation:

• Buffer — scheduling and multi-channel publishing (API and OAuth flows);
• X (Twitter) — posts, threads, and related APIs where connected;
• LinkedIn — professional network publishing where connected;
• TikTok — short-form video and caption workflows where supported;
• Meta (e.g. Facebook / Instagram family of products) where integrations or future connectors apply;
• Google (e.g. YouTube or other Google APIs) where used for auth, media, or publishing;
• Reddit or other data/source APIs when used for research or content inputs;
• and more — any other social, ads, analytics, or creator platforms we add via API, OAuth, webhook, or partner program. You are responsible for each platform’s developer rules and automation policies.

Payments, billing, and finance

When paid plans exist, payment processors, tax engines, invoicing tools, and banking partners process transaction and billing data as subprocessors or independent controllers under their terms, as shown at checkout—plus more regional or backup providers as we scale.

Email, notifications, and support

Providers for transactional email, in-app messaging infrastructure, customer-support tooling, and status pages—and more as we add channels.

Analytics, monitoring, logging, and security

Error tracking, uptime monitoring, log aggregation, SIEM, bot/abuse detection, secrets management, and similar operational tools—and more over time.

Questions

For subprocessors, DPAs, or data processing questions, contact us via Contact.