RoPA Pilot

MongoDB Atlas and GDPR: hosting, non-EU transfer and DPA

MongoDB Atlas is published by MongoDB, Inc.. If your teams use it, it is a processor within the meaning of Article 28 GDPR and it must appear in your record of processing activities.

Vendor (processor)
MongoDB, Inc.
Headquarters
United States
EU hosting
EU optional (plan/config)
Non-EU transfer
Yes
Transfer mechanism
United States — EU-US DPF
Category
Development
Typical personal data
identity, technical data, content
Detected domains
cloud.mongodb.com

Does using MongoDB Atlas mean a non-EU transfer?

Yes. MongoDB, Inc. is a US vendor listed under the EU-US Data Privacy Framework: the transfer is lawful as long as the certification is active — check it on dataprivacyframework.gov and record the date of your check.

What to write in your Article 30 record

Purpose: Development. Categories of personal data: identity, technical data, content. Recipient: MongoDB, Inc.. Transfer: United States — EU-US DPF. Retention: aligned with the contract or the account lifetime, whichever is shorter.

How RoPA Pilot handles it

RoPA Pilot detects MongoDB Atlas from the domain name of the tab — never from page content — and pre-fills the record above in one click. The extension flags the record if the transfer mechanism is missing or unverified.

Indicative information from public sources. The transfer mechanism actually applicable to you is the one written in your contract.