Merge pull request #17211 from demel/patch-1

Update NR Customer-Facing Docs Hosting and data storage Sections

src/content/docs/security/security-privacy/data-privacy/security-controls-privacy.mdx

@@ -44,11 +44,11 @@ Typically the numbered host is fixed for your account, and it appears in `log/ne
 
 For required changes when you want to create firewall rules to allow the agent to communicate, see [Networks](/docs/using-new-relic/cross-product-functions/install-configure/networks). For more information about security measures for your data in transit to New Relic or at rest in our storage, see [Data encryption](/docs/security/new-relic-security/compliance/data-encryption).
 
-## Hosting and data storage [#Hosting_and_Data_Storage]
+## Cloud Data Storage [#cloud-data-storage]
 
-New Relic is self-hosted with co-location services called Server Central in a Tier 3 data center in Chicago, Illinois and an IBM-hosted data center near Frankfurt, Germany, as well as cloud storage through Amazon Web Services. We use standard best practices to maintain a firewall for our servers and to protect our servers from unauthorized login.
+New Relic uses a multi-cloud data storage approach in two regions currently, the United States and the European Union. We currently have data storage in Amazon Web Services and Azure in those regions. Data is stored in our New Relic telemetry database. 
 
-All data is stored in a cluster of MySQL databases. New Relic data is backed up nightly, and an archive is stored at a secondary data center.
+We have specific certifications and standards as it pertains to data storage, which can be found in more detail in our [Certifications, standards, and regulations](https://docs.newrelic.com/docs/security/security-privacy/compliance/regulatory-audits-new-relic-services/) documentation. 
 
 ## Data access [#Data_Access]