Current provider list
Availability depends on workspace configuration and approved capability use. A listed execution provider receives data only when its capability is enabled and invoked.
| Provider | Purpose | Data involved | Status |
|---|---|---|---|
| Cloudflare | Application hosting, Workers, database, object storage, queues, workflow execution, security | Account, workspace, execution, audit, evidence, and technical data required to operate Taploop | Active |
| Resend | Transactional account and service email when configured | Recipient email, message content, delivery metadata | Configuration dependent |
| Google Analytics | Optional public-website measurement after visitor consent | Page paths, selected action labels, analytics cookies, and standard technical information; no form contents or URL queries | Configuration and consent dependent |
| Bright Data | Bounded public-web search and single-page reading behind Taploop MCP | Search query or requested public URL, normalized public content, provider request metadata | Active |
Not active
DataForSEO, Apify, Firecrawl, and planned advertising, CRM, commerce, publishing, and external creator integrations are not active data sources behind the public Taploop MCP unless this list is updated.
Customer-directed connected services
A service you connect or instruct Taploop to use may act as your provider under its own agreement rather than solely as a Taploop subprocessor. Provider roles and data terms will be clarified during production onboarding.
Changes
Taploop may update this list as the service changes. Enterprise customers may receive advance notice and objection rights through a signed data-processing agreement. Questions can be sent to hello@taploop.agency.