NeuroPage
Legal

Subprocessors

Every third party that can receive personal data because NeuroPage sends it to them, with what it does, where it holds the data, and which categories of data reach it. Published so that a customer can copy it straight into their own processing register. Read alongside the Privacy Policy and the Data Processing Agreement.

Last updated: 7 September 2026

Notice of changes

We give customers at least 30 days notice before a new subprocessor starts processing their personal data. A customer may object on reasonable data protection grounds within that period, and where we cannot offer a workable alternative the customer may terminate the affected part of the Services without penalty. To receive these notices, write to privacy@neuropage.io.

Infrastructure

ProviderPurposeLocationDataTransfer safeguard
SupabasePrimary database and file storage. Holds accounts, leads, generated pages, and generated messages.European Union (eu-west-1, Ireland)Account and contact data, professional profile and lead data, generated content, persona analysis outputNo transfer outside the EEA for data at rest
CloudflareEdge compute for page generation and page serving (Workers), object storage for page assets (R2), CDN and network security.European Union (R2 buckets created with EU jurisdiction; CDN edge serving is global by design)Generated pages and page assets, visitor IP address and request metadataEU Standard Contractual Clauses under the provider DPA
VercelHosting for the NeuroPage web application and its API routes.European Union (eu-west deployment region)Account and contact data, usage data, application logs, request metadataEU Standard Contractual Clauses under the provider DPA

AI models

ProviderPurposeLocationDataTransfer safeguard
OpenRouterRoutes copy generation requests to the text model used to write page copy and outbound messages.United StatesProfessional profile context and the prompt built from it, generated copyEU Standard Contractual Clauses under the provider DPA
AnthropicModels used for content analysis, output quality checks, and image understanding.United StatesProfessional profile context, page and brand content submitted for analysisEU Standard Contractual Clauses under the provider DPA
GroqModels used for persona analysis and for extracting structured fields from submitted content.United StatesProfessional profile data used to derive the persona analysis described in Article 7 of the Privacy PolicyEU Standard Contractual Clauses under the provider DPA

Research and enrichment

ProviderPurposeLocationDataTransfer safeguard
AirscaleLooks up professional profile and company data for a submitted lead.European UnionName, employer, job title, LinkedIn URL and other professional profile identifiersNo transfer outside the EEA for data at rest
ApolloProfessional profile and company lookup, and contact list synchronisation.United StatesName, work email address, employer, job title and other professional profile identifiersEU Standard Contractual Clauses under the provider DPA
ExaWeb search used to research a lead and their employer before a page is written.United StatesSearch queries containing a name, employer, or job titleEU Standard Contractual Clauses under the provider DPA
LinkupWeb search used to research a lead and their employer before a page is written.European Union (France)Search queries containing a name, employer, or job titleNo transfer outside the EEA for data at rest
FirecrawlReads the content of public web pages, including a customer website during onboarding and a lead employer website during research.United StatesURLs submitted for extraction and the public page content returnedEU Standard Contractual Clauses under the provider DPA
PredictLeadsCompany signal data, used as a fallback source for technology and hiring signals.European Union (Slovenia)Company identifiers and public company signalsNo transfer outside the EEA for data at rest

Communications

ProviderPurposeLocationDataTransfer safeguard
ResendSends transactional email from the platform, such as sign-in links, invitations, and service notifications.United StatesWork email address, name, message contentEU Standard Contractual Clauses under the provider DPA
Google WorkspaceInternal email, documents, and the mailbox that answers privacy and support requests.European Union and United StatesCorrespondence with NeuroPage, including anything a sender chooses to includeEU Standard Contractual Clauses under the provider DPA

Analytics

ProviderPurposeLocationDataTransfer safeguard
PostHogProduct analytics for the NeuroPage application. Not loaded on generated pages.European Union (EU Cloud)Usage events within the signed-in applicationNo transfer outside the EEA for data at rest
Google (Tag Manager and Analytics)Tag management and website analytics on the NeuroPage marketing website only. Not loaded on generated pages.United StatesWebsite usage events, IP address, device and browser dataEU Standard Contractual Clauses under the provider DPA
Microsoft (Clarity)Behaviour analytics on the NeuroPage marketing website only. Not loaded on generated pages.United StatesWebsite usage events, IP address, device and browser dataEU Standard Contractual Clauses under the provider DPA

Customer-activated integrations

These are connected by a customer, with the credentials of that customer, and receive data because the customer instructed it. They are the processors of the customer rather than subprocessors of NeuroPage. They are listed here because a customer building its own processing register needs to know that data leaves through these doors.

ServiceWhat it receives and why
HeyReachLinkedIn outreach: enrols leads and sends connection notes and messages.
SmartleadEmail outreach: enrols leads into the customer email sequences.
InstantlyEmail outreach: enrols leads into the customer email sequences.
ReachBoostOutreach and inbound reply synchronisation.
ApolloWhere a customer connects their own Apollo account, contact lists are synchronised into the workspace.

What is deliberately not on this list

  • Payment processing. NeuroPage does not currently process card payments through the platform, so no payment provider receives personal data. This list will be updated before that changes.
  • Tools used only for our own sales and marketing, which never receive customer or prospect data from the platform.
  • Model training providers, because there are none. We do not train models on customer or prospect data, and our model providers do not train on data submitted through their APIs. See Article 8 of the Privacy Policy.