Mongodb

Summary of Important Changes

> Note: The diff appears to contain substantial website-navigation and page-content corruption. Some apparent “changes” are likely scraping artifacts rather than intentional legal amendments. The substantive changes below are based on identifiable privacy-language replacements.

1. AI and chatbot processing

• The policy now expressly covers the operation of “AI chatbots and assistants on MongoDB properties.”
• Data categories expressly associated with this activity include:
• Identifiers;
• Technical information;
• Internet or electronic network activity;
• Profile information; and
• Chatbot inputs and outputs, which may contain personal data.
• MongoDB states that this processing is based on its legitimate interests and that chatbot interaction is entirely optional.
• Affiliates and service providers may receive data for this purpose.

AI-training implications

• The diff does not expressly state that customer data, chatbot inputs, outputs, or Product data will be used to train, fine-tune, or improve AI models.
• It also does not expressly prohibit such use. The broader provisions allowing analytics, Product improvement, creation and disclosure of “Anonymous Data,” and use by affiliates/service providers could potentially leave room for model-development or training-related uses, depending on how those provisions are interpreted.
• Customers should seek clarification on:
• Whether prompts, outputs, logs, or Product/customer data are used for model training or fine-tuning;
• Whether data is used to train MongoDB’s models or third-party models;
• Whether data is de-identified before such use;
• Retention and deletion of AI interaction data;
• Whether enterprise/customer content is segregated from public or aggregated training data; and
• Whether customers can opt out of any training or model-improvement use.

2. Expanded data collection and scope

• The policy now expressly covers data collected when users:
• Use MongoDB Products;
• Engage through online chat applications;
• Download or install Products;
• Create or access an account; and
• Register for newsletters, marketing materials, white papers, webinars, or events.
• The definition of Personal Data is framed more broadly to include information that could reasonably be linked directly or indirectly to an individual.
• The policy continues to cover browsing, search, technical, profile, commercial, and marketing data.

3. Anonymous Data

• The policy retains MongoDB’s ability to create Anonymous Data by excluding information from Personal Data and to use or disclose that Anonymous Data at its discretion.
• The broadened Personal Data definition may make the boundary between “anonymous” and identifiable data more important and potentially more contestable.
• The policy does not provide detailed safeguards against re-identification or expressly address whether Anonymous Data may be used for AI development.

4. Legal and operational changes

• A DPO contact is now expressly identified: privacy@mongodb.com.
• Rights requests may be submitted by email, telephone, or webform.
• The policy adds or clarifies accessibility-related assistance.
• The U.S. State Data Privacy Notice more clearly addresses collection, use, retention, disclosure, and CCPA “sharing” for targeted advertising.
• The policy continues to permit targeted advertising and sharing of technical data with third parties, subject to applicable opt-out rights.

Overall risk

The main new risk is greater transparency that AI chatbot interactions may contain personal data and may be shared with service providers, without a clear statement resolving whether those interactions or customer data may be used for AI training or model improvement.

Summary

The provided diff does not include the actual amended legal language. It only states:

> “Added approximately 251 words to the document”

Accordingly, it is not possible to identify:

• Which contractual provisions changed;
• New obligations, rights, fees, warranties, or liability exposures;
• Changes to confidentiality, data ownership, security, or permitted data uses;
• Whether customer data may be used to train, fine-tune, evaluate, or improve AI models;
• Whether such use is subject to consent, opt-out rights, anonymization, aggregation, retention limits, or restrictions on human review; or
• Whether the customer receives notice of model-training activities or protection against disclosure of its data through model outputs.

AI-Training Data Review

No substantive language concerning AI models or training data appears in the material provided. Therefore, no conclusion can be reached about whether the amendments:

• Permit use of customer content for AI training;
• Expand existing rights to use telemetry, prompts, inputs, outputs, or usage data;
• Allow data to be shared with affiliates, service providers, or third-party model providers;
• Remove or narrow confidentiality or deletion commitments; or
• Allocate responsibility for personal-data compliance and regulatory obligations.

Required Information

Please provide the full redlined text, including the approximately 251 added words and any surrounding provisions. The relevant changes should be shown using the stated notation:

• Additions: {new language}
• Deletions: [deleted language]
• Replacements: [old language]{new language}

Without the actual wording, a reliable legal-risk analysis is not possible.

Summary

The supplied diff does not include the actual contract language. It only states:

> “Added approximately 251 words to the document”

Accordingly, it is not possible to identify:

