Subprocessors
The launch list of vendors FinkMesh uses to host, store, deliver, bill, authenticate, and support the service.
FinkMesh subprocessors
AI/model providers, including Anthropic and OpenAI, may process prompts, workflow context, or other customer content only when users invoke AI-powered features or configure workflows that use those providers.
| Vendor | Purpose | Data processed | Location/region | Notes | Trust link |
|---|---|---|---|---|---|
| Vercel | Application hosting and deployment | Account, workspace, request, runtime, and application data processed by the hosted app | Provider regions and edge network | Core application infrastructure | Vendor docs |
| Neon | Postgres database | Account, workspace, workflow, run, billing metadata, support, audit, and operations records | Configured database region | Primary production database | Vendor docs |
| Cloudflare | Network, edge, cron, and traffic protection services | Request metadata, cron traffic, IP address, user agent, and security telemetry | Global edge network | Used for edge/network services and email-obfuscation handling on public pages | Vendor docs |
| Stripe | Billing, checkout, invoices, subscription status, and payment portal | Billing contact details, customer identifiers, subscription metadata, invoices, and payment events | Stripe processing regions | FinkMesh does not store raw card details | Vendor docs |
| Resend | Transactional, support, alert, and service email delivery | Recipient, sender, subject, message body, delivery metadata, and support-email content | Provider regions | Used for account, support, billing, workflow, and operational emails | Vendor docs |
| Authentication and OAuth where configured by the user or workspace | Authentication identifiers, email address, profile metadata, OAuth tokens, scopes, and provider events | Google processing regions | Applies when Google sign-in or Google-connected workflows are used | Vendor docs | |
| Anthropic | FinkMesh-managed AI builder and Ask AI node execution where enabled | Prompts, workflow context, inputs, outputs, and metadata needed to perform the requested AI action | Provider regions | May process customer content only when users invoke FinkMesh-managed AI features that use Anthropic models | Vendor docs |
| OpenAI | Embeddings and AI-assisted search or retrieval features where enabled | Text submitted for embedding, query, classification, or retrieval support | Provider regions | May process customer content only when users invoke or configure features that use OpenAI | Vendor docs |
Operational vendors
Some vendors support FinkMesh operations without necessarily processing customer workflow payloads as subprocessors for every customer.
| Vendor | Purpose | Notes | Trust link |
|---|---|---|---|
| GitHub | Source control, code hosting, deployment, and operational collaboration | Operational repository and deployment metadata is separate from customer-directed GitHub workflow integrations. | Vendor docs |
Customer-directed integrations
FinkMesh workflows can send data to third-party services that you choose to connect, such as APIs, OAuth providers, webhook destinations, databases, CRMs, spreadsheets, messaging tools, or internal systems. Those customer-directed services are not always FinkMesh subprocessors; they process data because your workspace configures workflows to send data to them.
Changes
We may update this list as FinkMesh evolves. Material subprocessor changes will be reflected on this page. Customers with signed agreements may receive additional notice rights if stated in their agreement or DPA.
Last material update: July 1, 2026.
Questions
For subprocessor, region, or vendor-risk questions, contact contact@finkmesh.com.