Public Evidence Packet
Microsoft - Privacy Statement
Privacy Statement
322d5b66-a58e-485c-a367-487528a80f44- Screening date
- 23 Sept 2026, 17:17 UTC
- Jurisdiction
- Global
- Risk screening
- Medium · 4/10
- Score trace
- -3 points from previous 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
- 23 Sept 2026, 17:17 UTC
- Sanitized channel
direct- Data status
- Available
- Public snapshot evidence
- Available
Public snapshot fingerprints
0d69136f4c89eac5a2a6b57f1c5f81fb68e1acc289f939d66e158406f74ab54eCaptured 01 Aug 2026, 04:33 UTC9e926972399f575385a7e5ce858a241e040cf216702544060ac870cb4b135c24Captured 23 Sept 2026, 17:17 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 Microsoft Privacy Statement expands data collection for device usage and reduces transparency on marketing data use, raising privacy concerns.
- Reason 1-1 score contribution
Expanded data collection for device and usage data.
- Related KPI
- Data collection
- Source side
- new snapshot
Verified exact source passage
“Data about your device and product features you use, hardware and software details, product performance, your interactions with our websites and apps, and your settings.”
- Reason 2-1 score contribution
Reduced marketing transparency due to truncated section.
- Related KPI
- Algorithmic transparency
- Source side
- new snapshot
Verified exact source passage
“Marketing, Advertising, and Pr”
- Reason 3-1 score contribution
Unclear AI training opt-out mechanism within the policy text.
- Related KPI
- AI training opt-out
- Source side
- new snapshot
Verified exact source passage
“As part of our efforts to improve and develop our products, we may use your data to develop and train our AI models. Learn more here.”
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?
- AI training opt-out
- Not Available
- 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
- Partial
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
- Opt-Out
- 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 JSONf3af34a0a359561dffb70cbc34e72b29178f2540b8b3ef53896e01ff5eb6c1c5Questions before reuse
- Does the original Privacy Statement source still match the recorded public snapshot version 3?
- 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?