When you use an AI model from a company other than Amazon through Bedrock, your data may be sent to that company and governed by their separate rules, not just AWS's rules.
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
The clause creates a bifurcated governance structure in which data processing for third-party models falls outside AWS's direct control and contractual scope, requiring users to separately evaluate and comply with each model provider's distinct terms, privacy policies, and data handling practices.
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 →Using third-party foundation models through Bedrock means your prompts, documents, and outputs may leave AWS's direct control and become subject to terms you have not directly negotiated, which could affect your data protection, confidentiality, and compliance posture.
How other platforms handle this
We share Personal Data with vendors, service providers, and agents who work on our behalf and provide us with services related to the purposes described in this Privacy Policy or our Terms of Service.
we may use, retain or share information with law enforcement or others in circumstances where a person's vital interests require protection, such as in the case of emergencies.
Third-party apps use data from Gemini consistent with their own privacy policies and terms.
"If you use a third-party model, your inputs and outputs may be processed by the third-party model provider, and such processing will be subject to that provider's terms and conditions.Excerpt from AWS Bedrock's AWS Service Terms
REGULATORY LANDSCAPE: This provision directly engages GDPR Article 28 on sub-processor relationships and the obligation for data controllers to ensure sub-processors provide sufficient guarantees.
Enforcement risk, jurisdiction flags, contract triggers, and due diligence action items.
ConductAtlas detected a major restructuring of Meta’s privacy policy that removed detailed consumer rights disclosures and relocated them to separate documents.
Your genetic data may be transferred to a new owner as a business asset. Here is what the Terms of Service actually say and what you can do right now.
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.
The clause creates a bifurcated governance structure in which data processing for third-party models falls outside AWS's direct control and contractual scope, requiring users to separately evaluate and comply with each model provider's distinct terms, privacy policies, and data handling practices.
Using third-party foundation models through Bedrock means your prompts, documents, and outputs may leave AWS's direct control and become subject to terms you have not directly negotiated, which could affect your data protection, confidentiality, and compliance posture.
ConductAtlas has identified this type of provision across 287 platforms. See the full comparison.
No. ConductAtlas is an independent monitoring service. We are not affiliated with, endorsed by, or sponsored by AWS Bedrock.