SUBPROCESSOR LIST

Used for RUNSHIFT authentication, PostgreSQL, storage and Edge Functions. Workspace/account/source/evidence data may be processed as required by the deployed RUNSHIFT environment.

Used for server-side candidate-generation and planning functions. The model receives explicitly constructed structural context for those functions. HubSpot OAuth tokens, call transcripts and email bodies are not part of the required model input.

The production hosting/runtime serving RUNSHIFT processes application and request traffic according to the deployed architecture. The actual provider, region and contractual terms are recorded for the production environment rather than inferred here.

HubSpot is the customer's connected CRM/source system. Its contractual role in the customer's stack is addressed in the customer-specific data-flow and DPA review where legally appropriate.

A new production service that can receive or process customer data is added to the production register before that access occurs.