New Relic Data Processing Agreement

The New Relic DPA is tailored to the service offer of New Relic and its surroundings with several customers. It outlines specialized procedures and procedures related to New Relic`s obligations as a data processor under the RGPD. New Relic DPA handles the relevant requirements of the RGPD with respect to the scope and confidentiality of data processing, security measures to ensure customer data security, the data breach notification process, and our audit and sub-processing activities. All of this correlates with how New Relic`s unique services and multi-body infrastructure work. The Dpa of New Relic describes our commitment to our obligations in accordance with the terms of the RGPD subcontractor in accordance with Article 28, paragraph 3, and refers to the specific provision of the RGPD that covers each section of the Dpa. This information in this document does not provide legal advice. We advise you to consult your own lawyer for advice tailored to your own unique situation and how you want to use the new relic services – remember that a privacy authority is only required if you intend to send personal data for processing purposes. You have the right to complain to a data protection authority about the collection and use of your personal data. For more information, please contact your local data protection authority. We may create anonymous data records from personal data in accordance with applicable legislation. A.

Collecting customer data (including performance data). The customer can use the services, to send new relic data, such as. B: (i) if our software (for example. B, agents, software development kits (SDK) etc.) is provided in our customers` applications, websites and infrastructure, (ii) synthetic monitors (simulating transactions and user actions) or (iii) cloud integration or (iii) when sent to our data collection systems (for example. B application program interface (API). which allows data transfer between applications) for processing made available on the customer account (“customer data”). We use a comprehensive set of technical controls to support the general security requirements as well as the data security we receive. You`ll find more information in our data security, data encryption and high-security information for APM agents. By default, our alert services do not collect personal data. In addition, they automatically set standard permissions for individual account users and access levels within account structures. You will find more information in our documentation on applied intelligence as well as in our rules and limits for alerts. New Relic has a series of internal policies and procedures to assist employees in data protection-related areas, such as data classification and processing, data retention, processing of personal data, processing of personal data requests, incident response, etc.

All staff members are required to complete data security and protection training each year after the recruitment and renewal of this training. You may want to process personal data in New Relic products or services through your own customers. We have taken steps to ensure that you can do so in accordance with existing data protection legislation, such as the General Data Protection Regulation (GDPR) in the EU. Your personal data can be transferred and processed in countries other than the country you are in. These countries may have data protection laws that differ from those in your country. “System Operational Data” is data relating to the use and operation of our services and the systems and networks on which these services are performed, including log files, event files and other tracking and diagnostic files, as well as data