• The specific legal changes;
• New customer obligations or provider rights;
• Changes to liability, confidentiality, security, ownership, or termination;
• Whether customer data may be used to train, fine-tune, evaluate, or improve AI models;
• Whether such use is limited to de-identified, aggregated, or anonymized data;
• Whether customer consent, opt-out rights, or contractual safeguards have changed.

AI Training and Data-Use Risk

No conclusion can be reached about AI-model training from the information provided. The added language should be reviewed for terms such as:

• “train,” “fine-tune,” “improve,” “develop,” or “enhance” models;
• “inputs,” “outputs,” “customer data,” “usage data,” or “telemetry”;
• “de-identified,” “aggregated,” or “anonymized” information;
• Rights to retain data after termination;
• Provider rights to share data with affiliates, contractors, or third-party model providers;
• Customer opt-out, consent, or deletion rights;
• Restrictions on using confidential or personal information for training.

Information Needed

Please provide the complete redline or the actual 251 words added, using the stated notation:

• Additions: {...}
• Deletions: [...]
• Replacements: [...]{}

Without the underlying text, a substantive legal-risk analysis would be speculative.

Summary of Important Changes

> Important caveat: The diff appears heavily corrupted by inserted website-navigation text and repeated fragments. The conclusions below focus on identifiable substantive legal changes and should be verified against the clean revised policy.

1. AI-related processing

• The revised policy expressly adds processing to operate MongoDB AI chatbots and assistants on MongoDB properties.
• The data categories may include:
• Identifiers;
• Technical information;
• Internet/electronic network activity;
• Profile information; and
• Chatbot inputs and outputs, which may contain Personal Data.
• The stated legal basis is MongoDB’s legitimate interests. The policy says chatbot interaction is optional, and that consent may be requested in some contexts.
• No express authorization to train AI models is visible in this diff. It does not clearly state that customer prompts, outputs, product data, or other Personal Data may be used to train, fine-tune, evaluate, or improve generative-AI models.
• However, the revised purposes include broad analytics and improvement of MongoDB’s website, Products, marketing, customer relationships, and user experiences. Those provisions could potentially support model improvement or evaluation unless limited elsewhere.
• Risk: Customers should not assume that “optional chatbot use” means inputs and outputs will never be retained, reviewed, shared with service providers, or used for AI development. A separate product-specific AI/data-processing notice or contract should be checked.

2. Expanded data collection

The policy now expressly covers data collected when users:

• Engage through online chat applications;
• Download and install Products;
• Create or use an account;
• Use Products;
• Register for newsletters, marketing materials, white papers, webinars, and events.

It also expressly adds chatbot inputs and outputs to the listed data categories. This increases the likelihood that user-submitted business or confidential information may be treated as Personal Data if it identifies, relates to, or could reasonably be linked to a person.

3. Narrower “Anonymous Data” concept

The definition changes from data merely “not associated with” a person to data that is not associated with or linked to Personal Data and does not permit identification of individuals. MongoDB may still create Anonymous Data from Personal Data by removing identifying information and may use or disclose it to third parties at its discretion.

Risk: De-identification standards and re-identification safeguards are not specified.

4. Sharing and advertising

The policy continues to permit sharing with affiliates, service providers, and third parties, including for targeted advertising, direct marketing, analytics, and product improvement. The CCPA section clarifies that MongoDB does not “sell” data but may engage in “sharing” for cross-context behavioral advertising.

5. Other notable changes

• A DPO and updated privacy-rights contact channels are identified.
• U.S. state privacy disclosures are expanded and separated into a state notice.
• Accessibility commitments are added.
• Data collection, retention, and legal-basis descriptions are reorganized and expanded.

Overall risk assessment

The principal change is the formal inclusion of AI chatbot/assistant interactions and their potentially personal content. The policy does not clearly grant or deny model-training rights, leaving material uncertainty for customers concerned about confidential data, model training, retention, or third-party AI providers.

Summary

The provided diff does not include the actual amended contract language. It only states:

> “Added approximately 251 words to the document”

Because the added text is not shown, it is not possible to determine:

• What contractual provisions changed;
• Whether new obligations, permissions, or liabilities were introduced;
• Whether customer data may be used to train, fine-tune, evaluate, or improve AI models;
• Whether data is shared with affiliates, service providers, or model providers;
• Whether customer data is retained after termination;
• Whether customer data is anonymized, aggregated, or de-identified before use;
• Whether the customer can opt out of AI training or request deletion; or
• Whether the provider claims ownership or broad usage rights over customer inputs, outputs, or derived data.

AI-Training Risk Assessment

No conclusion can be reached regarding AI-model training because the relevant added language is missing. The key provisions to examine would include references to:

