New Relic
Observability · newrelic.com · last read 2026-11-16
At a glance
- Is New Relic GDPR compliant?
- No tool is GDPR compliant on its own: compliance depends on what you process with it and how. What follows is what New Relic itself publishes, each answer linked to its source and the date we read it.
- Does New Relic have a data processing agreement (DPA)?
- Yes. New Relic publishes a data processing agreement at newrelic.com. It gives 21 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 New Relic DPA is current?
- On 2026-11-02, New Relic's DPA at newrelic.com printed “Last Updated: July 22, 2026”. Source and date
- Does New Relic have a SOC 2 report?
- New Relic 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 New Relic ISO 27001 certified?
- New Relic 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
- How does New Relic transfer personal data out of the EU?
- New Relic's agreement relies on the EU standard contractual clauses, the EU-U.S. Data Privacy Framework and the UK transfer addendum. New Relic is on the official Data Privacy Framework List (status: Active). Source and date
- Does New Relic 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 New Relic's subprocessors?
- New Relic lists 18 third-party subprocessors; 11 of them name at least one processing country outside the EEA. We last read the list on 2026-10-19. We have recorded 1 change to it, the latest on 2026-10-19. Source and date
- How do you report a security vulnerability to New Relic?
- New Relic publishes a security.txt at newrelic.com naming https://hackerone.com/newrelic. 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 | New Relic, Inc. |
|---|---|
| HQ | US |
| Parent company | — |
| Ultimate ownership | — |
| EU contracting entity | — |
| LEI | 549300AB8FY2HQILL804 |
| US CLOUD Act reach | Contracting entity incorporated in the US |
| Source | newrelic.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.
New Relic data residency
| Region | EU data location | Minimum plan | Source | Observed |
|---|---|---|---|---|
| EU | Terms not stated | — | docs.newrelic.com | 2026-10-08 |
EU: The customer can choose the EU region when creating an organization at signup; the default is the US region. No plan is named as a requirement. The document says only that "Costs for data ingest may vary depending on your data center region" and refers to the pricing page. It does not state a specific uplift.
The same question for every vendor: where SaaS vendors store EU data.
New Relic'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
18 third parties · 11 with a country outside the EEA · all read 2026-10-19
| Subprocessor | Country | Purpose |
|---|---|---|
| Anthropic Claude | — | Support |
| Atlassian/Jira | US | Management of customer support tickets |
| AWS | US | Data storage and diagnostics (Codestream) |
| AWS | — | Infrastructure, Cloud service provider, including AI services for intelligence features |
| CloudFlare | — | Traffic routing, TLS Termination and security services |
| EzProtect (Adaptus) | US | Cybersecurity solution scanning user-uploaded content to ensure it is not malicious |
| Fastly | — | Traffic routing & TLS Termination |
| Fivetran | US | Connector and extract, transform and load (ETL) services |
| — | Infrastructure; Cloud service provider; including AI services for intelligence features; Email and office applications | |
| Google Cloud Platform | — | Data storage and diagnostics (Pixie) |
| Kentik | US | Network Synthetic monitoring |
| Microsoft Azure | — | Infrastructure, Cloud service provider, including AI services for intelligence features |
| Pinecone.io | US | Vector database providing vector storage, search, matching, and document retrieval in connection with New Relic’s AI-assisted services |
| PubNub | US | Real-time messaging between the CodeStream client extensions and Cloudstream’s API service in the cloud |
| Salesforce Service Cloud and Agentforce | US | Management of customer support tickets |
| Sendgrid | US | Email messaging services |
| Sendgrid | US | Emails messaging services (Codestream) |
| Snowflake | US | Data warehouse services |
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 · newrelic.com
| Term | What the agreement says |
|---|---|
| Transfer mechanism | EU-U.S. DPF |
| 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 | 21 days' prior notice of new core third-party sub-processors, provided customer signs up for notifications at the New Relic sign-up URL |
| Notice of new subprocessors | For non-core sub-processors tied to optional new features the customer must deliberately enable: notice given at the same time as the feature announcement |
| Notice of new subprocessors | Prior notice of Sub-Processor changes under SCC Clause 9 Option 2; period as set out in Section 9.2 of the Addendum |
| If you object to one | Customer may send a reasonable written objection within 10 business days of notice; if it does not, the new sub-processor counts as approved |
| If you object to one | New Relic uses reasonable efforts to offer a change that avoids the sub-processor; if none within a reasonable period (max 45 days), customer may terminate the affected order |
| Obligations passed to subprocessors | Places obligations substantially similar to this Addendum on each Sub-Processor, after due diligence and security review; remains fully liable for the Sub-Processor's performance |
| Breach notification | without undue delay after becoming aware of a Personal Data Breach |
| Deletion when the service ends | On Customer's written request, closes the account and deletes all Personal Data within 90 days of termination. Data that the law requires New Relic to keep is securely isolated and protected from further processing. A certificate of deletion is provided on request where SCC Clause 8.5 applies |
| Getting your data back | On Customer's written request and at Customer's election, New Relic returns the Personal Data instead of deleting it |
| Requests from data subjects | Uses reasonable efforts, at Customer's expense, to help Customer respond to data subject requests; does not answer a request sent to it directly without Customer's prior authorization unless legally compelled or Customer cannot be identified |
| Audit | Customer may audit once annually, on its own behalf or at a supervisory authority's direction; New Relic provides its third-party certifications and audits, to Customer or a non-competitor independent auditor |
| Processing on your instructions | processes Personal Data only as a Processor acting on behalf or on the instruction of Customer |
| Confidentiality of staff | authorized persons (staff and agents) committed to a contractual or statutory duty of confidentiality and receive privacy and security training |
| Security measures | appropriate technical and organizational measures per Article 32 GDPR, set out in Schedule 2 (Security) |
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-02, the agreement printed: Last Updated: July 22, 2026
at newrelic.com
Last updated 2026-07-22
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 New Relic have a SOC 2 report?
New Relic 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 New Relic ISO 27001 certified?
New Relic 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.
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 |
|---|---|---|---|---|
| FedRAMP | Claimed | — | docs.newrelic.com | 2026-10-08 |
| HIPAA enabled capabilities · HIPAA | Claimed | — | docs.newrelic.com | 2026-10-08 |
| ISO 27001 · ISO27001 | Claimed | — | docs.newrelic.com | 2026-10-08 |
| ISO 42001 · ISO42001 | Claimed | — | docs.newrelic.com | 2026-10-08 |
| PCI DSS · PCIDSS | Claimed | — | docs.newrelic.com | 2026-10-08 |
| SOC 1 · SOC1 | Claimed | — | docs.newrelic.com | 2026-10-08 |
| SOC 2 · SOC2 | Claimed | — | docs.newrelic.com | 2026-10-08 |
| TISAX | Claimed | — | docs.newrelic.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 |
|---|---|---|---|---|---|
| Data Privacy Framework List (US) | EU-U.S. Data Privacy Framework · New Relic | Active | non-HR data | 2027-08-12 | 2026-10-09 |
| Data Privacy Framework List (US) | Swiss-U.S. Data Privacy Framework · New Relic | Active | non-HR data | 2027-08-12 | 2026-10-09 |
| Data Privacy Framework List (US) | UK Extension to the EU-U.S. DPF · New Relic | Active | non-HR data | 2027-08-12 | 2026-10-09 |
| FedRAMP Marketplace (US) | New Relic · New Relic | FedRAMP Authorized | Moderate | — | 2026-10-09 |
| Global LEI Index (GLEIF) | NEW RELIC, INC. · NEW RELIC, INC. | ISSUED | US-DE | 2026-12-19 | 2026-10-09 |
- ACN qualified cloud (Italy): checked 2026-11-16, no entry under New Relic; New Relic, Inc.
- ISO 27001 on the basis of IT-Grundschutz (BSI, Germany): checked 2026-11-16, no entry under New Relic; New Relic, Inc.
- CISPE Data Protection Code of Conduct (GDPR Art. 40): checked 2026-11-16, no entry under New Relic; New Relic, Inc.
- DORA critical ICT third-party providers (ESAs): checked 2026-11-16, no entry under New Relic; New Relic, Inc.
- Data Privacy Framework List (US): checked 2026-11-16, 3 entries under New Relic; New Relic, Inc.
- ENS certificates of conformity (CCN, Spain): checked 2026-11-16, no entry under New Relic; New Relic, Inc.
- EU Cloud Code of Conduct (GDPR Art. 40): checked 2026-11-16, no entry under New Relic; New Relic, Inc.
- FedRAMP Marketplace (US): checked 2026-11-16, 1 entry under New Relic; New Relic, Inc.
- GPAI Code of Practice signatories (European Commission): checked 2026-11-16, no entry under New Relic; New Relic, Inc.
- SecNumCloud qualified services (ANSSI, France): checked 2026-11-16, no entry under New Relic; New Relic, Inc.
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 |
|---|---|---|---|---|---|
| Java agent v9.5.0 | 2027-09-25 | Declared | unknown | docs.newrelic.com | 2026-10-11 |
| New Relic distributed software | 12 months | Declared | unknown | docs.newrelic.com | 2026-10-11 |
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-11 |
| lifecycle-2 | Public | full | 200 | 2026-10-11 |
| residency | Public | full | 200 | 2026-10-08 |
| subprocessors | Public | full | 200 | 2026-10-19 |
History
| Detected | What moved | Why | Source |
|---|---|---|---|
| 2026-10-19 | Subprocessors added Anthropic Claude; Google; Salesforce Service Cloud and Agentforce Subprocessors removed Salesforce Service Cloud; Zendesk | the vendor changed it | newrelic.com |
Every reviewed change across the registry, newest first: vendor changes.