PolicyWatcherPublic evidence laboratory

Public Evidence Packet

PayPal - Privacy Statement

Privacy Statement

858f0ed6-c3a6-4084-a5eb-e7ff9ba238e6
Screening date
07 Jul 2026, 02:33 UTC
Jurisdiction
EU
Risk screening
High · 8/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.

  1. 01Source evidence
  2. 02Explainability
  3. 03Governance Relevance
  4. 04Report Output
01

Dataset QA · sanitized public view

Source evidence

Publication gate
Published
Retrieval state
Recorded retrieval available
Latest retrieval
04 Nov 2026, 18:40 UTC
Sanitized channel
direct
Data status
Available
Public snapshot evidence
Available

Public snapshot fingerprints

Previous · version 1320239c1eb5644bef52632ccf2177de89fd5c2d82de78bab34f0b8c193a41ec7Captured 06 Jul 2026, 07:20 UTC
Current · version 2168f01646ad727bfb22632a07b38d4213b1e7ace135386ba18deefa502a85984Captured 07 Jul 2026, 02:33 UTC

Source confidence describes recorded retrieval and publication state. It does not rate the provider policy or certify source authenticity.

02

Source-anchored screening trace

Explainability

No changes were found in the PayPal Privacy Statement; it outlines extensive data collection, AI training, and broad sharing, raising significant privacy considerations.

  1. Reason 1+2 score contribution

    Extensive collection of sensitive and biometric data.

    Related KPI
    No related KPI recorded
    Source side
    Not recorded
    Source passage not recorded

    This historical reason has no recorded source passage.

  2. Reason 2+2 score contribution

    Personal data used for AI training and automated decisions.

    Related KPI
    No related KPI recorded
    Source side
    Not recorded
    Source passage not recorded

    This historical reason has no recorded source passage.

  3. Reason 3+1 score contribution

    Broad data sharing with many third parties and authorities.

    Related KPI
    No related KPI recorded
    Source side
    Not recorded
    Source passage not recorded

    This 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.

03

Advisory review map

Governance Relevance

EU AI Act

Official Journal text, 2024

Mapped evidence

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
Framework source

ISO/IEC 42001

ISO/IEC 42001:2023 overview

Mapped evidence

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
Framework source

NIST AI RMF

AI RMF 1.0; NIST revision in progress, checked 2026-07-29

Mapped evidence

Which recorded policy statements may support Govern, Map, Measure or Manage review questions?

Algorithmic transparency
Opaque
Automated decisions
Opaque
AI bias and fairness
Absent
Framework source

OECD AI Principles

OECD AI Principles, updated 2024

Mapped evidence

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
Framework source

Mappings identify review relevance between recorded PolicyWatcher KPI fields and framework topics. They are not legal interpretations, conformity assessments, certifications or compliance verdicts.

04

Exact change-bound files

Report Output

Both files are generated from this exact change ID.

Download exact-change PDF Download exact-change JSON
Packet content digest · SHA-256df6bfa2c8cc428fb1cff645c4df0ca09b9e63857e83214751a4038515c7008cb

Questions before reuse

  1. Does the original Privacy Statement source still match the recorded public snapshot version 2?
  2. Do the cited source passages support each displayed reason, KPI value and regional note?
  3. Which advisory framework topics require specialist legal, risk or governance review for this use case?
  4. Has a later public change superseded this packet before it is reused in a decision or publication?