Logo de CORMAIA

Subprocessors

This list is Annex 3 of COR's Data Processing Agreement. COR gives Customers at least 30 days' notice by email before adding or replacing a subprocessor.

Last Updated: November 10, 2026

Contents

By entering into this Agreement through execution or incorporation by reference, the Customer authorises COR to engage the Subprocessors in Table 1, which are those authorised as at the Effective Date. COR notifies updates to them in accordance with clause 10 and with the change procedure in this Annex. Providers listed below act as Subprocessors only to the extent they process Customer Personal Data on COR’s behalf in providing the Services. Processing for COR’s independent controller purposes is outside the scope of this Agreement and is described in the Privacy Policy.

Table 1 - Infrastructure and Service Subprocessors#

ProviderCountry of establishmentPurpose of the processing
Amazon Web Services, Inc.United StatesHosting, compute, storage, databases, sending of the service’s transactional email, and language model inference
CloudflareUnited StatesNetwork and edge execution services for the service’s access points, with the associated storage
OpenAIUnited StatesLanguage model inference for the assisted functionality
AnthropicUnited StatesLanguage model inference for the assisted functionality
TavilyUnited StatesSearch and information retrieval for the assisted functionality
PineconeUnited StatesStorage of vector representations for semantic search
LangChain (LangSmith)United StatesObservability and diagnostics of the model-assisted functionality, including storage of Input, Output and related traces containing Customer Personal Data, with a configured retention period of fourteen (14) days.
Grafana LabsUnited StatesObservability, metrics and application logs
SentryUnited StatesDetection and diagnosis of application errors
GoogleUnited StatesEmail, communications and operational notifications, platform services for product functionality, language model inference of the Gemini family, and tag management on the service’s front end
MicrosoftUnited StatesCommunications and operational notifications, and integration with the Customer’s collaboration tools
ZendeskUnited StatesManagement of support requests
Appcues, Inc.United StatesIn-app user guidance and onboarding flows, with the associated user and usage identifiers
Retently (Remsys, Inc.)United StatesSatisfaction surveys addressed to the Customer’s users
ChargebeeUnited StatesBilling and subscription management
MetabaseUnited StatesInternal analytics over operational service data
Amplitude, Inc.United StatesProduct analytics over use of the Services, with the associated user and usage identifiers
HubSpotUnited StatesManagement of the commercial relationship with the Customer

Table 1 comprises the third parties that process Customer Personal Data on COR’s behalf. It does not comprise the suppliers COR engages for its own administration without access to Customer Personal Data, nor the third parties the Customer selects under Table 2, nor the infrastructure COR operates itself.

Tag management. COR operates a tag-management layer on the front end of the Services, through which identification and usage data of the categories described in Annex 1 is transmitted to Subprocessors identified in Table 1. COR does not enable in that layer the transmission of Customer Personal Data to any third party that is not identified in Table 1. Enabling a tag that transmits Customer Personal Data to a third party constitutes the addition of a Subprocessor and is subject to the notice and objection procedure in this Annex and in clause 10.

Model-assisted functionality. Language model inference is provided through Amazon Web Services, OpenAI, Anthropic and Google. Where a model is served through Amazon Bedrock, it runs on Amazon Web Services infrastructure and the Customer Personal Data is not disclosed to the organisation that developed the model, which is accordingly not a Subprocessor. In accordance with clause 15.1, the provider that handles a given interaction may vary among those listed depending on model availability.

The purpose stated delimits the processing authorised for each Subprocessor, which is not permitted to process Customer Personal Data for any other purpose.

The country stated is that of establishment of the entity with which COR contracts; a Subprocessor may process Customer Personal Data from another location. Those transfers are governed by clause 11 and by Annex 4.

Table 2 - Customer-Directed Integrations#

A third party that the Customer selects and enables by its own decision, by activating an integration or configuring an output destination, is not a Subprocessor of COR. COR carries out the transmission on the Customer’s instruction, and the subsequent processing by that third party is the Customer’s responsibility; the Customer acts as controller towards it and determines which integrations it enables and with what scope.

Category of destination selected by the CustomerExamplesSubsequent processing
Customer management systemsEnterprise resource planning, accounting, human resources, or issue and project management systemsCustomer’s responsibility
Automation or integration platforms contracted by the CustomerWorkflow orchestration services between applications, under the account the Customer contractsCustomer’s responsibility
Customer productivity and communication toolsThe Customer’s email, calendar and corporate messaging servicesCustomer’s responsibility
Model providers configured by the CustomerInference services for which the Customer supplies the credentialCustomer’s responsibility
Customer-Connected AI ToolsThird-party AI applications, assistants, models or agents that the Customer connects through COR’s APIs, MCP servers or connectors (Section 9 of the AI Additional Terms)Customer’s responsibility
Output destinations configured by the CustomerAccess points designated by the Customer to receive service dataCustomer’s responsibility

Change Procedure#

COR will give notice of every addition or replacement of a Subprocessor not less than thirty (30) days in advance. COR sends the notice by email to the privacy contact the Customer has designated and, failing that, to the contact registered in the Services. The Customer may designate or change that contact, and indicate additional destination addresses, by communication to the privacy address stated in the contact section. That contact is also the one that completes, in accordance with provision A.8 of Annex 4, the data exporter’s contact person row in Annex I.A to the SCCs.

The Customer may object to the change with reasons within the notice period, with the effects provided for in clause 10. This procedure applies to the enabling of a tag in the tag-management layer on the same terms as to any other addition of a Subprocessor.

For a Customer subject to Chilean law, the authorisation of each Subprocessor is governed by provision D.1 of Annex 4.

Questions about this document?

Write to legals@projectcor.com. COR Global Ltd., 900 Foulk Road, Suite 201, Wilmington, DE 19803, United States.