DemandVector Subprocessor Register
Effective Date: August 18, 2026
1. ABOUT THIS REGISTERDemandVector Inc ("DemandVector," "we," "us," or "our") engages the service providers identified in Sections 2 and 3 to process Client Data on DemandVector's behalf in connection with the Services. These providers are subprocessors for purposes of applicable data protection laws and agreements.
Section 4 separately identifies third-party integrations that a Client may select, enable, or connect to the Services through the authorization controls provided by those providers. These Customer-Directed Integration Providers are identified for transparency but are not DemandVector subprocessors solely because a Client authorizes an integration. Their processing is also governed by the Client's agreement with the applicable provider.
2. CORE PLATFORM SUBPROCESSORSCore Platform Subprocessors provide infrastructure required to operate the Services.
2.1 Amazon Web Services, Inc.Function: Cloud infrastructure, application hosting, databases, storage, backups, and infrastructure logging.
Client Data Processed: Client Data stored in or processed through the Services.
Provider Headquarters: United States.
3. FEATURE-DEPENDENT SUBPROCESSORSFeature-Dependent Subprocessors process Client Data only when the related Service functionality is used.
3.1 OpenAI, L.L.C.Function: LLM inference for Workflows.
When Used: When a Workflow invokes an OpenAI model.
Client Data Processed: Workflow inputs and related context sent to the model, and model outputs returned to DemandVector.
Provider Headquarters: United States.
3.2 Twilio Inc. (SendGrid)Function: Campaign and service-email delivery and delivery-event processing.
When Used: When the Services send an email through SendGrid or process a related delivery event.
Client Data Processed: Recipient information, email content, message metadata, and delivery or engagement events.
Provider Headquarters: United States.
4. CUSTOMER-DIRECTED INTEGRATION PROVIDERSDemandVector exchanges data with the following providers only when a Client authorizes the related integration.
4.1 HubSpot, Inc.Function: CRM integration.
When Used: When a Client authorizes a HubSpot connection through HubSpot's authorization controls.
Data Exchanged: OAuth credentials and tokens, contacts, companies, lists, list membership, and related CRM data authorized by the Client.
Provider Headquarters: United States.
4.2 PipedriveFunction: CRM integration.
When Used: When a Client authorizes a Pipedrive connection through Pipedrive's authorization controls.
Data Exchanged: OAuth credentials and tokens, contacts, organizations, filters, and related CRM data authorized by the Client.
Provider Location: Determined by the Client's Pipedrive account and contracting region.
4.3 LinkedIn CorporationFunction: LinkedIn account and content integration.
When Used: When a Client authorizes a LinkedIn connection through LinkedIn's authorization controls.
Data Exchanged: OAuth credentials and tokens, account information, and content or activity data authorized by the Client.
Provider Headquarters: United States.
4.4 Google LLCFunction: Google service integrations.
When Used: When a Client authorizes a Google connection through Google's authorization controls.
Data Exchanged: OAuth credentials and tokens, account information, and data made available through the Google services and access scopes authorized by the Client.
Provider Headquarters: United States.
5. CHANGES TO THIS REGISTERDemandVector may add, replace, or remove subprocessors as the Services evolve. DemandVector will provide notice of a material change as required by the applicable agreement or data processing addendum.
Questions about this register may be sent to privacy@demandvector.io.
1. ABOUT THIS REGISTERDemandVector Inc ("DemandVector," "we," "us," or "our") engages the service providers identified in Sections 2 and 3 to process Client Data on DemandVector's behalf in connection with the Services. These providers are subprocessors for purposes of applicable data protection laws and agreements.
Section 4 separately identifies third-party integrations that a Client may select, enable, or connect to the Services through the authorization controls provided by those providers. These Customer-Directed Integration Providers are identified for transparency but are not DemandVector subprocessors solely because a Client authorizes an integration. Their processing is also governed by the Client's agreement with the applicable provider.
2. CORE PLATFORM SUBPROCESSORSCore Platform Subprocessors provide infrastructure required to operate the Services.
2.1 Amazon Web Services, Inc.Function: Cloud infrastructure, application hosting, databases, storage, backups, and infrastructure logging.
Client Data Processed: Client Data stored in or processed through the Services.
Provider Headquarters: United States.
3. FEATURE-DEPENDENT SUBPROCESSORSFeature-Dependent Subprocessors process Client Data only when the related Service functionality is used.
3.1 OpenAI, L.L.C.Function: LLM inference for Workflows.
When Used: When a Workflow invokes an OpenAI model.
Client Data Processed: Workflow inputs and related context sent to the model, and model outputs returned to DemandVector.
Provider Headquarters: United States.
3.2 Twilio Inc. (SendGrid)Function: Campaign and service-email delivery and delivery-event processing.
When Used: When the Services send an email through SendGrid or process a related delivery event.
Client Data Processed: Recipient information, email content, message metadata, and delivery or engagement events.
Provider Headquarters: United States.
4. CUSTOMER-DIRECTED INTEGRATION PROVIDERSDemandVector exchanges data with the following providers only when a Client authorizes the related integration.
4.1 HubSpot, Inc.Function: CRM integration.
When Used: When a Client authorizes a HubSpot connection through HubSpot's authorization controls.
Data Exchanged: OAuth credentials and tokens, contacts, companies, lists, list membership, and related CRM data authorized by the Client.
Provider Headquarters: United States.
4.2 PipedriveFunction: CRM integration.
When Used: When a Client authorizes a Pipedrive connection through Pipedrive's authorization controls.
Data Exchanged: OAuth credentials and tokens, contacts, organizations, filters, and related CRM data authorized by the Client.
Provider Location: Determined by the Client's Pipedrive account and contracting region.
4.3 LinkedIn CorporationFunction: LinkedIn account and content integration.
When Used: When a Client authorizes a LinkedIn connection through LinkedIn's authorization controls.
Data Exchanged: OAuth credentials and tokens, account information, and content or activity data authorized by the Client.
Provider Headquarters: United States.
4.4 Google LLCFunction: Google service integrations.
When Used: When a Client authorizes a Google connection through Google's authorization controls.
Data Exchanged: OAuth credentials and tokens, account information, and data made available through the Google services and access scopes authorized by the Client.
Provider Headquarters: United States.
5. CHANGES TO THIS REGISTERDemandVector may add, replace, or remove subprocessors as the Services evolve. DemandVector will provide notice of a material change as required by the applicable agreement or data processing addendum.
Questions about this register may be sent to privacy@demandvector.io.