PolicyWatcherPublic evidence laboratory

Public Evidence Packet

PayPal - User Agreement

User Agreement

ab33f12c-223c-4045-89ac-0ea091eb21c3
Screening date
10 Jul 2026, 01:47 UTC
Jurisdiction
EU
Risk screening
Medium · 6/10
Score trace
+1 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.

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

Dataset QA · sanitized public view

Source evidence

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

Public snapshot fingerprints

Previous · version 23e217da9e7ae7a1db9b349adc236cadeadd301a3ed9218ab56117447e2280894Captured 07 Jul 2026, 02:34 UTC
Current · version 3dcc651853121f39a69abe965fdc1aa7b74abee98a7ce2a4a039a11821a93bea1Captured 10 Jul 2026, 01:47 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

This PayPal User Agreement outlines terms for Luxembourg residents, detailing account types, payment services, and user responsibilities, with standard financial service clauses.

  1. Reason 10 score contribution

    Account data and e-money can be held indefinitely post-closure for risk protection.

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

    This historical reason has no recorded source passage.

  2. Reason 20 score contribution

    Users are liable for actions of third parties they authorize to access their account.

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

    This historical reason has no recorded source passage.

  3. Reason 30 score contribution

    PayPal may automatically update linked card information without explicit user action.

    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

Not assessed

Which recorded policy statements may be relevant to transparency, automated decisions, data use and human oversight review?

No assessed KPI value is available for this advisory mapping.

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?

Independent audit
Absent
Regulatory compliance
Comprehensive
Framework source

NIST AI RMF

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

Not assessed

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

No assessed KPI value is available for this advisory mapping.

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
Implicit
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-256b1dc2032fa9f6d0ee34f03c4fbad37ca3b37375b03edc7339cf9be28d14d2527

Questions before reuse

  1. Does the original User Agreement source still match the recorded public snapshot version 3?
  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?