Skip to content

Sub-processors

List in force as of 24 October 2026

MARTÍNEZ CAMPOY CONSULTING, S.L. · InvokeApp

This is the version in force, archived exactly as published.
Version 2026-10-24 · 24 October 2026 · sha256 ef8e76a6b71b8041047a1f937aabe6df870c494d8c3b5350dc97836331123ab6
Download the original file: ES · EN · All versions

This is a translation. In case of discrepancy, the Spanish version prevails.

Service providers that process personal data on behalf of InvokeApp when providing the service. This is the Sub-processor Annex referred to in clause 16.2 of the Terms of Service and Annex C of the Data Processing Agreement. Any addition or replacement is notified 30 days in advance (clause 16.3 of the Terms of Service and clause 7.2 of the Agreement).

ProviderServiceDataProcessing locationSafeguard outside the EEA
Google Cloud EMEA Limited (Ireland)Hosting of the platform and the agents: compute, database, files, queues, scheduled tasks, secrets, logs and backups; website hostingAll platform dataEuropean Union: Madrid (europe-southwest1) for compute, database and files; Belgium (europe-west1) for task queues and scheduled tasks; messages between the platform and the agents (Pub/Sub), in the region closest to the publisher (today, Madrid), with no fixed region configured; backups in the European Union multi-region. Technical logs and secrets: Google Cloud's global location. The website is served from Firebase's global content delivery network (the blog, from the Netherlands, europe-west4)Google Cloud data processing terms; standard contractual clauses and Data Privacy Framework for processing in or access from third countries
Google Cloud EMEA Limited — Vertex AI (Gemini models) and Cloud Text-to-SpeechArtificial intelligence features (including transcription of voice dictation) and text-to-speechOnly the content each feature needs: text and, in voice or image features, the dictated audio (not stored) or the images providedEuropean Union: Belgium (europe-west1); the Netherlands (europe-west4) as a fallback for image generation; text-to-speech through the EU endpointSame as above. No training with customer data
Google Cloud EMEA Limited — Vertex AI (Veo model)Video generation, only if the company enables that featureThe instructions and brand images sent for the videoUnited States (us-central1)Standard contractual clauses and Data Privacy Framework
Google Ireland Limited — Google WorkspaceEmail sent by InvokeApp (platform notices and communications)Email address, name and message contentEuropean Union and United StatesStandard contractual clauses and Data Privacy Framework
Brevo (Sendinblue SAS, France)Sending email from the invokeapp.io domain (platform notices and communications)Email address, name and message contentEuropean Union—
Stripe Payments Europe, Ltd. (Ireland)Payments and subscriptionsBilling and payment dataEuropean Union and United StatesStandard contractual clauses and Data Privacy Framework. Stripe is an independent controller for its own legal obligations
Meta Platforms Ireland LimitedWhatsApp Business PlatformPhone numbers, messages, templates and account identifiersEuropean Union and United StatesMeta processor terms; Data Privacy Framework and standard contractual clauses
Twilio Ireland LimitedWhatsApp and SMS for the receptionist and appointment managementPhone numbers and message contentEuropean Union and United StatesStandard contractual clauses and Data Privacy Framework
360dialog GmbH (Germany)Alternative WhatsApp provider, only if the customer chooses itPhone numbers and messagesEuropean Union—

Recipients that act as independent controllers

They are not sub-processors: they receive the data under their own terms and decide on it as independent controllers. They are listed here because the data leaves the EEA without a Chapter V GDPR safeguard in place.

RecipientUse by InvokeAppData they receiveLocationSafeguard outside the EEA
Telegram FZ-LLC (United Arab Emirates)Internal technical alerts for the InvokeApp teamEvent codes, internal identifiers (of the execution, the integration and the company) and the type of technical error. They do not receive the content of emails or WhatsApp messages, their subject, the data of forms or support tickets, or names, email addresses or phone numbers. Before each alert is sent, email addresses, phone numbers, identity documents (Spanish DNI and NIE), tax IDs (CIF), IBANs, card numbers, social security numbers, IP addresses and keys or tokens are masked, and of the rest of the text only identifiers, codes, error types and technical labels are keptOutside the EEANone in place: according to its privacy policy, Telegram acts as an independent controller and does not sign processing agreements or standard contractual clauses with those who use its bots

Third parties that receive data only when the company enables a feature

They are not sub-processors: they process the queries under their own terms, not on behalf of InvokeApp.

Third partyInvokeApp featureData they receiveLocationRegime
Google — Google Maps Platform (Places API) and Custom Search JSON APILead prospecting and enrichment, only if the company enables those featuresSearch terms: sector, area and the lead's business name (which, for a sole trader, may be a person's name)GlobalGoogle processes these queries under its own terms, not as InvokeApp's processor (for Google Maps Platform, as an independent controller). Google LLC participates in the Data Privacy Framework

Services the customer connects with its own account (for example its Gmail or Google Calendar, HubSpot, Salesforce, Typeform, Slack, its Brevo or Mailchimp account, Calendly, WordPress, its social networks, its Telegram channel or its Meta app) are not listed: there the provider works for the customer, not for InvokeApp. Importing a CSV file (for example from Apollo.io) does not connect InvokeApp to that provider.