Provision record
AWS Bedrock · AWS Service Terms · View original document ↗

RCS messaging subject to Google RCS Terms

High severity Explicit document language Common · 297 of 352 platforms
Stay ahead of the changes
Track AWS Bedrock and get the diff the day its terms change.
Share 𝕏 Share in Share 🔒 PDF
ⓘ

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

Recent Activity

This document changed recently

Medium Sep 2, 2026

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 →
High Aug 18, 2026

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 →
Medium Jul 30, 2026

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 →

How other platforms handle this

Shopify Medium

Your use of the Services is subject to your acceptance of the Google Maps and Earth Enterprise Universal Acceptable Use Policy, Google Maps and Google Earth Additional Terms of Service and Google Privacy Policy...

Pinterest Medium

To the extent that any provisions in the Business Terms of Service conflict with these Terms, the Business Terms of Service shall govern to the extent of the conflict.

Snapchat Medium

Regardless of who terminates these Terms, both you and Snap continue to be bound by Sections 2, 3 (to the extent any additional terms and conditions would, by their terms, survive), and 6 - 25 of the Terms.

See all platforms with this clause type →
▸ View Original Clause Language DOCUMENT RECORD
"
your use of the RCS messaging channel in AWS End User Messaging is subject to the Google RCS for Business Terms of Service ("Google RCS Terms"). The Google RCS Terms contain important information about use of Google RCS for Business, including how Google may use your RCS message content...

Excerpt from AWS Bedrock's AWS Service Terms

Provision details

Document information
Document
AWS Service Terms
Entity
AWS Bedrock
Date stated by the document
Oct. 1, 2026
As printed in AWS Bedrock’s text (version CA-V-007312), not a ConductAtlas date.
Tracking information
First captured by ConductAtlas
May 5, 2026
Text quoted from version
CA-V-007312, captured Oct. 2, 2026
Record ID
CA-P-052769
Document ID
CA-D-000648
Evidence Provenance
Source URL
Wayback Machine
Archived bytes SHA-256 (version CA-V-007312)
c89d642f0a5996d2873d7a916a5283f4360f2bf164522006fbdebaf5a0a00aeb
Analysis generated
July 9, 2026 09:33 UTC
Methodology
Evidence
✓ Excerpt found verbatim in version CA-V-007312 (checked Oct. 5, 2026)
Citation Record
Entity: AWS Bedrock
Document: AWS Service Terms
Record ID: CA-P-052769
Version: CA-V-007312
Captured: 2026-10-02 01:17:57 UTC
SHA-256: c89d642f0a5996d2…
URL: https://conductatlas.com/platform/aws-bedrock/aws-service-terms/provision/CA-P-052769/rcs-messaging-subject-to-google-rcs-terms/
Accessed: Oct. 8, 2026
Permanent archival reference. Stable identifier suitable for legal filings, compliance documentation, and research citation.
Classification
Severity
High
Categories

Other risks in this policy

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.

Frequently Asked Questions

What does AWS Bedrock's RCS messaging subject to Google RCS Terms clause do?

The clause states: “your use of the RCS messaging channel in AWS End User Messaging is subject to the Google RCS for Business Terms of Service ("Google RCS Terms"). The Google RCS Terms contain important information about use of Google RCS for Business, including how Google may use your RCS message content...”

How many platforms have this type of clause?

ConductAtlas has identified this type of provision across 297 platforms. See the full comparison.

Is ConductAtlas affiliated with AWS Bedrock?

No. ConductAtlas is an independent monitoring service. We are not affiliated with, endorsed by, or sponsored by AWS Bedrock.