Elastic Cloud
Observability · elastic.co · last read 2026-11-16
At a glance
- Is Elastic Cloud GDPR compliant?
- No tool is GDPR compliant on its own: compliance depends on what you process with it and how. What follows is what Elastic Cloud itself publishes, each answer linked to its source and the date we read it.
- Does Elastic Cloud have a data processing agreement (DPA)?
- Yes. Elastic Cloud publishes a data processing agreement at elastic.co. It gives 30 days' notice before a new subprocessor is added. It promises breach notification "without undue delay", with no number of hours. Source and date
- Which version of the Elastic Cloud DPA is current?
- On 2026-11-09, Elastic Cloud's DPA at elastic.co printed “v100623.0 – Elastic Data Processing Addendum – ES ALL”. Source and date
- Does Elastic Cloud have a SOC 2 report?
- Elastic Cloud states SOC 2 (no type given) 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 Elastic Cloud ISO 27001 certified?
- Elastic Cloud 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 Elastic Cloud's trust center?
- Elastic Cloud publishes a page it calls “Trust center” at elastic.co/trust. Some of its documents sit behind a request or sign-in: the page says “Request access”. The page mentions SOC 2 and ISO 27001. We read it on 2026-11-03. Source and date
- How does Elastic Cloud transfer personal data out of the EU?
- Elastic Cloud's agreement relies on the EU standard contractual clauses and the UK transfer addendum. We found no entry for Elastic Cloud on the official Data Privacy Framework List. Source and date
- Does Elastic Cloud offer EU data residency?
- The vendor documents an EU region but states nothing about which plan reaches it or what it costs. Source and date
- Who are Elastic Cloud's subprocessors?
- Elastic Cloud lists 22 third-party subprocessors; 13 of them name at least one processing country outside the EEA. We last read the list on 2026-10-08. Source and date
The same questions for any vendor, and the rule behind each: the vendor due diligence checklist.
Identity
No identity observation recorded yet.
Elastic Cloud data residency
| Region | EU data location | Minimum plan | Source | Observed |
|---|---|---|---|---|
| EU | Terms not stated | — | elastic.co | 2026-10-08 |
EU: EU regions such as AWS EU (Frankfurt) are listed as available for ECH deployments. The customer picks the region, and the page names no plan or price for it.
The same question for every vendor: where SaaS vendors store EU data.
Elastic Cloud's subprocessor list names AWS, Microsoft and Google for hosting or infrastructure. Which SaaS vendors run on which cloud, and the sovereign offerings of each: sovereign clouds.
Subprocessor chain
22 third parties · 13 with a country outside the EEA · all read 2026-10-08
| Subprocessor | Country | Purpose |
|---|---|---|
| Amazon Web Services EMEA SARL | — | Hosting (in Europe, the Middle East, and Africa) |
| Amazon Web Services, Inc. | US | Backup |
| Amazon Web Services, Inc. | — | Hosting (other than in Europe, the Middle East, and Africa) |
| Amazon Web Services, Inc. | US | Hosting for https://support.elastic.co and the Elastic Uploader Service |
| Atlassian Statuspage | — | Public status-page monitoring: https://status.jina.ai/ |
| Cloudflare, Inc. | — | CDN / edge proxy for Jina AI APIs and dashboard |
| Google Ireland Limited (GCP) | IE | Email correspondence with support via Gmail |
| Google Ireland Limited (GCP) | — | Hosting |
| Google LLC (GCP) | US | Hosting and inference for embeddings, rerank, and related public API services(api.jina.ai) |
| Google LLC (GCP) | US, BE, SG | Hosting for EIS(Elastic Inference Service) executors on Jina GCP |
| Google LLC (GCP) | US, BE | Hosting for Jina AI Reader and Search (r.jina.ai, s.jina.ai) |
| International Business Machines Corporation (IBM Cloud (Softlayer)) | US | Hosting |
| Microsoft Corporation (Azure) | — | Hosting |
| MongoDB, Inc. | US, BE | Caching layer and database for Jina Reader |
| Okta, Inc. | US | Access authentication |
| Salesforce.com, Inc. | US | Customer support ticketing via Service Cloud |
| Serper | US, SG | SERP API (Google Search) for Jina Search |
| Stripe, Inc. | US | Payment processing for prepaid tokens |
| Supabase, Inc. | US | Account, API key, and prepaid-wallet database |
| ThorData | — | Residential proxy when Reader cannot fetch a URL directly |
| Tines Automation, Inc. | US | Enterprise workflow automation based on alerts from the customer's Elastic Products (servicing customers in the US, Canada, and Mexico) |
| Tines Security Services Limited | IE | Enterprise workflow automation based on alerts from the customer's Elastic Products (servicing customers in all locations except the US, Canada, and Mexico) |
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 · elastic.co
| Term | What the agreement says |
|---|---|
| Transfer mechanism | SCC module 2 |
| Transfer mechanism | SCC module 3 |
| Transfer mechanism | Swiss FADP clauses |
| Transfer mechanism | UK Addendum |
| Transfer mechanism | other |
| Notice of new subprocessors | At least 30 days in advance of changes, by email to customers subscribed to the RSS feeds at the subprocessor list URLs |
| If you object to one | Customer may object in writing with reasonable grounds within 30 calendar days of notice; parties discuss in good faith; if unresolved, Elastic at its sole discretion either does not appoint the subprocessor or lets customer suspend or terminate the affected offerings without liability |
| Obligations passed to subprocessors | Written agreement with each Sub-processor imposing data protection terms requiring protection to the standard of Applicable Data Protection Laws and this DPA; Elastic remains liable for Sub-processors |
| Breach notification | without undue delay, by email to the Organization Owner's customer-designated address |
| Deletion when the service ends | Delete all Customer Personal Data (including copies) upon termination or expiry of the Elastic Offerings, or earlier per the applicable data retention policy, except where retention is required by applicable law |
| Requests from data subjects | Self-service functionality to retrieve, correct or delete data; where Customer cannot access the data itself, reasonable cooperation to help Customer respond to individuals' requests |
| Audit | Under US privacy laws, customer may take reasonable and appropriate steps to ensure compliance, following the audit parameters in Section 3.4 (Audits) |
| Audit | written responses to reasonable information requests and security/audit questionnaires, confidential, no more than once per 12-month rolling period; also when requested by a data protection authority |
| Processing on your instructions | Processes Customer Personal Data for purposes in the Agreement and in accordance with Customer's documented lawful instructions; notifies Customer if an instruction is believed to violate data protection law |
| Confidentiality of staff | persons authorized by Elastic to process Customer Personal Data are under an appropriate contractual or statutory obligation of confidentiality |
| Security measures | appropriate technical and organizational security measures defined in the Elastic Security Standards, to protect Customer Information from a Security Breach |
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: v100623.0 – Elastic Data Processing Addendum – ES ALL
at elastic.co
Version v100623.0
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 Elastic Cloud have a SOC 2 report?
Elastic Cloud states SOC 2 (no type given) on its own page, but does not say there how to get a report. We read this on 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 Elastic Cloud ISO 27001 certified?
Elastic Cloud 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.
On the same list Elastic Cloud also names ISO/IEC 27017 and ISO/IEC 27018. Each standard's page says how it relates to ISO/IEC 27001.
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 |
|---|---|---|---|---|
| CSA STAR · CSA | Claimed | — | elastic.co | 2026-10-08 |
| Cyber Essentials Plus · CyberEssentialsPlus | Claimed | — | elastic.co | 2026-10-08 |
| FedRAMP High · FedRAMP | Claimed | — | elastic.co | 2026-10-08 |
| FedRAMP Moderate · FedRAMP | Claimed | — | elastic.co | 2026-10-08 |
| HIPAA | Claimed | — | elastic.co | 2026-10-08 |
| IRAP Assessed: Protected B · IRAP | Claimed | — | elastic.co | 2026-10-08 |
| ISO/IEC 27001 · ISO27001 | Claimed | — | elastic.co | 2026-10-08 |
| ISO/IEC 27017 · ISO27017 | Claimed | — | elastic.co | 2026-10-08 |
| ISO/IEC 27018 · ISO27018 | Claimed | — | elastic.co | 2026-10-08 |
| CyberGRX | Claimed | — | elastic.co | 2026-10-08 |
| PCI DSS · PCIDSS | Claimed | — | elastic.co | 2026-10-08 |
| SOC 2 · SOC2 | Claimed | — | elastic.co | 2026-10-08 |
| SOC 3 · SOC3 | Claimed | — | elastic.co | 2026-10-08 |
| TISAX | Claimed | — | elastic.co | 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 |
|---|---|---|---|---|---|
| FedRAMP Marketplace (US) | Elastic Cloud Hosted - High · Elastic Cloud Hosted | FedRAMP Authorized | High | — | 2026-10-09 |
- ACN qualified cloud (Italy): checked 2026-11-16, no entry under Elastic Cloud
- ISO 27001 on the basis of IT-Grundschutz (BSI, Germany): checked 2026-11-16, no entry under Elastic Cloud
- CISPE Data Protection Code of Conduct (GDPR Art. 40): checked 2026-11-16, no entry under Elastic Cloud
- DORA critical ICT third-party providers (ESAs): checked 2026-11-16, no entry under Elastic Cloud
- Data Privacy Framework List (US): checked 2026-11-16, no entry under Elastic Cloud
- ENS certificates of conformity (CCN, Spain): checked 2026-11-16, no entry under Elastic Cloud
- EU Cloud Code of Conduct (GDPR Art. 40): checked 2026-11-16, no entry under Elastic Cloud
- FedRAMP Marketplace (US): checked 2026-11-16, 1 entry under Elastic Cloud
- GPAI Code of Practice signatories (European Commission): checked 2026-11-16, no entry under Elastic Cloud
- SecNumCloud qualified services (ANSSI, France): checked 2026-11-16, no entry under Elastic Cloud
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 |
|---|---|---|---|---|---|
| Elastic Cloud Enterprise | 30 months | Declared | unknown | elastic.co | 2026-10-11 |
| Elastic Cloud on Kubernetes | 30 months | Declared | unknown | elastic.co | 2026-10-11 |
| Elasticsearch | 30 months | Declared | unknown | elastic.co | 2026-10-11 |
Vulnerability reporting: no security.txt at the well-known path (read 2026-10-17)
How other vendors publish theirs: security.txt across the registry.
Documents
Where is Elastic Cloud's trust center?
Elastic Cloud publishes a page it calls “Trust center” at elastic.co/trust. Some of its documents sit behind a request or sign-in. The page mentions SOC 2 and ISO 27001. We read it on 2026-11-03. Open elastic.co/trust
- Name “Trust center”
- Request step “Request access”
Source: elastic.co, 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-11 |
| residency | Public | full | 200 | 2026-10-08 |
| subprocessors | Public | full | 200 | 2026-10-08 |
| tia | Public | full | 200 | 2026-10-20 |
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.