Janus / Security & Privacy
Service providers
Infrastructure and AI providers, their roles, and processing locations.
Last updated
This register identifies services supporting Janus, the information they process, and their hosting or processing scope. The customer’s agreement identifies the authorized services and applicable account arrangements.
| Service | Purpose and information | Primary location or scope |
|---|---|---|
| Vercel | Web application, server-side requests and operational processing | Washington, D.C., United States |
| Supabase | Authentication, project records, reports, generated content, embeddings and approved uploads | East US, North Virginia, United States |
| Zoom or client environment | Full source transcripts and meeting records | Location and retention follow the source account or client environment |
| Google Cloud | Meeting transcription when enabled; audio and resulting text | Iowa, United States |
| Anthropic | AI drafting, synthesis, organization and planning using relevant project text and approved content | Processing location and retention depend on the selected API account and service terms |
| OpenAI | Embeddings for finding related project information; selected source text is transmitted | Processing location and retention depend on the selected API account and service terms |
Supabase and Vercel provide encryption in transit and at rest for their hosted services. See Supabase security and Vercel security and compliance for their published encryption measures.
The listed hosting regions describe primary infrastructure. Logs, backups, support access, and downstream processing can have different locations and retention arrangements. Customer-specific residency requirements must be documented in the services agreement.
AI processing
The AI and data use overview explains drafting, embeddings, human review, and approved inputs. Source text is transmitted for processing; outputs and embeddings remain customer information.
Source accounts and the extension
The client’s own environment is not automatically a Janus subprocessor. Zoom’s role depends on account ownership. Any meeting bot, intermediary, external document host, or additional ingestion service must be identified if used for the engagement.
The optional Chrome extension uses Google sign-in and submits approved feedback and attachments to Janus. Drafts and some sign-in information may remain on the device. The providers listed above support authentication and storage; local retention and any later AI processing are covered by the agreed scope.
Provider changes
The service terms, when incorporated into the customer’s agreement, require written agreement before a new or replacement subprocessor processes client information. The approved list must identify the applicable provider entities, accounts, purposes, locations, and retention arrangements. Questions can be raised through the existing engagement contact channel.