Last updated: 14 January 2026
This page lists third-party service providers (“subprocessors”) that may process customer personal data to help Zeta AI provide Viktor.
A subprocessor is a third party that processes customer personal data on behalf of Zeta AI (as a processor) to provide the Service (e.g., infrastructure, logging, billing, customer support, analytics, automation, and integrations).
We aim to:
We will update this page when we add or replace subprocessors.
If you want to be notified of updates or raise an objection (where applicable under your DPA), contact [email protected].
| Subprocessor | Service / Purpose | Data Potentially Processed |
|---|---|---|
| Slack | Core platform integration (OAuth, messaging, app functionality) | Slack messages and metadata in channels/DMs where Viktor is used |
| AWS (Amazon Web Services) | Hosting / storage / infrastructure | Service data, logs, stored workspace context (as configured) |
| Cloudflare | CDN, DDoS protection, edge security | Network metadata, request logs, caching as applicable |
| Modal | Compute / job execution (as applicable) | Task inputs/outputs needed for compute workloads |
| Stripe | Payments and billing (future paid plans) | Billing contact info, transaction metadata (payment details handled by Stripe) |
| Google (Gmail/Drive/Calendar/Sheets/Docs) | Integrations (if enabled by customer) | Data accessed via integration scopes authorized by customer |
| Microsoft (Outlook/OneDrive) | Integrations (if enabled by customer) | Data accessed via integration scopes authorized by customer |
| HubSpot | CRM integration (if enabled by customer) | CRM records and metadata authorized by customer |
| Meta Ads | Ads integration (if enabled by customer) | Ads account and reporting data authorized by customer |
| Google Ads | Ads integration (if enabled by customer) | Ads account and reporting data authorized by customer |
| QuickBooks | Finance/accounting integration (if enabled by customer) | Accounting records authorized by customer |
| Intercom | Customer support tools (if used) | Support communications, identifiers, troubleshooting content |
| Notion | Workspace/document integration (if enabled by customer) | Notion content authorized by customer |
| Customer.io | Customer messaging/notifications (if used) | Contact details and messaging events (as configured) |
| Moz | SEO tooling/integration (if enabled) | SEO-related data authorized by customer |
| Baremetrics | Metrics/analytics (business performance) | Subscription/usage metrics (typically aggregated) |
| PostHog | Product analytics (if enabled) | Usage events and identifiers (as configured) |
| LangSmith | LLM observability/tracing (if used) | Prompts/outputs and metadata as configured (may include customer content) |
| Axiom | Logging/observability | Logs and event data (may include identifiers and technical metadata) |
| Browserbase | Browser automation | Content accessed during automated browsing tasks (as configured) |
| BrightData | Web data access/proxying (if used) | Data involved in web research tasks (as configured) |
Viktor may use third-party AI processing providers to generate outputs (summaries, drafts, recommendations). The specific providers may vary depending on configuration and availability. Where used, these providers process customer content strictly to provide the Service and under contractual restrictions.
If you want the exact current AI providers listed explicitly in this table (instead of this general section), tell me which ones you use in production today and I’ll format them cleanly.
Questions or requests related to subprocessors: [email protected]