• “train,” “fine-tune,” “improve,” “develop,” or “evaluate” models;
• “inputs,” “content,” “customer data,” or “usage data”;
• de-identification, anonymization, or aggregation;
• use by affiliates, contractors, or third-party AI providers;
• opt-out mechanisms or enterprise exclusions;
• retention and deletion periods; and
• ownership of model outputs, embeddings, or other derived materials.

Information Needed

Please provide the actual 251-word addition and, ideally, the surrounding original language. The changes can then be analyzed for legal effect, including data-use permissions, confidentiality, intellectual-property rights, privacy compliance, security exposure, and termination-related risks.

Structured Summary of Important Changes

1. AI-related processing

• The revised policy expressly adds AI chatbots and assistants operated on MongoDB properties as a processing purpose.
• It identifies the following categories of data used for that purpose:
• Identifiers;
• Technical information;
• Internet or electronic network activity;
• Profile information; and
• Chatbot inputs and outputs, which may contain Personal Data.
• The stated legal basis is generally MongoDB’s legitimate interests. Interactions with the chatbots are described as optional.
• The policy also adds AI-focused product and marketing references, including Atlas Agent Engine and other AI-related services.

AI training risk

• The diff does not expressly state whether customer prompts, chatbot outputs, product usage data, or other Personal Data will be used to train, fine-tune, evaluate, or improve AI models.
• It also does not clearly state that such data will not be used for model training.
• The broad purposes of using data for analytics, improving Products, customer relationships, and experiences could potentially be interpreted to include AI-system improvement, but the policy does not provide sufficient detail.
• Customers should seek clarification on:
• Whether inputs and outputs are retained;
• Whether they are used to train MongoDB’s or third-party models;
• Whether data is de-identified before such use;
• Whether third-party AI providers may use the data for their own model training; and
• Whether enterprise customers can opt out or require deletion.

2. Expanded data collection

The policy now expressly covers collection when individuals:

• Use MongoDB Products;
• Engage through online chat applications;
• Download or install Products;
• Create accounts;
• Register for newsletters, marketing materials, white papers, webinars, or events; and
• Communicate with MongoDB.

It also expands the definition of Personal Data to include information that could reasonably be linked, directly or indirectly, to an individual. This may reduce the circumstances in which data is treated as Anonymous Data.

3. Anonymous Data

• MongoDB may create Anonymous Data from Personal Data and use or disclose it to Third Party Companies at its discretion.
• The revised language clarifies that Anonymous Data is data not associated with or linked to Personal Data and does not permit identification.
• However, the policy does not explain the de-identification methodology or address re-identification risks. “Anonymous” data used for analytics or AI development may therefore warrant further contractual controls.

4. Third-party sharing and advertising

• The policy continues to permit sharing with affiliates, service providers, and other third parties.
• It expressly addresses targeted advertising and “sharing” under U.S. state privacy laws, while stating that MongoDB does not “sell” Personal Data.
• Cookies and technical data may still be used for cross-context behavioral advertising.

5. Other notable changes

• A DPO contact and expanded rights-request methods are provided.
• U.S. state privacy disclosures are updated, including CCPA terminology.
• Accessibility commitments and contact information are added.
• The policy continues to rely heavily on legitimate interests and permits policy changes through future revisions.

Summary

The provided diff does not include the actual contractual language. It only states that approximately 251 words were added:

> “Added approximately 251 words to the document”

Because the added wording is not shown, it is not possible to reliably determine:

• What contractual obligations or rights changed.
• Whether liability, indemnification, confidentiality, intellectual property, or termination provisions were modified.
• Whether the customer’s data may be used to train, fine-tune, evaluate, or improve AI models.
• Whether data is shared with affiliates, vendors, or third-party AI providers.
• Whether customer data is retained after termination or deleted upon request.
• Whether the customer receives any opt-out, consent, or control rights.
• Whether the provider claims ownership of model outputs, derivatives, embeddings, or other trained materials.

AI-Training Review

No specific change concerning AI-model training can be identified from the supplied material. The actual 251 added words should be reviewed for terms such as:

• “train,” “fine-tune,” “improve,” “develop,” or “evaluate” models;
• “machine learning,” “artificial intelligence,” “generative AI,” or “models”;
• use of “customer data,” “content,” “inputs,” “prompts,” or “usage data”;
• rights to use data in aggregated, de-identified, or anonymized form;
• sharing data with subprocessors or third-party model providers;
• retention, deletion, or opt-out provisions; and
• ownership or licensing rights in resulting models or improvements.

Risk Assessment

