Seven listed AI providers may process customer data
The page lists seven providers that 'may process customer data when delivering Town's product features': Anthropic, OpenAI, Amazon Web Services (Bedrock), Google (Gemini), Gemini Enterprise Agent Platform, OpenRouter and ElevenLabs. The word 'may' is the page's own: it lists possible processors, and the entries that follow tie several of them to particular features or routes. Each provider's acceptable use policy is said to be linked where available.
Supporting quotations
AI model providers.
The following AI model providers may process customer data when delivering Town's product features.
Anthropic
OpenAI
Amazon Web Services (Bedrock)
Google (Gemini)
Gemini Enterprise Agent Platform
OpenRouter
ElevenLabs
Qualifications & exceptions
The providers 'may' process customer data; they are not all stated to process it for every customer or feature.
Applies when delivering Town's product features.
Not stated here
The page does not say which data goes to which provider, how long a provider keeps it, or where it is processed.
Routing layers apply controls intended to send data only to aligned providers
Town says some providers may be configured as fallback or conditional routes, and that where it uses routing layers it applies provider-selection controls 'intended to route customer data only to providers whose data-use commitments align with Town's no-training statement'. The page words this as an intention, not as a guarantee, and does not describe the controls.
Supporting quotations
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.
Qualifications & exceptions
Applies where Town uses routing layers.
The controls are 'intended to' route data to aligned providers.
Some providers may be fallback or conditional routes.
Not stated here
The page does not describe the controls or say how a provider's commitments are judged to 'align'.
The page does not say what happens if a fallback provider's commitments do not align.
Cross-references
contrast (model-proposed): Town configures providers so inputs and outputs do not train third-party foundation models — The configuration sentence says Town configures each provider and routing layer so inputs and outputs are not used for training; the routing sentence says provider-selection controls are 'intended to' send data only to aligned providers. One is worded as a configuration, the other as an intention; the page does not say how they fit together.
Sharing & Disclosure · Context
This page covers AI model providers; backend subprocessors are listed elsewhere
The page says it covers AI model providers only, and that ordinary backend subprocessors are listed separately on Town's subprocessor page. That page was not supplied and is not described here.
Supporting quotations
Scope.
This page covers AI model providers.
Ordinary backend subprocessors are listed separately on Town's
Qualifications & exceptions
Limited to AI model providers.
Covers 'ordinary backend subprocessors' only as a pointer to a separate page.
Not stated here
The subprocessor page was not supplied.
'Ordinary backend subprocessors' is not defined, and the page does not say what they do with customer data.
Customer-connected integrations are governed by the customer's relationship with those services
The page says customer-connected third-party integrations are governed by the customer's relationship with those third-party services and by those services' own terms. This sentence sits in the page's scope section, after the statement that the page covers AI model providers.
Supporting quotations
Customer-connected third-party integrations are governed by the customer's relationship with those third-party services and those services' own terms.
Qualifications & exceptions
Applies to integrations the customer connects.
Not stated here
The page does not list integrations or say what Town sends to them.
The third-party services' terms were not supplied.