Sub-processor list

Updated 15 July 2026

This page lists the third parties we engage to process data when providing the service. The list supports the Data Processing Agreement (Art. 28(2)/(4) GDPR — transparency of sub-processing and the right to object) and supplements the Privacy Policy.

Sub-processors

Sub-processor	Purpose	Processing region	Safeguards
Google Cloud — Vertex AI Search (Discovery Engine)	Indexing and search over site content	Service's configured Google Cloud region	Google Cloud Data Processing Addendum, SCCs / EU-US DPF, ISO 27001
Google Cloud — Gemini	Query preparation and grounded answer generation	Service's configured Google Cloud region	Google Cloud Data Processing Addendum, SCCs / EU-US DPF; data not used to train Google's models
Google Cloud Storage	Intermediate staging of extracted text for import into the index	Service's configured Google Cloud region	Google Cloud Data Processing Addendum, SCCs / EU-US DPF
Google Cloud Firestore	Owner accounts, service configuration, query logs, and audit records	Service's configured Google Cloud region	Google Cloud Data Processing Addendum, SCCs / EU-US DPF
Firebase Authentication / Identity Platform	Account authentication and session management	Service's configured Google Cloud region	Google Cloud Data Processing Addendum, SCCs / EU-US DPF
Google — reCAPTCHA Enterprise	Optional monitor-only bot and abuse detection when enabled; the widget may send no token	EU / US	Google Cloud Data Processing Addendum, SCCs / EU-US DPF

Paddle — Merchant of Record (not a sub-processor)

Paddle processes subscriptions and payments as Merchant of Record. In that role, Paddle itself determines the purposes and means of processing payment data and acts as an independent controller, not as our sub-processor. We list Paddle here for transparency; the processing of payment data is governed by Paddle's own terms and privacy policy. We do not store card details.

Change notification and the right to object

We give clients advance notice of any intended addition or replacement of a sub-processor (by email and/or in the dashboard) before the new sub-processor begins processing. A client may object on reasonable data-protection grounds within a reasonable period from the notice. If an objection cannot be resolved, the client may stop using the service for the affected processing. The current version of this list is always available on this page.

Contact

Questions about sub-processors — via the contact form.