The risk level cannot be assessed without the added language. In particular, a provision allowing customer data to be used for model training could create confidentiality, privacy, intellectual-property, regulatory, and data-security risks. The scope of any authorization, including whether it is perpetual, worldwide, irrevocable, royalty-free, or applies by default, would be especially important.

Please provide the actual inserted wording, ideally with the surrounding clauses, for a substantive comparison.

No

Executive Summary

The diff appears to replace or substantially restructure the Privacy Policy, with a revised date of November 4, 2025. It also expands the policy from website-focused processing to processing connected with MongoDB’s products, services, chat tools, and AI assistants.

Key Changes and Risks

1. AI chatbots and assistants expressly covered

A new processing purpose permits MongoDB to:

• Operate “AI chatbots and assistants on MongoDB properties.”
• Process identifiers, technical data, internet/electronic activity, profile data, and chatbot inputs and outputs that may contain personal data.
• Rely on legitimate interests as the legal basis.
• Share relevant data with affiliates and service providers.

Interactions are described as “entirely optional,” which reduces—but does not eliminate—the risk that users may submit confidential, personal, or proprietary information into the tools.

Risk: The policy does not clearly explain what happens to chatbot inputs and outputs after collection, including retention, human review, security controls, cross-border transfers, or whether the information is used to improve or train AI models.

2. No express customer-data training authorization identified

The diff does not expressly state that customer data, chatbot inputs, outputs, or product data will be used to train, fine-tune, evaluate, or improve AI models.

However, the policy authorizes broad uses such as:

• Data analytics to improve products, marketing, customer relationships, and experiences.
• Creation and discretionary use of “Anonymous Data.”
• Processing chatbot inputs and outputs.
• Sharing data with affiliates, service providers, and third parties.

Important ambiguity: “Improve products” and analytics language could potentially be interpreted broadly enough to support model improvement, but it is not a clear or specific AI-training grant. Customers should seek confirmation in applicable product terms, enterprise agreements, data-processing addenda, or AI-specific documentation.

3. Broader data-collection scope

The revised policy expressly covers data collected when users:

• Use MongoDB Products;
• Download or install Products;
• Create or access accounts;
• Use online chat applications;
• Register for newsletters, webinars, white papers, and events;
• Interact with MongoDB websites, applications, or advertisements.

The categories of personal data are reorganized and expanded to include product usage, browsing/search history, commercial information, chat transcripts, and other interaction data.

4. Expanded third-party sharing and advertising disclosures

The policy continues to permit sharing with affiliates, service providers, and other third parties. It also more clearly addresses targeted advertising and “cross-context behavioral advertising” under U.S. state privacy laws.

MongoDB states that it does not sell personal information, but acknowledges that certain disclosures may constitute “sharing” under the CCPA.

5. Rights and administrative updates

The revised text:

• Adds or clarifies a DPO email address: privacy@mongodb.com.
• Updates privacy-rights request methods and phone number.
• Clarifies U.S. state privacy-law disclosures.
• Adds accessibility language.
• Updates the policy revision notice and formatting.

Overall Assessment

The most significant substantive change is the express inclusion of AI chatbot/assistant interactions and potentially personal data in prompts and outputs. The policy does not clearly authorize AI-model training, but its broad improvement, analytics, anonymous-data, and service-provider language leaves meaningful uncertainty.

No

No

Summary

The provided diff does not include the actual amended language. It only states:

> “Added approximately 159 words to the document”

Accordingly, it is not possible to identify:

• What contractual provisions changed;
• Whether customer data may be used to train, fine-tune, evaluate, or improve AI models;
• Whether any new customer consent or opt-out rights were added;
• Whether the provider obtained broader rights to use, retain, anonymize, aggregate, or disclose customer data;
• Changes to confidentiality, security, ownership, intellectual property, or compliance obligations; or
• Any changes to liability, indemnification, warranties, or termination rights.

AI Training Risk Assessment

No reliable assessment can be made because the added 159 words were not supplied. In particular, the diff does not reveal whether the new language:

• Authorizes use of customer content or inputs for model training;
• Permits use of metadata, prompts, outputs, telemetry, or usage information for AI development;
• Applies training rights by default or only with customer permission;
• Allows data to be shared with affiliates, subprocessors, or third-party model providers;
• Uses de-identification or aggregation as a basis for broader use;
• Allows retention after termination; or
• Gives the customer an effective opt-out or deletion right.

Information Needed

Please provide the full redline showing the additions, deletions, and replacements—for example, text in {added} and [deleted] format. Once provided, the changes can be analyzed for legal effect and specific risks, including any new rights to use customer data for AI training.

Summary

The provided diff does not include the actual added, deleted, or replaced legal language. It only states:

