Subprocessors
Victoria AI: All Products and Services
Last updated: October 2, 2026
These are the providers that process customer data on our behalf to deliver Victoria, Pulse, this site, and our managed services, as described in our Data Processing Addendum. Each row links to the provider's own privacy notice.
| Provider | Function | Used by | Location | Transfer mechanism |
|---|---|---|---|---|
| Supabase | Database, authentication, and file storage | Victoria, Pulse, Site | United States | SCCs Module 2 + UK Addendum |
| Vercel | Web application hosting | Victoria, Pulse, Site | United States | SCCs Module 2 + UK Addendum |
| Railway | Backend application hosting | Victoria, Pulse | United States | SCCs Module 2 + UK Addendum |
| Anthropic | AI model processing: message drafting, reply classification, research, and Pulse enrichments | Victoria, Pulse | United States | SCCs Module 2 + UK Addendum |
| OpenAI | AI model processing: embeddings and fallback generation | Victoria | United States | SCCs Module 2 + UK Addendum |
| Unipile | Email and LinkedIn message processing and delivery from connected accounts | Victoria | France | EU internal |
| FullEnrich | Lead search and contact enrichment: Search results as an independent controller of its own database; email and phone enrichment as our processor. Serves the Lead database in Victoria on Victoria AI's own provider account, and contact enrichment for managed services. | Victoria, Managed services | United States | SCCs Module 2 + UK Addendum |
| Inngest | Background job orchestration | Pulse | United States | SCCs Module 2 + UK Addendum |
| Stripe | Payments and billingVictoria AI is the controller of billing data. | Victoria, Pulse | United States | SCCs Module 2 + UK Addendum |
| Resend | Transactional and account email delivery | Victoria | United States | SCCs Module 2 + UK Addendum |
| Slack | Internal operational notifications, which may include customer and prospect data in alerts and briefs | Victoria, Pulse, Managed services | United States | SCCs Module 2 + UK Addendum |
| Google (Google Calendar) | Scheduling integration for booked meetings | Victoria | United States | SCCs Module 2 + UK Addendum |
| Google (Google Analytics) | Site and product analyticsVictoria AI is the controller of analytics data. | Site, Victoria | United States | SCCs Module 2 + UK Addendum |
| Amplitude | Product analytics in the Victoria app (being replaced by PostHog)Victoria AI is the controller of analytics data. | Victoria | United States | SCCs Module 2 + UK Addendum |
| PostHog | Product analytics in the Victoria app and on the Site (replaces Amplitude)Victoria AI is the controller of analytics data. | Site, Victoria | United States | SCCs Module 2 + UK Addendum |
| CalendlyPlanned | Scheduling integration | Victoria | United States | SCCs Module 2 + UK Addendum |
| Calendly | Booking calendar embedded on the Site's contact pageVictoria AI is the controller of booking requests made on the Site. | Site | United States | SCCs Module 2 + UK Addendum |
| Google (Google Ads)Planned | Site advertising: ad conversion measurement and remarketingVictoria AI is the controller of advertising data; Google is an independent controller of its own use. | Site | United States | SCCs Module 2 + UK Addendum |
| Meta (Meta Pixel)Planned | Site advertising: ad conversion measurement and remarketingVictoria AI and Meta are joint controllers for collecting and sending pixel data; Meta is an independent controller of its own use afterwards. | Site | United States | SCCs Module 2 + UK Addendum |
| LinkedIn (Insight Tag)Planned | Site advertising: ad conversion measurement and remarketingVictoria AI and LinkedIn are joint controllers for collecting and sending tag data; LinkedIn is an independent controller of its own use afterwards. | Site | United States | SCCs Module 2 + UK Addendum |
"Planned" marks a provider we have approved for an integration that is not yet processing customer data. It appears here so that the notice period under DPA §4.2 has already run by the time it goes live.
Providers and assistants you connect
Contact resolution in Pulse runs on an enrichment provider account that you own and connect with your own API key. Contact data is retrieved on your credentials under your agreement with that provider, so that provider is your vendor rather than our subprocessor. Lead database searches in Victoria run on our own provider account instead (FullEnrich, listed above as planned). The providers you can connect to Pulse:
AI assistants you connect to your workspace through the API or the MCP server (for example Claude, ChatGPT, Claude Code, or any MCP host) are your vendors in the same way. They receive the workspace data you choose to expose to them, under your control and your agreement with their provider, and you can revoke the connection at any time in the app.
Get notified when this list changes
Under our DPA we update this page at least 30 days before adding or replacing a subprocessor. Leave your email and we'll send you each change as it is posted.
Questions
Data protection questions or objections under DPA §4.2: privacy@versionseven.ai.