Sub-processors

Last updated: April 14, 2026

ChatSEO, operated by GROW IT, uses the following sub-processors to deliver its services. This page is maintained as a living document and updated whenever sub-processors are added, removed, or changed.

To be notified of changes to this list, enterprise customers with a Data Processing Agreement can subscribe to notifications by emailing [email protected].

Infrastructure & Hosting

Sub-processorPurposeData ProcessedLocationTransfer Mechanism
Hetzner Online GmbHServer hostingAll service dataGermany (EU)N/A (EU)

AI & Machine Learning

Sub-processorPurposeData ProcessedLocationTransfer Mechanism
AnthropicAI-powered SEO analysis (Claude Sonnet 4, Claude Haiku)Conversation content, SEO data (transient, real-time inference only)United StatesEU-US DPF + SCCs
Voyage AIVector embeddings for cross-conversation memoryText content for embedding generationUnited StatesSCCs

Important: Under Anthropic's commercial API terms of service, data submitted via the API is not used for model training. Voyage AI processes data for embedding generation only with no retention. ChatSEO does not use any user data to train, fine-tune, or improve AI models.

Payment & Billing

Sub-processorPurposeData ProcessedLocationTransfer Mechanism
Stripe, Inc.Payment processingBilling details, payment information, subscription dataUnited StatesEU-US DPF + SCCs (PCI-DSS compliant)

Communication

Sub-processorPurposeData ProcessedLocationTransfer Mechanism
ResendTransactional email deliveryEmail address, nameUnited StatesSCCs
Crisp IM SASCustomer support chatName, email, chat conversationsFrance (EU)N/A (EU)

Analytics & Monitoring

Sub-processorPurposeData ProcessedLocationTransfer Mechanism
Mixpanel, Inc.Product analyticsUsage events, email, nameUnited States (EU endpoint)EU-US DPF + SCCs
Customer.io (Peaberry Software Inc.)Marketing automationEmail, name, usage eventsUnited States (EU endpoint)EU-US DPF + SCCs
Sentry (Functional Software Inc.)Error monitoringTechnical errors, IP address, browser infoUnited StatesEU-US DPF + SCCs

Note: Mixpanel and Customer.io only receive data after explicit user consent via our cookie banner (analytics category). They do not initialize without consent.

SEO Data Providers

Sub-processorPurposeData ProcessedLocationTransfer Mechanism
Google APIs (Google LLC)OAuth authentication + Search Console APIOAuth tokens, GSC data (transient, never stored)United StatesEU-US DPF + SCCs
DataForSEOSEO data (keyword research, SERP analysis, backlinks)Public domain/URL dataUnited StatesSCCs
FirecrawlWeb page content scrapingPublic URLs, publicly accessible page contentSelf-hosted (EU - Hetzner)N/A (self-hosted, EU)

Marketing & Attribution

Sub-processorPurposeData ProcessedLocationTransfer Mechanism
Tolt, Inc.Affiliate trackingReferral attribution dataUnited StatesSCCs
Meta Platforms, Inc.Marketing analytics (Facebook Pixel)Page views, conversion eventsUnited StatesEU-US DPF + SCCs

Note: Tolt and Meta Pixel only receive data after explicit user consent via our cookie banner (marketing category). They do not load without consent.

Feature Management

Sub-processorPurposeData ProcessedLocationTransfer Mechanism
FlagsmithFeature flag managementUser identifierEUN/A (EU)

Important Notes

The following sub-processors only receive data after the user has given explicit consent via our cookie banner:

  • Analytics (opt-in required): Mixpanel, Customer.io
  • Marketing (opt-in required): Tolt, Meta Pixel

Without consent, these services do not initialize and receive no data.

Google Search Console data handling

Google Search Console data (queries, impressions, clicks, rankings, page performance) is fetched via the Google Search Console API in real-time using the read-only OAuth scope (webmasters.readonly). This data is returned directly to the user and is never stored in our database, cached in Redis, or persisted in any form. Only OAuth credentials (access token, refresh token) are stored to authenticate API requests on the user's behalf.

AI data handling

Anthropic and Voyage AI process data in real-time for inference and embedding generation respectively. Under their respective commercial API terms of service, data submitted via the API is not used for model training. No user data is retained by these providers beyond the duration of the API request.


Change Log

DateChange
April 14, 2026Initial publication