Public Evidence Packet
Amazon - AWS Customer Agreement
AWS Customer Agreement
5a7ffcf2-bee3-4d3c-9e4f-6162558fe211- Screening date
- 31 Oct 2026, 03:56 UTC
- Jurisdiction
- Global
- Risk screening
- Medium · 6/10
- Score trace
- Baseline; no earlier public change
This packet records PolicyWatcher evidence and AI-assisted screening for one public change. It is not legal advice, a compliance verdict, a certification, or proof that the external source remains unchanged.
- 01Source evidence
- 02Explainability
- 03Governance Relevance
- 04Report Output
Dataset QA · sanitized public view
Source evidence
- Publication gate
- Published
- Retrieval state
- Recorded retrieval available
- Latest retrieval
- 31 Oct 2026, 03:56 UTC
- Sanitized channel
direct- Data status
- Available
- Public snapshot evidence
- Available
Public snapshot fingerprints
67ad5f05c29aba9eac158d2fe0b446bb0e73c670b84c71ffeedc0cc18263ff2eCaptured 02 Oct 2026, 04:54 UTCd614cdbda964cb1cd0513eede34725cdb87657bbead7157a3333bf1bc1f0962cCaptured 31 Oct 2026, 03:56 UTCSource confidence describes recorded retrieval and publication state. It does not rate the provider policy or certify source authenticity.
Source-anchored screening trace
Explainability
The updated AWS agreement clarifies payment terms, requiring timely invoice payment and authorizing automatic charges to your default payment method.
- Reason 1-1 score contribution
Explicit authorization to charge default payment method.
- Related KPI
- Regulatory compliance
- Source side
- new snapshot
Verified exact source passage
“you authorize us to charge your default payment method for the invoiced amount.”
- Reason 2-1 score contribution
New mandatory payment of invoices by due date.
- Related KPI
- Regulatory compliance
- Source side
- new snapshot
Verified exact source passage
“You must pay all invoices by the due date set forth on the invoice”
- Reason 3-1 score contribution
Increased clarity on AWS's payment enforcement mechanisms.
- Related KPI
- Regulatory compliance
- Source side
- Not recorded
Source passage not recordedThis historical reason has no recorded source passage.
Score reasons and deltaScore values are stored AI-assisted screening outputs. Verified anchors confirm only that the quoted passage occurs in the named snapshot; they do not prove the interpretation.
Advisory review map
Governance Relevance
EU AI Act
Official Journal text, 2024
Which recorded policy statements may be relevant to transparency, automated decisions, data use and human oversight review?
- Algorithmic transparency
- Opaque
- Automated decisions
- Opaque
- AI bias and fairness
- Absent
ISO/IEC 42001
ISO/IEC 42001:2023 overview
Which recorded policy statements may inform an AI management-system review of transparency, risk oversight and independent assurance?
- Algorithmic transparency
- Opaque
- AI bias and fairness
- Absent
- Independent audit
- Absent
- Regulatory compliance
- Partial
NIST AI RMF
AI RMF 1.0; NIST revision in progress, checked 2026-07-29
Which recorded policy statements may support Govern, Map, Measure or Manage review questions?
- Algorithmic transparency
- Opaque
- Automated decisions
- Opaque
- AI bias and fairness
- Absent
- Content moderation
- Opaque
OECD AI Principles
OECD AI Principles, updated 2024
Which recorded policy statements may be relevant to transparency, fairness, accountability and user agency review?
- Consent mechanism
- Implicit
- Algorithmic transparency
- Opaque
- AI bias and fairness
- Absent
- Independent audit
- Absent
Mappings identify review relevance between recorded PolicyWatcher KPI fields and framework topics. They are not legal interpretations, conformity assessments, certifications or compliance verdicts.
Exact change-bound files
Report Output
Both files are generated from this exact change ID.
Download exact-change PDF Download exact-change JSON6bfdc00e38241d7e34401b15ea7577a86e0180536a229a4736e16eb9263e1f73Questions before reuse
- Does the original AWS Customer Agreement source still match the recorded public snapshot version 2?
- Do the cited source passages support each displayed reason, KPI value and regional note?
- Which advisory framework topics require specialist legal, risk or governance review for this use case?
- Has a later public change superseded this packet before it is reused in a decision or publication?