The GDPR is a European privacy law that became enforceable on May 25, 2018. The GDPR replaces the EU Data Protection Directive and is intended to reconcile data protection laws throughout the European Union (EU) by applying a single data protection law enforceable across every member state. The GDPR does the following:
The GDPR applies not only to organizations established within the EU, but also to organizations located outside of the EU that offer goods or services to, or monitor the behaviour of, EU data subjects. It applies to all companies processing and holding the personal data of data subjects located in the European Union, regardless of the company’s location. The GDPR defines personal data to include any information relating to an identified or identifiable natural person.
MongoDB is working across our organization to ensure that our products and services enable our customers to comply with GDPR. This includes:
MongoDB Atlas, MongoDB’s cloud database service, is security hardened by default. Each MongoDB Atlas project is provisioned into its own VPC, thereby isolating your data and underlying systems from other MongoDB Atlas users. Network encryption, storage volume encryption and access control are configured by default, and IP whitelists allow you to specify a specific range of IP addresses against which access will be granted. All security-specific updates to the operating system and database of the underlying instances are automatically applied by MongoDB engineers. For deployments running in AWS, VPC Peering can be used to connect your application servers deployed to another AWS VPC directly to your MongoDB Atlas cluster using private IP addresses.
Read the MongoDB Atlas Security Controls white paper for more information.
MongoDB also pursues external testing and certifications regarding security for Atlas. Visit the SOC 2 overview for more information.
MongoDB Atlas infrastructure runs on top of Amazon Web Services, Microsoft Azure, and Google Cloud Platform. Each cloud provider undergoes its own series of independent third-party audits on a regular basis.
The GDPR requires data controllers (such as organizations using MongoDB Atlas) to use only data processors (such as MongoDB) that provide sufficient guarantees to meet the requirements of GDPR Article 28. MongoDB’s terms of service applicable to MongoDB Atlas and other MongoDB Cloud Services reflect the Article 28 requirements
The terms of service applicable to MongoDB Cloud Services (including MongoDB Atlas) incorporate our Data Processing Agreement, which satisfies the requirements the GDPR imposes on data controllers with respect to data processors.
If you have questions about how these terms apply, please contact us at email@example.com
GDPR requires controllers and processors to implement appropriate safeguards before transferring personal data out of the EEA, Switzerland and the United Kingdom. When transferring personal data that our customers upload to our Cloud Services to countries that are not the subject of an adequacy decision by the European Commission (EC) or the United Kingdom, including the United States, MongoDB uses Standard Contractual Clauses as the transfer mechanism under Article 46 of GDPR.
In June 2021, the EC approved new SCCs. These new SCCs align with GDPR and also address issues raised by the European Court of Justice in its Schrems II decision. MongoDB has incorporated the new SCCs into our standard Data Processing Agreement, which itself is incorporated into our standard legal agreement governing our customers’ use of MongoDB’s Cloud Services. For transfers of customer personal data from the United Kingdom, the prior version of the SCCs will remain in place for the time being.
MongoDB assists our customers in complying with their obligations under Clause 14 of the new SCCs by contributing to our customers’ Transfer Impact Assessments (TIA) and by conducting our own TIAs when appropriate. We also enable our customers to implement technical supplementary measures, including data encryption options whereby our customers control the encryption keys, and MongoDB has implemented a number of its own contractual and organizational supplementary measures for the benefit of our customers. For more information about these measures, please see our DPA and our Technical & Organizational Security Measures.
Please contact us at firstname.lastname@example.org with any questions about the matters addressed above.
This page is for informational purposes only, and MongoDB does not intend the information or recommendations presented here to constitute legal advice. Each customer is responsible for independently evaluating its own particular use of MongoDB's services as appropriate to support its legal and compliance obligations.