Proton
Productivity suite · proton.me · last read 2026-10-12
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.
Subprocessor chain
11 third parties · 2 of the vendor's own group companies · 7 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.
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) |
| Breach notification | without delay |
| 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 |
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.
Assurance
| 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.
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-10-12, no entry under Proton; Proton AG
- DORA critical ICT third-party providers (ESAs): checked 2026-10-12, no entry under Proton; Proton AG
- Data Privacy Framework List (US): checked 2026-10-12, no entry under Proton; Proton AG
- EU Cloud Code of Conduct (GDPR Art. 40): checked 2026-10-12, no entry under Proton; Proton AG
- FedRAMP Marketplace (US): checked 2026-10-12, no entry under Proton; Proton AG
- SecNumCloud qualified services (ANSSI, France): checked 2026-10-12, 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.
Support window
Not yet collected. This row will say not declared only once we have read a lifecycle or security page and found no period stated — see support windows.
Vulnerability reporting: [email protected] (security.txt, expires 2026-12-31; read 2026-10-12)
Documents
| Document | Disclosure | Transcription | HTTP | Observed |
|---|---|---|---|---|
| certifications | Public | full | 200 | 2026-10-08 |
| dpa | Public | full | 200 | 2026-10-09 |
| subprocessors | Public | full | 200 | 2026-10-08 |
History
| Detected | What moved | Why | Source |
|---|---|---|---|
| 2026-10-12 | Contact set to mailto:[email protected] 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 |