Snapshot 74807
Normalized text
Scripts and page chrome removed; this is what change detection compares.
The vendors Town relies on to process and support customer data. This page lists the vendors that likely process customer or end-user data on our behalf, including core platform subprocessors and feature-specific subprocessors used only in certain flows. Last updated: August 24, 2026 Public vendor list How we organize this list. We separate the vendors we rely on for the core product from those only used in specific feature paths, so the page stays useful for both procurement reviews and customer due diligence. Likely subprocessors Vendors that support the normal hosted Town product and are likely to process data during standard service delivery. Conditional subprocessors Vendors used only for specific AI, voice, sandbox, messaging, or integration capabilities when those features are enabled. Separate from customer integrations Customer-directed integrations such as Slack, GitHub, Notion, Linear, HubSpot, Dropbox, and Asana are generally documented separately from this list. Likely subprocessors. These vendors support the normal hosted Town product and are likely to process data during standard service delivery. Convex Likely Application backend, database, file storage, and realtime sync. Vercel Likely Website hosting, content delivery, and supporting storage services. Sentry Likely Application monitoring, error reporting, and replay diagnostics. Statsig Likely Product analytics, experimentation, and feature flag delivery. Anthropic Likely Large language model processing for assistant and routine features. Resend Likely Transactional email delivery and inbound email processing. SendGrid Likely Fallback transactional email delivery. Apple Likely Push notification delivery through Apple Push Notification service. Axiom Likely Operational log ingestion, storage, and observability analysis. Conditional subprocessors. These vendors are used only for particular AI, voice, sandbox, messaging, or integration capabilities when those features are enabled. OpenAI Conditional Model inference for selected AI features and provider routing. Used when specific model paths or routing rules select OpenAI. OpenRouter Conditional Model routing and inference for supported LLM requests. Used only when configured model routes send traffic through OpenRouter. Amazon Web Services (Bedrock) Conditional Managed AI model hosting for supported Bedrock-backed requests. Applies when Town uses Bedrock-backed model paths. ElevenLabs Conditional Speech synthesis and related voice generation routines. Applies when audio generation features are used. Reducto Conditional Document parsing and structured file extraction. Applies when document parsing or form-fill flows are used. Vapi Conditional AI phone calls, call orchestration, and call transcript processing. Applies when voice calling features are enabled. Meta (WhatsApp Cloud API) Conditional WhatsApp message delivery, receipt handling, and channel operations. Applies only to customers using the WhatsApp channel. Telegram Conditional Telegram bot messaging, media transfer, and channel operations. Applies only to customers using the Telegram channel. Linq Conditional iMessage and text message delivery for the texting channel. Applies only to customers using the texting channel. Pipedream Conditional OAuth credential management and API request execution for Pipedream-backed integrations. Applies when a user connects a Pipedream-backed integration (e.g. Jira, Salesforce, Zoom, Calendly). E2B Conditional Sandboxed code execution for supported routine automation features. Applies when sandbox-backed routine execution is used. Notes. We may update this page as our infrastructure evolves, as vendors are added or removed, or as optional features become generally available. This page focuses on vendors acting on Town's behalf. Customer- directed product integrations are typically described separately from the subprocessor list. Questions about vendors or privacy? If your organization needs more detail on a listed vendor or our data handling practices, we'd love to help. Contact us