Trains on customer data
unclear
Not stated in the documents we could read. An absence here is an unknown, not a no.
Opt-out mechanism
You may "opt-out" of those communications by following the unsubscribe instructions provided in the e-mail or by contacting us directly (please see Controller and Contact Details).
“You may "opt-out" of those communications by following the unsubscribe instructions provided in the e-mail or by contacting us directly (please see Controller and Contact Details).”
AI features
none stated
Not stated in the documents we could read. An absence here is an unknown, not a no.
Model providers named
none named
Not stated in the documents we could read. An absence here is an unknown, not a no.
Retention
not stated
Not stated in the documents we could read. An absence here is an unknown, not a no.
Hosting regions
not stated
Not stated in the documents we could read. An absence here is an unknown, not a no.
Subprocessor notice
not stated
Not stated in the documents we could read. An absence here is an unknown, not a no.
Downstream
Who's behind MongoDB, as listed in its own subprocessor documents. 0 listed.
Model providers
- none listed
Hyperscalers
- none listed
Other subprocessors
- none listed
Reviewer notes
Extracted by deterministic rules (rules/v1), no language model. Coverage is limited to recognisable clauses and a gazetteer of common subprocessors; absent values mean 'not matched', not 'not present'. no training clause matched
Documents read
- privacy policy https://www.mongodb.com/legal/privacy/privacy-policyHTTP 200 · 2026-09-05
- dpa https://www.mongodb.com/legal/dpaHTTP 200 · 2026-09-06
Document changes
- high 2026-09-06 · dpa +3 / −3 lines
show diff
+ 3.2. Security Measures. We will implement appropriate technical and organizational security measures to ensure a level of security appropriate to the risks that are presented by the processing of Customer Personal Data. The current technical and organizational security measures are described at https://www.mongodb. (“Technical and Organizational Security Measures”).+ 4.1. Authorized Subprocessors. You acknowledge and agree that we may retain our affiliates and other third parties to further process Customer Personal Data on your behalf as Subprocessors in connection with the provision of the Cloud Services. We maintain a current list of our Subprocessors at: https://www.mongodb. which we will update at least 30 days before the addition or replacement of any Subprocessor. You may also register to receive email notifications of any change to our list of Subprocessors.+ 3.3.6 For transfers to Subprocessors, the subject matter and nature of the processing is described at: https://www.mongodb.. The duration of processing by Subprocessors is the same as by Data Importer.− 3.2. Security Measures. We will implement appropriate technical and organizational security measures to ensure a level of security appropriate to the risks that are presented by the processing of Customer Personal Data. The current technical and organizational security measures are described at https://www.mongodb.com/legal/customer-service-agreement/technical-and-organizational-security-measures (“Technical and Organizational Security Measures”).− 4.1. Authorized Subprocessors. You acknowledge and agree that we may retain our affiliates and other third parties to further process Customer Personal Data on your behalf as Subprocessors in connection with the provision of the Cloud Services. We maintain a current list of our Subprocessors at: https://www.mongodb.com/products/platform/trust/subprocessors which we will update at least 30 days before the addition or replacement of any Subprocessor. You may also register to receive email notifications of any change to our list of Subprocessors.− 3.3.6 For transfers to Subprocessors, the subject matter and nature of the processing is described at: https://www.mongodb.com/products/platform/trust/subprocessors. The duration of processing by Subprocessors is the same as by Data Importer.
Fact changes
No changes recorded yet. Changes appear here when a later reading differs from an earlier one.
Corrections
No correction requests. Anyone may dispute a fact with a source; requests and resolutions are public and ledger-entered.
Facts are as stated in MongoDB's public documents on the date read. This is a record, not legal advice. Work for MongoDB? Claim this profile · Something wrong? Request a correction.