PayPal
Payments · paypal.com · last read 2026-11-16
At a glance
- Is PayPal GDPR compliant?
- No tool is GDPR compliant on its own: compliance depends on what you process with it and how. What follows is what PayPal itself publishes, each answer linked to its source and the date we read it.
- Does PayPal have a data processing agreement (DPA)?
- Yes. PayPal publishes a data processing agreement at paypal.com. We recorded no breach-notification deadline in it. Source and date
- Which version of the PayPal DPA is current?
- On 2026-11-09, PayPal's DPA at paypal.com printed “Last updated on November 18, 2024”. Source and date
- How does PayPal transfer personal data out of the EU?
- PayPal's agreement relies on the EU standard contractual clauses and Binding Corporate Rules. We found no entry for PayPal on the official Data Privacy Framework List. Source and date
- How do you report a security vulnerability to PayPal?
- PayPal publishes a security.txt at www.paypal.com naming https://hackerone.com/paypal. The file falls short of RFC 9116: no Expires field. Source and date
The same questions for any vendor, and the rule behind each: the vendor due diligence checklist.
Identity
| Legal entity | PayPal (Europe) S.à r.l. et Cie, S.C.A. |
|---|---|
| HQ | LU |
| Parent company | PAYPAL HOLDINGS, INC. |
| Ultimate ownership | US |
| EU contracting entity | — |
| LEI | 549300ZV1RSA9F0LU821 |
| US CLOUD Act reach | Through a US parent company |
| Source | paypal.com · 2026-10-08 |
Legal entity from the vendor's own terms. LEI, registered country and parent company from the Global LEI Index (GLEIF); ownership is left empty where GLEIF names no parent. The CLOUD Act row is arithmetic over those countries, not an assessment of risk.
Data location
No data-location observation recorded yet.
The same question for every vendor: where SaaS vendors store EU data.
Subprocessor chain
Processing terms
From the vendor's data processing agreement · read 2026-10-09 · paypal.com
| Term | What the agreement says |
|---|---|
| Transfer mechanism | Binding Corporate Rules |
| Transfer mechanism | SCC module 1 |
| Transfer mechanism | other |
Terms as the agreement states them. Where it is silent on a term, there is no row; that is not a statement that the vendor does not offer it.
Which version applies
On 2026-11-09, the agreement printed: Last updated on November 18, 2024
at paypal.com
Last updated 2024-11-18
This version is in our copies from 2026-10-09.
These terms side by side for every vendor: data processing agreements compared. What vendors give you for a transfer impact assessment: transfer impact assessments.
Assurance
| Scheme | Status | Scope | Source | Observed |
|---|---|---|---|---|
| PCI · PCIDSS | Claimed | the processing, storing, and transmitting of card data for your transactions; tokenization, vault, and orchestration services | paypal.com | 2026-10-08 |
Claimed means the vendor asserts the scheme on its own page and offers nothing further. Available on request means the report or certificate exists but sits behind a request, a login or an NDA. Neither is a certificate we have seen. That is a distinction an auditor makes, so we make it too.
SecNumCloud, C5, ENS and HDS for every vendor, with the pages for ISO standards, SOC 2 and TISAX: certifications compared.
Official registers
| Register | Offering, as the register names it | Status | Level | Valid until | Observed |
|---|---|---|---|---|---|
| Global LEI Index (GLEIF) | PayPal (Europe) S.à r.l. et Cie, S.C.A. · PayPal (Europe) S.à r.l. et Cie, S.C.A. | ISSUED | LU | 2027-04-12 | 2026-10-09 |
- ACN qualified cloud (Italy): checked 2026-11-16, no entry under PayPal
- ISO 27001 on the basis of IT-Grundschutz (BSI, Germany): checked 2026-11-16, no entry under PayPal
- CISPE Data Protection Code of Conduct (GDPR Art. 40): checked 2026-11-16, no entry under PayPal
- DORA critical ICT third-party providers (ESAs): checked 2026-11-16, no entry under PayPal
- Data Privacy Framework List (US): checked 2026-11-16, no entry under PayPal
- ENS certificates of conformity (CCN, Spain): checked 2026-11-16, no entry under PayPal
- EU Cloud Code of Conduct (GDPR Art. 40): checked 2026-11-16, no entry under PayPal
- FedRAMP Marketplace (US): checked 2026-11-16, no entry under PayPal
- GPAI Code of Practice signatories (European Commission): checked 2026-11-16, no entry under PayPal
- SecNumCloud qualified services (ANSSI, France): checked 2026-11-16, no entry under PayPal
What the authority publishes, not what the vendor claims. An entry covers the offering it names and nothing else: a FedRAMP authorisation for a government edition says nothing about the commercial service. No entry is not a finding about security - most vendors never apply - and an entry filed under a name not listed above would not have been found.
What an entry on the Data Privacy Framework List covers, and which vendors hold one: EU-US Data Privacy Framework.
Support window
| Product | Support period | State | SBOM | Source | Observed |
|---|---|---|---|---|---|
| Braintree JS SDK | 12 months | Declared | unknown | developer.paypal.com | 2026-10-19 |
Vulnerability reporting: hackerone.com (security.txt, no Expires field; read 2026-10-17)
How other vendors publish theirs: security.txt across the registry.
Documents
| Document | Disclosure | Transcription | HTTP | Observed |
|---|---|---|---|---|
| certifications | Public | full | 200 | 2026-10-08 |
| dpa | Public | full | 200 | 2026-10-09 |
| lifecycle | Public | full | 200 | 2026-10-19 |
History
Nothing has moved since we started watching this vendor on 2026-10-08. Changes appear here only after a human has reviewed them.
Every reviewed change across the registry, newest first: vendor changes.