Got it. Here's the plain page content — just paste it.

PartnerOS Sub-Processors

Last updated: May 11, 2026

PartnerOS, Inc. ("PartnerOS") engages a small number of third-party service providers ("Sub-Processors") to help us deliver, secure, and improve our partner relationship management platform. This page lists the Sub-Processors that may process Customer Personal Data on our behalf, as referenced in our Data Processing Addendum and Privacy Policy.

We enter into written agreements with each Sub-Processor imposing data protection obligations substantially equivalent to those in our DPA. Customers may subscribe to notifications of changes to this list by emailing legal@partneros.ai with the subject line "Subscribe — Sub-Processor Updates." We will provide notice at least thirty (30) days before engaging a new Sub-Processor.

Infrastructure and Hosting

Amazon Web Services, Inc. Purpose: Cloud infrastructure underlying the Services, including compute, storage, and networking provided through the platforms listed below. Data Categories: All categories of Customer Personal Data submitted to the Services. Location: United States

Vercel Inc. Purpose: Application hosting, edge compute, and deployment infrastructure for the PartnerOS web application and API. Data Categories: All categories of Customer Personal Data transmitted through the application layer. Location: United States

Supabase, Inc. Purpose: Managed Postgres database, authentication services, and storage for Customer Content. Data Categories: All categories of Customer Personal Data submitted to the Services. Location: United States

Cloudflare, Inc. Purpose: Content delivery network, DDoS protection, DNS services, and edge compute for partneros.ai and related domains. Data Categories: IP addresses, device identifiers, request metadata, and any Customer Personal Data transmitted through the edge layer. Location: Global edge network

Upstash, Inc. Purpose: Serverless data caching and queue infrastructure (Redis, Kafka) supporting application performance and asynchronous processing. Data Categories: Session data, queued workload items, and cached views of Customer Personal Data. Location: United States

Inngest Inc. Purpose: Background job execution, workflow orchestration, and scheduled task processing for the Services. Data Categories: Job payloads and scheduled-task metadata, which may include Customer Personal Data. Location: United States

Authentication

Supabase, Inc. (Supabase Auth) Purpose: Authentication, session management, and identity federation for Customer workspaces. Data Categories: Names, business email addresses, employer information, and authentication identifiers. Location: United States

Artificial Intelligence

Anthropic, PBC Purpose: Large language model inference powering AI Actions, AI Signals, and other AI-assisted features within the Services. Data Categories: Customer Content and prompts submitted to AI features by Customer. Anthropic is contractually prohibited from using this data for model training. Location: United States

Voyage AI, Inc. Purpose: Vector embeddings for semantic search, retrieval-augmented generation, and AI-assisted features within the Services. Data Categories: Customer Content submitted to AI features, processed to generate embeddings. Location: United States

ElevenLabs Inc. Purpose: AI-generated voice and text-to-speech for the PartnerOS enablement and learning management (LMS) module, where Customer chooses to use this feature. Data Categories: Text content submitted for speech synthesis, and voice samples provided by Customer or its users where voice cloning features are used. Location: United States

FireCrawl (Mendable Labs Inc.) Purpose: Web content extraction for partner research, partner profile enrichment, and AI-assisted features. Data Categories: Public web content retrieved at Customer's direction; URLs and queries provided by Customer. Location: United States

Communications

Resend, Inc. Purpose: Transactional email delivery (account verification, password resets, partner invitations, and notification emails). Data Categories: Names and email addresses of Customer's users and partners. Location: United States

Google LLC (Google Workspace) Purpose: Business email and document collaboration for PartnerOS personnel communicating with Customer. May incidentally process Customer Personal Data in support correspondence. Data Categories: Customer contact information and any Personal Data included in support correspondence. Location: United States

Agreements and E-Signature

DocuSeal Inc. Purpose: E-signature and document workflow infrastructure for agreements that Customer's partners sign through the PartnerOS platform (e.g., partner program agreements, NDAs, reseller terms). Data Categories: Signatory names, business email addresses, IP addresses, and the content of agreements Customer chooses to send for signature through the Services. Location: United States

Billing and Payments

Stripe, Inc. Purpose: Payment processing, subscription billing, invoicing, and tax calculation for Customer's PartnerOS subscription. Data Categories: Billing contact name, business email, billing address, and payment method metadata. Card numbers are processed directly by Stripe; PartnerOS does not store them. Location: United States

Monitoring

Functional Software, Inc. (Sentry) Purpose: Error monitoring, performance monitoring, and crash reporting for the Services. Data Categories: Error and stack-trace data, IP addresses, user-agent strings, and user identifiers needed to investigate issues. Location: United States

Customer-Initiated Integrations

The Services allow Customers to connect third-party systems (such as Salesforce, HubSpot, Slack, Google Drive, and other tools) to their PartnerOS workspace. When a Customer enables an integration, the third-party provider is acting under the Customer's direction and authorization, not as a PartnerOS Sub-Processor. The processing of data by such third parties is governed by the Customer's agreement with that third party.

International Data Transfers

PartnerOS's primary processing occurs in the United States. Where Sub-Processors are located outside the European Economic Area, the United Kingdom, or Switzerland, transfers are governed by the Standard Contractual Clauses and the UK International Data Transfer Addendum as described in our DPA.

Changes to this List

We may add or replace Sub-Processors from time to time as our infrastructure evolves. We will provide notice of changes to subscribed Customers at least thirty (30) days in advance, except where a change must be made more quickly for security, legal compliance, or service continuity reasons (in which case we will notify Customers as soon as practicable).

Subscribe to Updates

To receive notifications when this list changes, email legal@partneros.ai with the subject line "Subscribe — Sub-Processor Updates" and include the Customer entity name and the email address to be notified.