AWS will not use individualized usage data to compete

The updated terms establish a new project-based account structure for new AWS sign-ups, requiring automatic disclosure of billing and project activity to team members and granting AWS authority to suspend or permanently close accounts if spend limits are exceeded. Project owners become responsible for the conduct of invited team members and the content they contribute, which becomes the project owner's property under a nonexclusive license shared with all project members. The terms also introduce spend limit controls that allow AWS to suspend access immediately and permanently close accounts if spending thresholds are repeatedly exceeded or if AWS determines the use is fraudulent or abusive. You can configure AI services opt-out policies through AWS Settings.

The updated terms establish that when AWS Bedrock customers direct AWS to access regulated data (such as personal data, protected health information, or controlled unclassified information) in a Professional Services Order, and applicable data protection laws apply, the AWS Professional Services Supplementary Data Processing Addendum is automatically incorporated. This means customers engaging AWS professional services with regulated data now have formal data processing protections and obligations defined in the DPA, rather than relying solely on the general prohibition against disclosing regulated data. The automatic incorporation clarifies the legal framework governing how AWS processes such data.

The updated terms establish explicit restrictions on how AWS IoT SiteWise Scenario Discovery may be used. The agreement now states that this service is not designed for real-time vehicle control, transmission of operational commands to vehicles, direct vehicle system integration, or regulatory submissions. Users are prohibited from relying on data collected or curated through this service as the basis for determining vehicle safety, compliance, or fitness for deployment. AWS is not responsible for any such uses. These restrictions clarify the intended scope of the service and establish that users bear full responsibility for any safety-critical applications.