Data minimization
- Do not send unnecessary personal data to optional integrations.
- Do not log raw lead messages or sensitive details where avoidable.
- Use server-side secrets only.
- Keep provider payloads limited.
Trust Center
Subprocessors
Subprocessors are third-party infrastructure and service providers that may process customer data depending on configuration, account settings, and feature usage.
Current provider review
Infrastructure, billing, AI, monitoring, and optional integrations.
This list is intended to help business customers review likely vendor dependencies before onboarding. Optional providers apply only when the relevant feature or environment configuration is enabled.
| Provider | Service category | Purpose | Data categories | Region / transfer note | Status | Notes |
|---|---|---|---|---|---|---|
| Supabase | Database, authentication, storage if configured | Authentication, tenant data, lead records, subscription state | Account identifiers, authentication metadata, tenant records, lead records, subscription references, and storage objects if configured. | EU region configured where available / verify project settings | Core infrastructure | Project region, backups, and enabled services should be verified before customer onboarding. |
| Vercel | Hosting and deployment | Web hosting, serverless runtime, logs | Request metadata, runtime logs, deployment telemetry, and public page assets. | Global edge/runtime provider | Core infrastructure | Server-side secrets should stay in deployment environment variables and never be exposed to client code. |
| Stripe | Payments and billing | Checkout, subscription billing, customer portal, webhook events | Billing contact details, checkout session data, subscription records, invoice references, and payment event metadata. | Stripe global payment infrastructure | Core billing provider | Payment card details are handled by Stripe and should not be stored by the AgentFlow application. |
| OpenAI | AI processing | AI lead qualification and structured scoring | Lead messages, qualification context, scoring inputs, and AI output fields intentionally sent for processing. | Depends on OpenAI processing terms and account configuration | AI provider | Use prompt and payload minimization. Avoid sending unnecessary personal data or sensitive details. |
| HubSpot | CRM integration | Contact sync/enrichment when HUBSPOT_ACCESS_TOKEN is configured | Selected contact fields, company fields, lead status, and CRM handoff notes. | Depends on customer HubSpot account and vendor terms | Optional integration | Active only when configured for a customer workflow and validated for that workspace. |
| Slack | Notifications | Internal alerts or workflow notifications when SLACK_WEBHOOK_URL is configured | Limited notification payloads, lead routing summaries, and operational alerts. | Depends on Slack workspace and vendor terms | Optional integration | Notification payloads should avoid raw lead messages and sensitive details where possible. |
| Google Calendar / Google Sheets | Productivity integrations | Calendar/sheets readiness where configured | Scheduling metadata, spreadsheet rows, and workflow fields selected by the customer implementation. | Depends on Google Workspace account and vendor terms | Optional/readiness path unless surfaced in UI | Validate OAuth scopes, active UI behavior, and customer configuration before treating as live. |
| Sentry | Error monitoring | Error capture and operational diagnostics | Error traces, request metadata, stack context, and diagnostic information filtered to avoid raw PII. | Depends on Sentry project settings and vendor terms | Optional/observability, if configured | Filter sensitive values and avoid attaching customer payloads to diagnostic events. |
| Amplitude | Product analytics | GDPR-safe product analytics, page views, funnel analytics | Product events, page views, funnel events, pseudonymous identifiers, and analytics metadata where configured. | EU data region used by server analytics where configured; verify client and project settings | Optional/product analytics, if configured | Keep analytics events aggregated or pseudonymous and avoid raw lead content. |
| UptimeRobot | Uptime monitoring | Public uptime checks and status visibility | Public URL availability, response status, and response timing for monitored endpoints. | External monitoring provider | External monitoring provider | Health and status endpoints should not expose customer records, secrets, or provider payloads. |
| AWS SES | Transactional email | Transactional email if SMTP variables are configured | Recipient email addresses, delivery metadata, and transactional message content required for sending. | Depends on SES selected region, verified sending identity, and customer configuration | Optional/readiness path | Confirm production access, bounce handling, and complaint monitoring before production sending. |
Change notification
Customers may review this page for subprocessor changes. AgentFlow Enterprise does not promise a specific notice period on this page unless a signed agreement or separate legal terms state one.
Transparency notice
This page is for transparency and vendor review. It is not a certification or legal opinion.