Element
Messaging · element.io · last read 2026-11-16
At a glance
- Is Element GDPR compliant?
- No tool is GDPR compliant on its own: compliance depends on what you process with it and how. What follows is what Element itself publishes, each answer linked to its source and the date we read it.
- Does Element have a data processing agreement (DPA)?
- Yes. Element publishes a data processing agreement at static.element.io. It describes how a new subprocessor is announced but states no notice period. It promises breach notification "without undue delay", with no number of hours. Source and date
- Which version of the Element DPA is current?
- On 2026-11-09, Element's DPA at static.element.io printed “● 2023, November 24: updates to definitions”. Source and date
- Is Element ISO 27001 certified?
- Element states ISO/IEC 27001 (2022 edition, as Element names it) on its own page, but does not say there how to get the certificate. In Element's words: “Element is independently audited and certified as compliant with the ISO/IEC 27001:2022 information security management standard.” We read this on 2026-10-08. Source and date
- How does Element transfer personal data out of the EU?
- Element's agreement relies on the EU standard contractual clauses and the UK transfer addendum. We found no entry for Element on the official Data Privacy Framework List. Source and date
- Who are Element's subprocessors?
- Element lists 6 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 Element?
- Element publishes a security.txt at element.io naming security@element.io. The file falls short of RFC 9116: expired 2025-01-30. Source and date
The same questions for any vendor, and the rule behind each: the vendor due diligence checklist.
Identity
| Legal entity | Element Creations Ltd |
|---|---|
| HQ | GB |
| Parent company | — |
| Ultimate ownership | — |
| EU contracting entity | Element Software SARL (and 1 other EU entity by country) |
| LEI | — |
| US CLOUD Act reach | Not determined from the sources read |
| Source | element.io · 2026-10-08 |
Data location
No data-location observation recorded yet.
The same question for every vendor: where SaaS vendors store EU data.
Element's subprocessor list names AWS for hosting or infrastructure. Which SaaS vendors run on which cloud, and the sovereign offerings of each: sovereign clouds.
Subprocessor chain
6 third parties · 5 with a country outside the EEA · all read 2026-10-08
| Subprocessor | Country | Purpose |
|---|---|---|
| Amazon Web Services (AWS) | US, NL, DE, GB | Infrastructure services: Cloud services and data centre services |
| Hubspot. Inc. | US | Web analytics & marketing automation |
| Posthog | US, DE | Web analytics |
| Stripe | GB | Payments Processor |
| Twillio | US | SMS Multi Factor Authentication |
| Zammad | DE | Customer service communication |
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 · static.element.io
| Term | What the agreement says |
|---|---|
| Transfer mechanism | SCC module 2 |
| Transfer mechanism | UK Addendum |
| Transfer mechanism | UK IDTA |
| Notice of new subprocessors | Prior notice of any new sub-processor, with full details of the processing (period not stated) |
| If you object to one | Customer may terminate the Agreement without liability (no-fault) if it has reasonable grounds that the change would put it in breach of data protection law; requires at least 30 days' written notice of termination |
| Obligations passed to subprocessors | Element imposes on all Sub-processors the same data protection obligations as set out in the Agreement, and remains fully liable for them |
| Breach notification | without undue delay on becoming aware |
| Deletion when the service ends | Data is deleted on termination of the Agreement, unless it is required to comply with legal requirements |
| Getting your data back | At Customer's written direction, returns personal data and copies on termination; retained documentation data must be provided to Customer on request |
| Requests from data subjects | Assists Customer with data subject requests; requests sent directly to Element are notified and forwarded to Customer immediately, and Element awaits Customer's instructions and does not contact the data subject without them |
| Audit | Audits by the Customer or its designated auditor, only as far as necessary to demonstrate compliance; at least 30 days' notice required and parties must agree the scope, duration and purpose |
| Audit | Element keeps records and allows audits by the Customer or its designated auditor, only as far as needed to demonstrate compliance; requires at least 30 days' notice and agreed scope, duration and purpose |
| Processing on your instructions | Processes personal data within the scope of the Main Contract and exclusively on behalf of and according to Customer's instructions, unless required by law (Customer notified first unless the law prohibits this) |
| Confidentiality of staff | All personnel with access to personal data are obliged to keep it confidential, even beyond the term of the Main Contract |
| Security measures | Appropriate technical and organisational measures under GDPR Art. 32, including in particular those listed in Annex 1 |
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: ● 2023, November 24: updates to definitions
at static.element.io
Last updated 2023-11-24
In the vendor's words: updates to definitions
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
Is Element ISO 27001 certified?
Element states ISO/IEC 27001 (2022 edition, as Element names it) on its own page, but does not say there how to get the certificate. We read this on 2026-10-08.
- Claimed “Element is independently audited and certified as compliant with the ISO/IEC 27001:2022 information security management standard.”
Source: element.io, 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 |
|---|---|---|---|---|
| Cyber Essentials Plus · CyberEssentialsPlus | Claimed | — | element.io | 2026-10-08 |
| ISO/IEC 27001:2022 · ISO27001 | Claimed | Element is independently audited and certified as compliant with the ISO/IEC 27001:2022 information security management standard | element.io | 2026-10-08 |
| BITV 2.0 | Available on request | Accessibilty conformance reports available for clients | element.io | 2026-10-08 |
| Cyber Resilience Act | Claimed | — | element.io | 2026-10-08 |
| EN 301 549 | Claimed | accessibility across Element's product set; the page says Element aligns its efforts with these criteria, with ongoing audits (no conformance claimed) | element.io | 2026-10-08 |
| ISO/IEC 5230 | Claimed | Element's products are developed in accordance with ISO/IEC 5230 ("OpenChain"), an international standard for open source license compliance | element.io | 2026-10-08 |
| WCAG 2.1 Level AA · VPAT | Claimed | accessibility across Element's product set; the page says Element aligns its efforts with these criteria, with ongoing audits (no conformance claimed) | element.io | 2026-10-08 |
| WCAG AA 2.2 · VPAT | Available on request | Accessibilty conformance reports available for clients | element.io | 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
- ACN qualified cloud (Italy): checked 2026-11-16, no entry under Element; Element Creations Ltd; Element Software SARL
- ISO 27001 on the basis of IT-Grundschutz (BSI, Germany): checked 2026-11-16, no entry under Element; Element Creations Ltd; Element Software SARL
- CISPE Data Protection Code of Conduct (GDPR Art. 40): checked 2026-11-16, no entry under Element; Element Creations Ltd; Element Software SARL
- DORA critical ICT third-party providers (ESAs): checked 2026-11-16, no entry under Element; Element Creations Ltd; Element Software SARL
- Data Privacy Framework List (US): checked 2026-11-16, no entry under Element; Element Creations Ltd; Element Software SARL
- ENS certificates of conformity (CCN, Spain): checked 2026-11-16, no entry under Element; Element Creations Ltd; Element Software SARL
- EU Cloud Code of Conduct (GDPR Art. 40): checked 2026-11-16, no entry under Element; Element Creations Ltd; Element Software SARL
- FedRAMP Marketplace (US): checked 2026-11-16, no entry under Element; Element Creations Ltd; Element Software SARL
- GPAI Code of Practice signatories (European Commission): checked 2026-11-16, no entry under Element; Element Creations Ltd; Element Software SARL
- SecNumCloud qualified services (ANSSI, France): checked 2026-11-16, no entry under Element; Element Creations Ltd; Element Software SARL
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 |
|---|---|---|---|---|---|
| Element Server Suite Pro | 12 months | Declared | unknown | element.io | 2026-10-11 |
Vulnerability reporting: security@element.io (security.txt, expired 2025-01-30; 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-11 |
| subprocessors | Public | full | 200 | 2026-10-08 |
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.