> “Added approximately 236 words to the document”

Accordingly, it is not possible to determine:

• What contractual terms changed;
• Whether customer data may be used to train, fine-tune, evaluate, or improve AI models;
• Whether any new rights were granted to the provider;
• Whether confidentiality, security, ownership, retention, or deletion obligations changed;
• Whether the customer accepted new liability, indemnity, or compliance risks.

AI Training and Data-Use Review

No specific language concerning AI models or the use of customer data is visible in the supplied diff. The available information therefore does not establish whether the agreement:

• Permits training general-purpose or customer-specific AI models using customer data;
• Allows use of prompts, inputs, outputs, usage data, telemetry, or personal information for model improvement;
• Requires customer consent or provides an opt-out;
• Aggregates, anonymizes, or de-identifies customer data before AI-related use;
• Allows subcontractors or affiliates to use the data;
• Retains data after termination for training or model development; or
• Grants the provider ownership or a broad license over customer data or outputs.

Risk Assessment

A reliable legal risk assessment cannot be completed without the actual redline text. The statement that approximately 236 words were added is not sufficient to identify the effect of those additions. In particular, the additions could contain material provisions hidden from review, including broad data licenses, AI-training permissions, reduced confidentiality protections, or expanded provider rights.

Information Needed

Please provide the actual text of the additions and any deleted or replaced language, using the stated notation:

• Additions: {new text}
• Deletions: [deleted text]
• Replacements: [old text]{new text}

Once provided, the changes can be analyzed for commercial impact, data-protection implications, and AI-training risks.

Structured Summary of Important Changes

1. Overall nature of the changes

The diff appears to reflect a substantial website redesign or content migration rather than a clean revision of the legal terms. Large portions of the former Terms of Use are replaced with website navigation, product descriptions, blog links, and marketing content. This creates a risk that legal text may have been accidentally displaced, truncated, or improperly rendered.

Action recommended: Confirm the final published Terms of Use against an authoritative clean copy. Do not rely on this diff alone to determine the complete legal effect.

2. AI-related changes

New AI marketing and product references

The revised website adds prominent references to:

• “AI agents”
• “accurate, relevant data”
• “gen AI”
• “AI-ready platform”
• “Artificial Intelligence”
• “AI” as a service or product-related designation

These additions promote MongoDB’s AI-related products and capabilities, but they do not expressly state that customer data will be used to train AI models.

Customer data used for AI training

Based on the provided diff:

• There is no clear new clause expressly authorizing MongoDB to use customer data, prompts, inputs, outputs, or uploaded content to train, fine-tune, or improve AI models.
• There is also no visible restriction stating that customer data will not be used for AI training.
• The existing user-submitted-content language appears to grant MongoDB a perpetual, irrevocable, worldwide, royalty-free, non-exclusive license regarding submitted “Content.” If that clause remains applicable, its breadth could create uncertainty about whether submitted content may be used for product improvement or AI-related purposes.
• The diff does not clarify whether “Content” includes confidential business information, prompts, AI inputs, generated outputs, telemetry, or data submitted through MongoDB products rather than the public website.

Risk: Customers may be unable to determine from these Terms whether their data can be used in AI development. A separate product agreement, privacy policy, or AI-specific data-use policy may control, but the revised website does not make that relationship clear.

3. Terms modification and acceptance

The revised language states that MongoDB may modify the Terms “from time to time without notice.” Continued use after publication constitutes binding acceptance of the updated Terms.

Risk: This permits unilateral changes without direct notice and may bind users through continued website use, including changes affecting data rights or AI-related practices.

4. Intellectual-property and content provisions

The revised text:

• Reorganizes trademark and copyright provisions.
• Retains restrictions on copying, redistribution, and commercial use of website content.
• Clarifies that trademarks may belong to MongoDB or third parties.
• Preserves a broad license concerning user-submitted content.

Risk: The broad content license should be reviewed to confirm its permitted purposes, sublicensing rights, retention period, and whether it covers customer data or only public website submissions.

5. Liability and disclaimers

The revised text retains “AS IS” and “AS AVAILABLE” disclaimers and a limitation of aggregate liability.

Risk: These provisions may limit remedies for inaccurate AI-related information, service interruptions, data misuse, or unauthorized model-training activity.

6. Key follow-up questions

• Does “Content” include customer data submitted through MongoDB services?
• Is customer data used to train or improve AI models?
• Are prompts and outputs retained?
• Are enterprise customers able to opt out?
• Which document controls if the Terms conflict with a product agreement or privacy policy?

Executive Summary

