Proton
Productivity suite · proton.me · last read 2026-11-16
Products Proton names as its own: Proton Mail for Business, Proton VPN for Business, Proton Pass for Business, Proton Drive for Business, Proton Meet for Business, Lumo AI for Business, Calendar, Docs and 1 more
At a glance
- Is Proton GDPR compliant?
- No tool is GDPR compliant on its own: compliance depends on what you process with it and how. What follows is what Proton itself publishes, each answer linked to its source and the date we read it.
- Does Proton have a data processing agreement (DPA)?
- Yes. Proton publishes a data processing agreement at proton.me. It describes how a new subprocessor is announced but states no notice period. Source and date
- Which version of the Proton DPA is current?
- On 2026-11-09, Proton's DPA at proton.me printed “Last modified: February 10, 2026”. Source and date
- Does Proton have a SOC 2 report?
- Proton states SOC 2 Type 2 on its own page, but does not say there how to get a report. We read this on 2026-10-08. Source and date
- Is Proton ISO 27001 certified?
- Proton states ISO/IEC 27001 on its own page, but does not say there how to get the certificate. We read this on 2026-10-08. Source and date
- Where is Proton's trust center?
- Proton publishes a page it calls “Trust Center” at proton.me/business/trust. Its front page shows no request or sign-in step; documents further in may still have one. The page mentions SOC 2 and ISO 27001. We read it on 2026-11-03. Source and date
- How does Proton transfer personal data out of the EU?
- Proton's agreement relies on the EU standard contractual clauses. We found no entry for Proton on the official Data Privacy Framework List. Source and date
- Who are Proton's subprocessors?
- Proton lists 11 third-party subprocessors; 5 of them name at least one processing country outside the EEA. We last read the list on 2026-10-08. Source and date
- How do you report a security vulnerability to Proton?
- Proton publishes a security.txt at proton.me naming security@proton.me. Source and date
The same questions for any vendor, and the rule behind each: the vendor due diligence checklist.
Identity
| Legal entity | Proton AG |
|---|---|
| HQ | CH |
| Parent company | — |
| Ultimate ownership | — |
| EU contracting entity | — |
| LEI | 506700YLQ614KA7PB723 |
| US CLOUD Act reach | Not determined from the sources read |
| Source | proton.me · 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
11 third parties · 2 of the vendor's own group companies · 5 with a country outside the EEA · all read 2026-10-08
| Subprocessor | Country | Purpose |
|---|---|---|
| Atlassian Pty Ltd | EU, US, GB | store data in relation with customer support |
| Calendly | — | Communications with Proton, such as support requests, bug reports, or feature requests |
| Chargebee | — | Process payments |
| Chargebee, Inc. | US | Provide services in relation with the processing of payment data |
| Hubspot, Inc. | — | Processing Sales team contact form requests from Business customers and prospects |
| PayPal group | US, SG | Provide services in relation with the processing of payment data |
| Stripe, Inc. | US | Provide services in relation with the processing of payment data |
| third parties to process credit card, PayPal, and Bitcoin transactions | — | Process credit card, PayPal, and Bitcoin transactions |
| Zendesk | — | Communications with Proton, such as support requests, bug reports, or feature requests |
| Zendesk Inc | — | Provider of Proton's live chat support platform |
| Zendesk, Inc. | US | Provide services in relation with the processing of customer support data |
Proton's own group companies listed as subprocessors (2)
| Company | Country | Purpose |
|---|---|---|
| ProtonLabs DOOEL Skopje | MK | Process data in relation with customer support requests, or other direct communications with the company |
| ProtonLabs Taiwan Co., Ltd | TW | Process data in relation with customer support requests, or other direct communications with the company |
The count outside the EEA is arithmetic over the country column, not a judgement about lawfulness. A transfer outside the EEA can be perfectly lawful; whether this one is depends on your use, not on the vendor.
Every subprocessor in the registry, and which vendors name it: subprocessors.
Processing terms
From the vendor's data processing agreement · read 2026-10-09 · proton.me
| Term | What the agreement says |
|---|---|
| Transfer mechanism | SCC (module not stated) |
| Transfer mechanism | Swiss FADP clauses |
| Transfer mechanism | other |
| Notice of new subprocessors | Subprocessor list in Privacy Policy may be updated; customer informed via the Privacy Policy notification process (no period stated) |
| Obligations passed to subprocessors | agreement with Processor no less restrictive and protective than this Agreement, to the extent applicable to the subprocessor's services |
| Breach notification | without delay |
| Deletion when the service ends | On cessation of any Service involving processing, Processor deletes all Company Personal Data to the extent permitted by applicable laws and in accordance with Processor's Terms and Conditions and Privacy Policy |
| Getting your data back | Company may request a copy of its data, but only before its account is deleted; requests made after deletion are not considered |
| Requests from data subjects | reasonably assists Company in responding to data subject requests; promptly notifies Company of requests received directly and does not respond except on Controller's documented instructions or as required by law |
| Audit | Information on request; audits/inspections by Company or its mandated auditor, max once per calendar year (except after a breach or regulator instruction), 60 days' prior written notice, during business hours, scope agreed in advance, NDA may be required |
| Processing on your instructions | only on Controller's documented instructions |
| Confidentiality of staff | individuals with access subject to confidentiality undertakings or professional or statutory obligations of confidentiality |
| Security measures | appropriate technical and organizational measures per GDPR Art. 32(1), appropriate to the risk |
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 modified: February 10, 2026
at proton.me
Last updated 2026-02-10
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
Does Proton have a SOC 2 report?
Proton states SOC 2 Type 2 on its own page, but does not say there how to get a report. We read this on 2026-10-08.
- Claimed “SOC 2 Type II verified”
Source: proton.me, 2026-10-08
Of the 114 vendors in this registry whose own pages mention SOC 2, 57 say the report is available on request, 1 links to the report itself, and 56 state it without saying how to get it. The type is the one the vendor names.
Is Proton ISO 27001 certified?
Proton states ISO/IEC 27001 on its own page, but does not say there how to get the certificate. We read this on 2026-10-08.
- Claimed “Proton is ISO 27001 certified”
Source: proton.me, 2026-10-08
Of the 122 vendors in this registry whose own pages state ISO/IEC 27001, 16 link to the certificate, 43 say it is available on request, and 63 state it without saying how to get it. A certificate names the certification body, the scope and the expiry date: those are the three things to check.
| Scheme | Status | Scope | Source | Observed |
|---|---|---|---|---|
| ISO 27001 · ISO27001 | Claimed | — | proton.me | 2026-10-08 |
| SOC 2 Type II · SOC2T2 | Claimed | — | proton.me | 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) | Proton AG · Proton AG | ISSUED | CH | 2027-01-07 | 2026-10-09 |
- ACN qualified cloud (Italy): checked 2026-11-16, no entry under Proton; Proton AG
- ISO 27001 on the basis of IT-Grundschutz (BSI, Germany): checked 2026-11-16, no entry under Proton; Proton AG
- CISPE Data Protection Code of Conduct (GDPR Art. 40): checked 2026-11-16, no entry under Proton; Proton AG
- DORA critical ICT third-party providers (ESAs): checked 2026-11-16, no entry under Proton; Proton AG
- Data Privacy Framework List (US): checked 2026-11-16, no entry under Proton; Proton AG
- ENS certificates of conformity (CCN, Spain): checked 2026-11-16, no entry under Proton; Proton AG
- EU Cloud Code of Conduct (GDPR Art. 40): checked 2026-11-16, no entry under Proton; Proton AG
- FedRAMP Marketplace (US): checked 2026-11-16, no entry under Proton; Proton AG
- GPAI Code of Practice signatories (European Commission): checked 2026-11-16, no entry under Proton; Proton AG
- SecNumCloud qualified services (ANSSI, France): checked 2026-11-16, no entry under Proton; Proton AG
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 |
|---|---|---|---|---|---|
| Proton VPN | “Only the latest stable release version of Proton VPN on each platform is actively supported” | Declared | unknown | proton.me | 2026-10-19 |
Vulnerability reporting: security@proton.me (security.txt, expires 2026-12-31; read 2026-10-17)
How other vendors publish theirs: security.txt across the registry.
Products
- Proton Mail for Business
- Proton VPN for Business
- Proton Pass for Business
- Proton Drive for Business
- Proton Meet for Business
- Lumo AI for Business
- Calendar
- Docs
- Sheets
As Proton's own list names them. Each fact on this page comes from the document cited beside it; a product named here is not necessarily covered by every one of those documents. Source: proton.me, 2026-10-29.
Documents
Where is Proton's trust center?
Proton publishes a page it calls “Trust Center” at proton.me/business/trust. Its front page shows no request or sign-in step; documents further in may still have one. The page mentions SOC 2 and ISO 27001. We read it on 2026-11-03. Open proton.me/business/trust
- Name “The Proton Trust Center is where you’ll find the essential information about our security practices, compliance, and”
Source: proton.me, 2026-11-03. Read from the page's text, without a model; every vendor's trust center.
| 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 |
| products | Public | full | 200 | 2026-10-29 |
| subprocessors | Public | full | 200 | 2026-10-08 |
| tia | Public | full | 200 | 2026-10-20 |
History
| Detected | What moved | Why | Source |
|---|---|---|---|
| 2026-10-12 | Contact set to mailto:security@proton.me Expires set to 2026-12-31T23:59:59.999Z Policy set to https://proton.me/security/bug-bounty Problems set to State none → published | the vendor changed it | proton.me |
Every reviewed change across the registry, newest first: vendor changes.