Town Assistant
Sign Up

The AI model providers Town relies on and how we protect your data.

Town uses third-party AI model providers to deliver product features. Town configures these providers so customer inputs and outputs are not used to train third-party foundation models.

Last updated: May 2026

How we handle AI provider data use.

Town uses AI model providers through their APIs. We configure each provider and routing layer so customer inputs and outputs are not used to train third-party foundation models, unless a customer explicitly enables or instructs that use.

No training on your data

Town's agreements with AI model providers contractually prohibit them from using customer inputs or outputs for model training.

Conditional providers

Some providers are used only when specific features are enabled. Conditional providers are clearly marked below.

Verified opt-out

Town has verified opt-out or no-training status with each provider through dashboard settings, contractual terms, or API configuration.

AI model providers.

The following AI model providers may process customer data when delivering Town's product features. Each provider's acceptable use policy is linked where available.

Anthropic

Core

Large language model processing for assistant and routine features. Primary model provider.

OpenAI

Conditional

Model inference for selected AI features and provider routing. Used when specific model paths or routing rules select OpenAI.

Amazon Web Services (Bedrock)

Conditional

Managed AI model hosting for supported Bedrock-backed requests. Applies when Town uses Bedrock-backed model paths.

OpenRouter

Conditional

Model routing and inference for supported LLM requests. Used only when configured model routes send traffic through OpenRouter.

ElevenLabs

Conditional

Speech synthesis and voice generation. 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.

E2B

Conditional

Sandboxed code execution for routine automation features. Applies when sandbox-backed execution is used.

Routing and conditional providers.

Some providers may be configured as fallback or conditional routes. Where Town uses routing layers, Town applies provider-selection controls intended to route customer data only to providers whose data-use commitments align with Town's no-training statement.

Acceptable use.

Customers may not use Town or its AI features for illegal activity, security abuse, privacy violations, deceptive impersonation, child safety violations, regulated or high-risk decisions without appropriate oversight, harmful content generation, or misuse of voice, likeness, or identity rights. Provider-specific acceptable use policies may also apply, as linked above.

Scope.

This page covers AI model providers. Ordinary backend subprocessors are listed separately on Town's subprocessor page. Customer-connected third-party integrations are governed by the customer's relationship with those third-party services and those services' own terms.