The diff appears to update and substantially reformat MongoDB’s Privacy Policy, while also adding language concerning AI chatbots and assistants. Much of the apparent change is website-navigation content rather than substantive legal text; however, the following legal changes are important.

AI and Training-Related Changes

• New processing purpose for AI tools: The policy now expressly states that MongoDB may process data to “operate our AI chatbots and assistants on MongoDB properties.”
• Types of AI data identified: The listed data may include:
• Identifiers;
• Technical information;
• Internet or electronic network activity;
• Profile information; and
• Chatbot inputs and outputs, which may contain personal data.
• Legal basis: MongoDB identifies legitimate interests as the legal basis for this processing.
• Optional use: Interaction with the chatbots is expressly described as optional, which reduces—but does not eliminate—the risk that users may unknowingly submit personal or confidential information.
• Recipients: AI-related data may be disclosed to MongoDB affiliates and service providers.

Training-model risk

The diff does not expressly state that customer or chatbot data will be used to train, fine-tune, evaluate, or improve generative AI models. It also does not expressly prohibit such use. The new wording is limited to operating AI chatbots and assistants. Consequently:

• There is no clear contractual commitment that chatbot inputs or outputs will not be used for model training.
• The reference to “legitimate interests” and disclosure to affiliates/service providers could leave some flexibility for secondary AI-related uses, depending on other policies or service-provider terms.
• Customers should seek confirmation of whether prompts, outputs, product usage data, or customer content are retained, reviewed by humans, shared with model providers, or used for training.

Other Material Changes

• Expanded policy scope and definitions: The policy more clearly covers Personal Data collected through MongoDB.com and in connection with MongoDB products and services.
• Third-party data sources: The policy continues to permit collection of Personal Data and Anonymous Data from third parties and technology providers.
• Analytics and advertising: The policy expressly describes targeted advertising, direct marketing, analytics, and sharing technical data—including IP addresses and device/browser information—with third parties.
• U.S. privacy compliance: The policy is reorganized to address the CCPA and other U.S. state privacy laws, including disclosures regarding collection, use, retention, and disclosure.
• Expanded rights process: A dedicated DPO contact, privacy email address, telephone number, and deletion-request webform are provided for exercising legal rights.
• Accessibility: A new accessibility section commits MongoDB to making its products and services accessible and provides contact information for related requests.
• Dispute contact: The general privacy-complaint email address changes to legal@mongodb.com.

Key Customer Risks

1. Unclear AI training position: No explicit opt-out or “no training” commitment appears in the revised language.

2. Sensitive disclosure risk: Users may submit confidential information to optional chatbots even though chatbot inputs and outputs may contain Personal Data.

3. Broad recipient categories: Affiliates and service providers may receive AI-related and other Personal Data.

4. Separate terms may control: The policy states that other privacy notices and product-specific terms may apply, so this document may not be the complete statement of AI-data practices.

Summary

The provided diff does not include the actual amended legal language. It only states:

> “Added approximately 159 words to the document”

Because the added words and any deleted or replaced language are missing, it is not possible to determine:

• What contractual provisions changed
• Whether new obligations, rights, fees, liability, or termination terms were added
• Whether customer data may be used to train, fine-tune, evaluate, or improve AI models
• Whether data may be shared with affiliates, vendors, or third parties
• Whether the customer can opt out of AI training or withdraw consent
• Whether customer data is anonymized, aggregated, retained, or deleted
• Whether the provider obtains rights to use customer prompts, outputs, content, or usage data
• Whether the provider disclaims responsibility for confidentiality, security, or model-generated results

AI Training and Data-Use Review

No conclusion can be reached regarding AI-model training because the relevant added language was not provided. The key terms to look for include:

• “train,” “fine-tune,” “improve,” or “develop” models
• “customer data,” “content,” “inputs,” “prompts,” or “outputs”
• “de-identified,” “aggregated,” or “anonymized” data
• “service improvement” or “product development”
• Opt-out, consent, or data-deletion rights
• Disclosure to subprocessors or third-party AI providers
• Ownership or licensing rights in customer content

Information Needed

Please provide the actual diff, including the text inside {}, [], and []{}. Without that language, a substantive legal-risk analysis would be speculative.

Summary of Important Changes

1. AI and customer-data training

• The diff adds substantial AI-related marketing language, including references to:
• “AI agents”
• “accurate, relevant data”
• “gen AI”
• an “AI-ready platform”
• AI-related products and solutions.
• However, the diff does not clearly add an express provision stating that customer data, submitted content, prompts, outputs, or other user information may be used to train AI models.
• It also does not clearly state that MongoDB will not use customer data for model training. The applicable privacy policy, product-specific terms, and service agreements should therefore be reviewed separately.
• Marketing references to AI products should not be treated as a contractual restriction or authorization concerning training.

