> For the complete documentation index, see [llms.txt](https://docs.cerrix.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cerrix.com/about-cerrix/trust-and-compliance/subprocessors.md).

# Subprocessors

The third-party subprocessors CERRIX engages that may process client-related personal data, including their purpose, the data involved and processing location.

CERRIX works with a limited number of carefully selected third-party service providers (subprocessors) that may process personal data on our behalf. We believe in being fully transparent about who these parties are, what they do for us, and which data they may process.

Every subprocessor listed below has been assessed as part of our third-party risk management process, and appropriate data processing agreements are in place. The large majority of our subprocessors process data within Europe; where data is transferred outside the European Economic Area (EEA), this is done on the basis of Standard Contractual Clauses (SCCs).

## Client-related subprocessors

The sections below list the subprocessors that may process client-related personal data, grouped by the scope in which they are used.

### Product

Subprocessors used to build, host and operate the CERRIX platform.

<table><thead><tr><th>Subprocessor</th><th>Category</th><th width="211.953125">Purpose of Processing</th><th width="221.3125">Personal Data Processed</th><th width="183.12890625">Data Processing Location</th></tr></thead><tbody><tr><td>Microsoft BV</td><td>Cloud Infrastructure &#x26; Productivity</td><td>Platform hosting (Azure), productivity suite (M365), DevOps, CI/CD pipelines, AI services (Microsoft Foundry)</td><td>Client data, employee data, platform content</td><td>EU</td></tr><tr><td>Cloudmersive</td><td>Document Processing &#x26; Security</td><td>Document conversion and virus scanning APIs</td><td>Files and documents uploaded by users</td><td>EU</td></tr><tr><td>GitHub</td><td>Source Code Management</td><td>Source code management, CI/CD and engineering collaboration</td><td>Developer account data, source code repositories</td><td>EU</td></tr><tr><td>SendGrid</td><td>Transactional Email</td><td>Transactional email delivery for platform notifications</td><td>User email addresses, notification content. Data transfer outside the EEA on the basis of Standard Contractual Clauses (SCCs)</td><td>United States</td></tr></tbody></table>

### Marketing & Sales

Subprocessors used for lead generation, marketing, website and sales processes.

<table><thead><tr><th>Subprocessor</th><th>Category</th><th width="211.953125">Purpose of Processing</th><th width="221.3125">Personal Data Processed</th><th width="183.12890625">Data Processing Location</th></tr></thead><tbody><tr><td>HubSpot</td><td>CRM &#x26; Marketing Automation</td><td>Lead management, CRM and sales/marketing processes</td><td>Prospect and client contact data</td><td>EU</td></tr><tr><td>Usercentrics</td><td>Consent Management</td><td>GDPR cookie and consent compliance for website visitors</td><td>Website visitor consent records</td><td>EU</td></tr><tr><td>Webinargeek</td><td>Webinar Platform</td><td>Online events, training and marketing webinars</td><td>Registrant names, email addresses, attendance data</td><td>EU</td></tr><tr><td>Leexi</td><td>Conversation Intelligence</td><td>Meeting recording and sales conversation intelligence</td><td>Audio/video recordings of meetings, participant names, transcripts</td><td>EU</td></tr><tr><td>Lemlist</td><td>Sales Outreach Automation</td><td>Personalised cold email and LinkedIn outreach campaigns</td><td>Prospect contact data used in outreach campaigns</td><td>EU</td></tr><tr><td>Snitcher</td><td>Website Visitor Intelligence</td><td>Company identification of website visitors via IP resolution</td><td>Company IP addresses, visitor identification data</td><td>EU</td></tr><tr><td>Leadinfo</td><td>Website Analytics</td><td>Website visitor identification based on IP lookup</td><td>Company visitor data, IP addresses</td><td>EU</td></tr><tr><td>Webflow</td><td>Website &#x26; CMS</td><td>Marketing website hosting and content management</td><td>Website visitor data. Data transfer outside the EEA on the basis of Standard Contractual Clauses (SCCs)</td><td>United States</td></tr><tr><td>Clay</td><td>Data Enrichment</td><td>Contact and company data enrichment for sales and marketing</td><td>Prospect contact data enriched from external sources. Data transfer outside the EEA on the basis of Standard Contractual Clauses (SCCs)</td><td>United States</td></tr><tr><td>Walego</td><td>Website &#x26; CMS</td><td>AI-driven lead search, qualification, and personalized outreach message generation to support sales/business development</td><td>Business contact data of prospects (name, job title, company, LinkedIn profile URL, email address where available)</td><td>EU</td></tr></tbody></table>

### Operations

Subprocessors used to run CERRIX's internal business operations.

<table><thead><tr><th>Subprocessor</th><th>Category</th><th width="211.953125">Purpose of Processing</th><th width="221.3125">Personal Data Processed</th><th width="183.12890625">Data Processing Location</th></tr></thead><tbody><tr><td>Qics</td><td>Internal Tooling</td><td>Time tracking and invoicing administration for internal CERRIX employees and projects.</td><td>Employee names, worked hours, project allocations, client contact data and invoicing data.</td><td>EU</td></tr><tr><td>Slack (SFDC Ireland)</td><td>Internal Communications</td><td>Internal communication and collaboration platform</td><td>Employee personal data, client contact data, internal communications</td><td>EU</td></tr><tr><td>Anthropic PBC</td><td>AI Platform</td><td>AI assistance and content generation in support of CERRIX's internal business processes, including drafting communications, document analysis, and summarisation. Not used in the CERRIX product or platform.</td><td>Names, email addresses, and contact details of clients, prospects, and employees incidentally included in content submitted by CERRIX staff. Data transfer outside the EEA on the basis of Standard Contractual Clauses (SCCs)</td><td>United States</td></tr></tbody></table>

### Support

Subprocessors used to deliver client support and service management.

<table><thead><tr><th>Subprocessor</th><th>Category</th><th width="211.953125">Purpose of Processing</th><th width="221.3125">Personal Data Processed</th><th width="183.12890625">Data Processing Location</th></tr></thead><tbody><tr><td>Lovable.dev</td><td>AI App Development</td><td>AI-powered application development platform for internal and client-related tooling</td><td>Client contact data, community ticket content</td><td>EU: Database<br>United States: Telemetry and Logging</td></tr><tr><td>HaloPSA</td><td>IT Service Management</td><td>Help desk, ticketing and IT service management</td><td>Client contact data, support ticket content</td><td>EU</td></tr></tbody></table>

## International data transfers

Wherever possible, CERRIX selects subprocessors that process data within Europe. For the subprocessors located outside the EEA, data transfers take place on the basis of Standard Contractual Clauses (SCCs) as approved by the European Commission, complemented by additional technical and organisational safeguards where appropriate.

## Changes to this list

We review our subprocessor list periodically as part of our third-party risk management process and update this page whenever a subprocessor is added, replaced, or removed.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.cerrix.com/about-cerrix/trust-and-compliance/subprocessors.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.