Novo North Subprocessors
Providers used for North and its hosted Helper runtime.
Last updated: September 18, 2026
Subprocessors
Last updated: September 18, 2026
Provider details are maintained in North’s Privacy Policy.
Helper runtime
Your helper runs on Novo Agents, Novo's own hosted runtime. It processes task context, messages, files, tool interactions, and managed computer and browser activity. Its model, media, search, browser, and infrastructure providers are identified in the Novo Agents subprocessors disclosure, incorporated into this notice. Not every task uses every provider. Provider retention and training restrictions depend on the applicable service terms and configuration; this notice does not promise that all providers retain no data.
North service providers
| Provider | Information and purpose |
|---|---|
| Google (Vertex AI) | Workspace content and search queries for content analysis, enrichment, embeddings, retrieval, and meeting recaps. |
| ElevenLabs | Uploaded audio and video content for transcription during file processing. Helper media generation is covered by the Novo Agents disclosure. |
| AssemblyAI or Deepgram | Meeting audio sent through LiveKit Inference for real-time transcription. |
| Perplexity | Workspace name and public website in onboarding searches. |
| Fireworks AI | Public website text and search results for onboarding drafts; the first task message for generating a task title. |
| Vercel | Requests, application data, and execution state for hosting, durable workflows, isolated code execution, and AI Gateway routing of Workflow checks. |
| TypeSafe AI (through Vercel AI Gateway) | Workflow-selected text or JSON evidence, questions, and evaluation criteria for condition checks, choices, and scores. |
| Supabase | Account and workspace records, content, and files for database and storage services. |
| WorkOS | Sign-in identity, authentication events, and session state for authentication and account access. |
| Merge | Connected-service credentials, metadata, and authorized requests and responses for integrations. |
| Google Cloud Storage | Temporary staging of larger files for Vertex AI processing; cleanup is attempted after processing. |
| LiveKit | Meeting audio/video transport, session metadata, transcription infrastructure, and webhooks. |
| Stripe | Payment, subscription, and billing information. |
| Google and Microsoft | Identity and profile information when you choose those sign-in methods. |
| ConvertAPI | Document and image content for conversion, previews, and thumbnails. |
| Reducto | Document and image content accessed through short-lived signed URLs for parsing and extraction. |
| Resend | Email addresses, message content, and delivery status for transactional communications. |
| Sentry | Errors, diagnostics, and performance traces, including selected AI input and output text for onboarding drafts and task titles. |
| PostHog | Account identifiers, email and display name, workspace metadata, usage events, feature flags, and masked session replay for product operations and diagnostics. |
Independent third-party services
Google Maps Platform receives map areas, zoom levels, coordinates, referrers, and place-search text directly from your browser when you use map-enabled apps. Google acts as an independent controller under its Controller–Controller Data Protection Terms and Privacy Policy.
Customer-directed destinations
Requested work can send information to connected accounts, custom tool services, or websites. These destinations follow their own terms and privacy practices. GitHub receives repository contents, commit metadata, and identifiers through the GitHub App integration when you use connected repositories. A connected service can receive information even when it is not listed as a North service provider.
We may also disclose information to professional advisers, in response to lawful requests, to protect people or legal rights, or in connection with a business transfer. Any successor's processing remains subject to applicable law and notice requirements.