2. Broad license for submitted content

The terms continue to provide MongoDB with a perpetual, irrevocable, worldwide, royalty-free, non-exclusive license to content submitted by users. The excerpt does not fully specify all permitted uses in the revised text.

Risk

This license is potentially broad enough to permit extensive use, reproduction, modification, or distribution of submitted content, depending on the omitted continuation of the clause. Customers should confirm whether “submitted content” includes:

• Prompts and AI interactions;
• Uploaded files or datasets;
• Customer confidential information;
• Personal data;
• AI-generated outputs; and
• Data submitted through MongoDB products rather than only the public website.

The license should not be assumed to be limited to service delivery or excluded from analytics, product development, or AI training unless the relevant terms say so expressly.

3. Website terms can be changed unilaterally

The revision states that MongoDB may modify all or part of the Terms of Use from time to time without notice. Continued use after the updated terms are published constitutes binding acceptance.

Risk

• Customers may become bound by material changes without direct notice.
• There is no apparent grace period or affirmative acceptance requirement.
• Users who do not accept future changes must immediately stop using the website.

4. Intellectual-property and content-use provisions

The revised text reorganizes the copyright, trademark, and software provisions and clarifies that:

• MongoDB or third parties own website content and trademarks.
• Use of trademarks requires prior written consent.
• Website content may generally be displayed, downloaded, and printed only for personal, educational, and non-commercial purposes, without redistribution or alteration.
• Downloaded software remains subject to its applicable end-user license agreement.

These provisions may restrict commercial copying, redistribution, scraping, data mining, and reuse of website materials.

5. Liability and warranty position

The revised language preserves prominent disclaimers that content and services are provided “AS IS” and “AS AVAILABLE,” with use at the user’s risk, and retains an aggregate liability limitation.

Key action

Obtain and review the current Privacy Policy, product/service terms, AI-specific terms, and data-processing agreement to determine whether customer data may be used for AI training and whether opt-out, deletion, confidentiality, or data-isolation protections apply.

Summary of Important Changes

1. AI and chatbot data use

• The revised policy expressly adds processing for “AI chatbots and assistants on MongoDB properties.”
• The listed data categories include:
• Identifiers;
• Technical information;
• Internet or electronic network activity;
• Profile information; and
• Chatbot inputs and outputs, which may contain personal data.
• MongoDB states that this processing is based on its legitimate interests, although chatbot interaction is described as entirely optional.
• Chatbot data may be disclosed to affiliates and service providers. The policy does not identify those providers, specify where AI processing occurs, or explain how long chatbot inputs and outputs are retained.

AI-model training risk

• The diff does not expressly state that customer data, chatbot inputs, outputs, or Product data will be used to train, fine-tune, evaluate, or improve AI models.
• It also does not expressly prohibit such use. The broad purposes of:
• operating AI chatbots and assistants;
• improving Products, websites, analytics, customer relationships, and experiences; and
• creating and disclosing Anonymous Data at MongoDB’s discretion

could potentially support model development or evaluation, depending on how MongoDB interprets those provisions.

• “Anonymous Data” is created by excluding information such as names and email addresses. This is not necessarily the same as technically irreversible anonymization; residual or indirect re-identification risks may remain.
• Customers should seek a contractual clarification that their content and Product data will not be used to train or improve general-purpose or third-party AI models, unless expressly authorized.

2. Expanded and clarified data-sharing provisions

• The policy continues to permit sharing with affiliates, service providers, and third-party companies.
• Third-party disclosures expressly include targeted advertising, direct marketing, and other commercial purposes.
• Service-provider restrictions state that providers may not disclose Personal Data except to provide services requested by MongoDB, but the AI-specific provider safeguards are not detailed.

3. U.S. privacy-law updates

• The policy is reorganized to incorporate the California Consumer Privacy Act as amended by the California Privacy Rights Act and other U.S. state privacy laws.
• It adds or clarifies rights to access, correct, delete, restrict, object to processing, obtain portability, withdraw consent, and opt out of certain sharing.
• A DPO contact email, telephone number, and deletion-request webform are provided.
• The policy states that MongoDB does not collect CCPA-defined Sensitive Personal Information and does not “sell” personal information, but may engage in “sharing” for cross-context behavioral advertising.

4. Other notable changes

