Town configures providers so inputs and outputs do not train third-party foundation models
Town says it configures each provider and routing layer so that customer inputs and outputs are not used to train third-party foundation models. The fuller statement adds an exception: 'unless a customer explicitly enables or instructs that use'. The introductory paragraph states the commitment without that exception, so the exception belongs with the commitment. The statement is about training third-party foundation models; the page does not address Town's own models.
Supporting quotations
Town configures these providers so customer inputs and outputs are not used to train third-party foundation models.
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.
Qualifications & exceptions
Limited to training third-party foundation models.
Unless a customer explicitly enables or instructs that use.
Applies to each provider and routing layer that Town configures.
Not stated here
The page does not say whether Town trains or tunes its own models on customer inputs or outputs.
'Customer inputs and outputs' is not defined.
The page does not address other uses by providers, such as retention, human review or abuse monitoring.
Cross-references
contrast (model-proposed): Routing layers apply controls intended to send data only to aligned providers — 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.
has exception (model-proposed): A customer's explicit enablement or instruction lifts the no-training setup — The no-training configuration applies 'unless a customer explicitly enables or instructs that use'; the exception sits in the same sentence as the general rule, while the introductory paragraph states the rule without it.
A customer's explicit enablement or instruction lifts the no-training setup
The no-training configuration does not apply where a customer explicitly enables or instructs the use of their inputs and outputs for training. The page does not describe how a customer would do that.
Supporting quotations
unless a customer explicitly enables or instructs that use
Qualifications & exceptions
The customer must explicitly enable or instruct the use.
Not stated here
The page does not say how a customer enables or instructs training use, whether this is per account or per feature, or who counts as the customer.
Town's provider agreements prohibit training on customer inputs or outputs
Under a 'No training on your data' heading, Town says its agreements with AI model providers contractually prohibit those providers from using customer inputs or outputs for model training. The sentence speaks of model training only and states no exceptions.
Supporting quotations
No training on your data
Town's agreements with AI model providers contractually prohibit them from using customer inputs or outputs for model training.
Qualifications & exceptions
Covers use of customer inputs or outputs for model training, not other uses.
Not stated here
The page does not say which providers' agreements contain the prohibition or publish the contract terms.
The page does not address provider uses other than model training.
Cross-references
contrast (model-proposed): Town says it verified no-training status with each provider — One sentence says Town's agreements with providers contractually prohibit training; the verification sentence says no-training status was verified through dashboard settings, contractual terms, or API configuration, so for a given provider the basis may be a setting rather than a contract. The page does not reconcile the two or say which providers rely on which.
Inference & Profiling · Company practice
Town says it verified no-training status with each provider
Town says it has verified opt-out or no-training status with each provider through dashboard settings, contractual terms, or API configuration. Because the means are listed as alternatives, a given provider's status may rest on a setting or API configuration rather than on a contract. The broader sentence about provider agreements speaks of contractual prohibitions; the two statements describe the basis for no-training differently.
Supporting quotations
Verified opt-out
Town has verified opt-out or no-training status with each provider through dashboard settings, contractual terms, or API configuration.
Qualifications & exceptions
Verified 'with each provider'.
Through dashboard settings, contractual terms, or API configuration.
Not stated here
The page does not say when verification happened, how often it is repeated, or which provider relies on which method.
No verification evidence is published on this page.
Cross-references
contrast (model-proposed): Town's provider agreements prohibit training on customer inputs or outputs — One sentence says Town's agreements with providers contractually prohibit training; the verification sentence says no-training status was verified through dashboard settings, contractual terms, or API configuration, so for a given provider the basis may be a setting rather than a contract. The page does not reconcile the two or say which providers rely on which.