The terms state that customer prompts submitted to and outputs generated by Amazon Bedrock are not used to train the underlying foundation models made available through the service. This applies to both first-party Amazon models and third-party models accessed through Bedrock.
This analysis describes what AWS Bedrock's agreement states, permits, or reserves. It does not constitute a legal determination about enforceability. Regulatory applicability and practical outcomes may vary by jurisdiction, enforcement context, and individual circumstances. Read our methodology
This provision addresses a material concern for enterprise customers deploying proprietary data in AI workflows; the agreement states that customer content processed through Bedrock does not contribute to foundation model training, which is operationally significant for customers with confidentiality obligations around their data.
Interpretive note: The full scope of this provision as it applies to all model types available through Bedrock and the distinction between model training and service improvement uses requires review of the complete untruncated document.
The updated terms remove the explicit reference to a Data Processing Addendum governing Anthropic data transfers, though the requirement to obtain opt-in consent for Anthropic model use remains in place. For Kiro users, the revised language now explicitly states that abuse detection includes retention and potential human review of inputs and outputs when selecting certain models. Users of Anthropic models on Bedrock should verify opt-in consent mechanisms in service documentation to understand data handling practices.
View change record →The updated terms establish a new project-based service structure for AWS (new) users, effective August 17, 2026, with new rules governing team member access and content ownership. Users who enable spend limits agree that AWS may suspend their account or project access upon reaching their limit, and may permanently close the account or project if not reactivated within an unspecified timeframe. Contributed content by team members becomes the project owner's property and is subject to a nonexclusive irrevocable license granted to all project members. You can configure AI services opt-out policies through AWS Settings; project owners can manage team member permissions and access controls.
View change record →The updated terms now explicitly state that AWS IoT SiteWise Scenario Discovery is not designed for real-time vehicle control and cannot be used as the sole basis for determining vehicle safety or regulatory compliance. Organizations deploying this service must implement independent human monitoring and safety validation before using its outputs to support vehicle system decisions. The terms make clear that AWS assumes no responsibility for uses that violate these constraints.
View change record →Under this clause, inputs and outputs processed through Amazon Bedrock are not used to improve or retrain the foundation models available in the service. This is a contractual commitment regarding the use of customer content in model development.
How other platforms handle this
You can contact us in order to (1) update or correct your personally identifiable information, (2) change your preferences with respect to communications and other information you receive from us, or (3) delete the personally identifiable information maintained about you...
Your Profile will not publicly include or link to Your Content submitted semi-/anonymously to our services.
If you choose to reveal any personal information about yourself to other users, you do so at your own risk. We strongly encourage you to use caution in disclosing any personal information online.
"Amazon Bedrock does not use your inputs or outputs to train the underlying models available in Amazon Bedrock.Excerpt from AWS Bedrock's AWS Service Terms
(1) REGULATORY LANDSCAPE: This provision is relevant to GDPR data minimization and purpose limitation principles where customer prompts contain personal data; the stated restriction on training use supports a narrower processing purpose claim.
Enforcement risk, jurisdiction flags, contract triggers, and due diligence action items.
Ad personalization controls removed. Contact scanning added. Advertiser data partnerships quietly dropped. A timeline of every change.
Get the research letter
Companies change their terms quietly. We read every version and catch what actually changed. One email a week on the changes that matter and what they mean.
This provision addresses a material concern for enterprise customers deploying proprietary data in AI workflows; the agreement states that customer content processed through Bedrock does not contribute to foundation model training, which is operationally significant for customers with confidentiality obligations around their data.
Under this clause, inputs and outputs processed through Amazon Bedrock are not used to improve or retrain the foundation models available in the service. This is a contractual commitment regarding the use of customer content in model development.
ConductAtlas has identified this type of provision across 289 platforms. See the full comparison.
No. ConductAtlas is an independent monitoring service. We are not affiliated with, endorsed by, or sponsored by AWS Bedrock.