Legal

Subprocessors

Last updated: July 31, 2026

Clad Labs, Inc. uses the following subprocessors and service providers to help deliver, host, support, and improve the Clad Services. Some are engaged only when a customer enables the relevant integration, and we disclose only the information each provider reasonably needs to perform its function.

This list is updated as our product evolves. Where required by law or contract, we provide notice of material changes.

Current subprocessors

Provider
Purpose
Categories of data
Supabase
Managed database, authentication, and file storage infrastructure
Customer workspace data, account data, authentication data, attachments, application data, metadata
Railway
Backend application hosting
All application data processed by the Clad backend in transit and in memory
Vercel
Web application and help center hosting, including custom help-center domains
Web traffic data, help center content, request metadata
OpenAI
AI models powering triage, drafting, investigation, and knowledge-base search (including hosted vector stores for knowledge retrieval)
Prompts, message content, ticket content, knowledge base content, metadata, related context submitted for AI processing
Anthropic
AI models powering triage, drafting, investigation, and automation
Prompts, message content, ticket content, knowledge base content, metadata, related context submitted for AI processing
Modal
Isolated, ephemeral sandboxes for AI-driven issue investigation and knowledge-base generation
Repository contents and investigation context for customer-connected code repositories, during the lifetime of a sandbox
Resend
Transactional and support email delivery and inbound email processing
Email content and metadata, notification content, recipient email addresses, delivery metadata
Google
Customer-enabled integrations such as Gmail and Google Calendar, OAuth, and Cloud Pub/Sub delivery of email notifications
Email content and metadata, calendar data, authentication and integration metadata
Recall.ai
Meeting notetaker infrastructure for the Clad Notetaker (customer-enabled)
Meeting recordings, transcripts, participant metadata
Firecrawl
Website crawling for customer-initiated knowledge base imports
Publicly accessible content of URLs the customer submits for import
PostHog
Product analytics and usage analytics
Usage events, account/workspace metadata, device/browser metadata, limited diagnostic data
Slack
Customer-enabled messaging integration
Messages, threads, channel metadata, user identifiers, integration metadata
Telegram
Optional customer-enabled messaging integration
Message content, user identifiers, metadata, integration data

We may also engage hosting and infrastructure vendors, security and fraud-prevention vendors, customer support and communication vendors, and professional advisors — each subject to confidentiality obligations.

Questions

If you have questions about our subprocessors, contact support@useclad.ai.