Sub-processors

Last updated 12 June 2026 · Effective 3 June 2026

To provide GG we use the third-party providers ("sub-processors") below. Each is bound by a data-processing agreement with obligations at least as protective as our own Data Processing Addendum. We update this page before adding or replacing a sub-processor.

Current sub-processors

ProviderServiceData processedLocation
AnthropicAI summarisation, intent classification and enrichment evaluation (Claude)Communication content and client data sent at request time to generate output; not used to train modelsUSA / EU
StripePayment processing & billingBilling contact, plan, payment-method tokens (card data handled by Stripe)USA / EU
ResendTransactional & invite email deliveryRecipient email, name and message contentUSA / EU
[Hosting provider — e.g. IONOS]Cloud hosting, database & backupsAll Customer Data at restEU

Planned / activated when you connect a channel

The following are used only if your workspace enables the relevant live communication channel. Until you connect a channel, no data flows to them.

ProviderServiceData processedLocation
[Email provider — e.g. Nylas]Mailbox connection & email syncEmail metadata and content from connected mailboxesUSA / EU
[Messaging/voice — e.g. Twilio]WhatsApp & voice connectivityPhone numbers, message and call metadata/contentUSA / EU
[Transcription — e.g. Deepgram]Call transcriptionCall audio for transcriptionUSA
[Enrichment — e.g. OpenCorporates]Company registry enrichmentCompany names/identifiers queried for enrichmentEU / UK

Public data sources (not sub-processors)

  • EU VIES — VAT number validation and EU company details.
  • Public web & registries — used for confirm-before-save client enrichment; we read public information, we do not send your Customer Data to them.

Change notices

To be notified of changes to this list, email legal@taskgg.com and ask to be added to our sub-processor notification list. Under the DPA you may object to a new sub-processor on reasonable data-protection grounds.

Template for transparency, not legal advice. Keep this list accurate — it is a GDPR obligation. Replace bracketed providers with the vendors you actually use and confirm each one’s processing location and DPA before launch.