• The revised policy clarifies that it supplements, rather than overrides, other privacy notices and fair-processing notices.
• Accessibility commitments and related contact details are added.
• The diff appears heavily affected by website-navigation/content extraction, so the clean, final policy should be reviewed to confirm that headings and operative clauses have not been accidentally intermingled.

Summary

The provided diff states only:

> “Added approximately 159 words to the document”

It does not include the actual added, deleted, or replaced legal language. As a result, the substantive changes and their legal effects cannot be reliably analyzed.

AI Training and Customer Data

• No specific language is provided addressing:
• Whether customer data may be used to train, fine-tune, or improve AI models;
• Whether customer prompts, inputs, outputs, or uploaded content are retained;
• Whether data is anonymized, aggregated, or shared with third parties;
• Whether the customer can opt out of model training;
• Whether training use applies by default or requires consent; or
• Whether the provider may use data to develop products or services.

Accordingly, it is not possible to determine whether the document expands, restricts, or otherwise changes the provider’s rights to use customer data for AI training.

Other Legal Risks

The actual 159-word addition could potentially affect important issues such as:

• Confidentiality and privacy obligations;
• Intellectual-property ownership or licensing;
• Data retention and deletion;
• Security responsibilities and breach notification;
• Indemnification and liability limitations;
• Regulatory compliance; or
• Customer termination or opt-out rights.

However, no conclusion can be reached without the text of the change.

Required Information

Please provide the actual diff, including the words shown in {additions}, [deletions], and []{replacements}. Without that language, a meaningful legal comparison is not possible.

Summary

The supplied diff does not include the actual amended legal language. It only states:

> “Added approximately 236 words to the document”

As a result, it is not possible to identify the substantive legal changes, new risks, or whether the customer’s data may be used to train AI models.

AI Training and Data Use

No text was provided addressing any of the following:

• Whether customer data may be used to train, fine-tune, or improve AI or machine-learning models.
• Whether inputs, outputs, prompts, metadata, or usage information may be retained.
• Whether data may be shared with affiliates, service providers, or third-party AI providers.
• Whether customer data will be anonymized, aggregated, or de-identified before use.
• Whether customers can opt out of AI training or request deletion of training-related data.
• Whether the provider claims ownership or license rights over customer data or outputs.
• Whether confidentiality, security, or data-protection obligations apply to AI processing.

Limitations

Because the added 236 words and any deleted or replaced language are not shown, no reliable comparison can be made. The actual redline—using {additions}, [deletions], and []{replacements}—is needed for a meaningful legal-risk analysis.

Summary of Important Changes

1. No identifiable AI-training or model-development provision

The diff does not appear to add, remove, or modify a clause expressly stating that customer or website-submitted data may be:

• used to train, fine-tune, or evaluate AI models;
• used to improve machine-learning systems;
• shared with AI providers or subprocessors for model development; or
• retained in datasets, embeddings, prompts, outputs, or other AI artifacts.

Although the revised website prominently uses AI-related marketing language—such as “AI agents,” “gen AI,” “AI-ready platform,” and “Artificial Intelligence”—these appear to be navigation and promotional content rather than operative contractual permissions.

Risk: The absence of an explicit AI-training restriction or prohibition leaves the separate Privacy Policy, product terms, data-processing terms, and service-specific documentation as the likely sources governing whether customer data can be used for AI purposes. Those documents should be reviewed separately.

2. Website terms can continue to change without notice

The revised language states that MongoDB may modify all or part of the Terms of Use “from time to time without notice,” and that continued use after the updated terms are published constitutes binding acceptance.

It also states that users who no longer accept the Terms must immediately stop using the website.

Risk: Users may be bound by revised terms without individualized notice or affirmative acceptance. This is particularly important if the website terms are relied upon for access to content, software, or other services.

3. Website content license and copying rules remain restrictive

The revised text continues to provide that MongoDB either owns the intellectual-property rights in website content or has permission to make it available. It prohibits copying or redistribution without written permission, while allowing limited personal, educational, and non-commercial downloading or printing subject to conditions such as preserving notices and not altering the information.

The revised trademark language also states that MongoDB or third parties own displayed marks and that use requires prior written consent.

Risk: Commercial reuse, automated extraction, data mining, republication, or incorporation of website materials into AI datasets or products may be prohibited unless separately authorized.

4. Other changes are largely editorial or formatting-related

Several changes correct punctuation, capitalization, quotation marks, and headings. The diff also contains extensive apparent website-navigation and formatting substitutions, making it difficult to determine whether every displayed change reflects the operative Terms.

Recommended follow-up

Review the current Privacy Policy, applicable product/service terms, and any AI-specific data terms for the actual rules on customer-data use, retention, sharing, and model training.