Densify

Summary

Scope of the Change

• The diff states that approximately 125 words were removed from the document.
• No specific deleted language or replacement language is provided.

AI Training and Customer Data

• No determination can be made about whether the document’s treatment of customer data and AI model training changed.
• The deleted language could potentially have addressed:
• Whether customer data may be used to train, fine-tune, or improve AI models;
• Whether data is used in aggregated, anonymized, or identifiable form;
• Whether customer content is retained after services end;
• Whether human reviewers or service providers may access customer data;
• Whether the customer can opt out of AI training;
• Ownership of inputs, outputs, or model improvements; or
• Security, confidentiality, and deletion obligations.

Potential Legal Risks

• If the removed text previously restricted AI training or required customer consent, its deletion could broaden the provider’s rights to use customer data.
• If the removed text previously disclosed or limited data retention, access, or sharing, deleting it could reduce transparency and customer protections.
• Conversely, the deletion could remove language that was unfavorable to the customer, such as a broad provider license or consent to use data.
• Because the actual wording is unavailable, it is not possible to determine whether the change is favorable, unfavorable, or merely editorial.

Recommended Review

• Obtain the complete redline showing the exact deleted 125 words and any surrounding provisions.
• Compare the deletion against provisions concerning:
• Data use and licensing;
• AI training and model improvement;
• Confidentiality and security;
• Data retention and deletion;
• Subprocessors and third-party disclosures; and
• Ownership of inputs, outputs, and derived data.
• Until the deleted text is reviewed, treat the change as an unresolved data-use and AI-governance risk.

Summary

The diff only states that approximately 125 words were added; it does not include the actual added language or identify where it appears in the agreement.

Key Legal Changes

• Cannot be determined: The substance, scope, and legal effect of the additions cannot be assessed without the new text.
• No confirmed changes identified: It is not possible to determine whether the additions modify:
• Customer data ownership or licensing rights
• Permitted uses of customer data
• Data retention or deletion obligations
• Confidentiality or security requirements
• Sharing with affiliates or third parties
• Liability, indemnification, or compliance obligations
• Termination rights or post-termination data handling

AI Training and Model-Use Provisions

The supplied diff does not reveal whether customer data may be:

• Used to train, fine-tune, test, or improve artificial intelligence or machine-learning models
• Used to create aggregated, anonymized, or de-identified datasets
• Retained for model development after account termination
• Shared with AI providers, subprocessors, or other third parties
• Excluded from training by default or only excluded if the customer opts out
• Used to generate outputs, embeddings, analytics, or other derived data

Risk Assessment

No reliable risk assessment can be made from the information provided. The actual 125 words are necessary to determine whether the change expands the provider’s rights to use customer data, weakens confidentiality protections, or creates new obligations for the customer.

Information Needed

Please provide the text of the additions, ideally with the surrounding unchanged provisions and any deleted or replaced language. This is particularly important for terms such as “train,” “improve,” “develop,” “fine-tune,” “machine learning,” “AI,” “models,” “aggregated,” “de-identified,” “service data,” or “customer data.”

Summary of Changes

Scope of the Diff

• The diff states only that approximately 125 words were removed.
• The actual deleted language is not provided.
• No additions, replacements, or specific deleted provisions are identified.

Legal and Commercial Impact

Because the removed text is unavailable, it is not possible to determine:

• Which contractual rights or obligations changed.
• Whether liability, indemnity, confidentiality, security, intellectual property, termination, or payment terms were affected.
• Whether any protections, limitations, disclosures, or customer obligations were removed.
• Whether the deletion creates ambiguity or shifts risk between the parties.

Customer Data and AI Training

The available diff does not identify any change concerning:

• Whether customer data may be used to train, fine-tune, evaluate, or improve AI models.
• Whether prompts, inputs, outputs, usage data, or personal information may be retained or shared for model development.
• Whether customer data is excluded from training by default or only upon opt-out.
• Whether de-identified, aggregated, or derived data may be used for AI-related purposes.
• Ownership or licensing rights in customer data, outputs, or trained-model artifacts.
• Security, deletion, confidentiality, or subprocessors relating to AI training.

However, because approximately 125 words were removed, an AI-training restriction or disclosure could have been deleted. This cannot be confirmed without the actual redlined language.

Risk Assessment

Current assessment: Indeterminate / requires the underlying text.

The deletion-only description is insufficient to assess whether the amendment:

• Expands the provider’s ability to use customer data;
• Removes a prohibition or consent requirement for AI training;
• Reduces confidentiality or data-protection protections; or
• Merely removes redundant or administrative language.

Recommended Follow-Up

Obtain the actual deleted wording and compare it with the prior version, specifically searching for terms such as:

train, training, fine-tune, improve, develop, machine learning, artificial intelligence, models, inputs, outputs, usage data, aggregated, de-identified, retain, and customer data.

Summary of Important Changes

1. Broader and More Specific Data-Use Purposes

The policy replaces general language about using personal information to operate the business with more detailed purposes, including:

• Personalizing the customer’s experience.
• Understanding how customers use the services and online resources.
• Improving websites, products, offerings, and services.
• Using customer feedback to improve products and services.
• Responding to inquiries, questions, and requests.
• Sending communications, updates, company news, and information about related products or services.

Risk: The revised purposes are broader and may permit more extensive profiling, analytics, product development, and marketing based on customer information.

2. Changes to Third-Party Sharing

The prior language stated that information could be shared with third-party service providers for limited business purposes, provided the customer had consented. The revised language states that Kubex may use or share information with third parties for operational and administrative purposes, while retaining a general statement that Kubex does not sell, trade, or rent personal data.

Risk: The revised wording is less precise about the limits imposed on third parties and may make it less clear whether service providers can use the information for their own purposes. Vendor contracts should expressly prohibit independent use, sale, disclosure, or model training unless separately authorized.

3. Marketing Communications and Consent

The revised policy expressly permits use of contact information to send communications and updates. It also adds an unsubscribe link requirement for future emails and describes the types of communications customers may receive.

The revised consent language states that customers provide “additional consent” when they select “I consent,” submit a form, opt in at an event, or use a designated consent form.

Risk: Consent mechanisms are described broadly and may combine service communications with marketing communications. The policy should clearly distinguish legally required or transactional communications from optional marketing and explain how consent can be withdrawn.

4. Security and Data-Management Language

Security provisions are expanded to refer to:

• Protection against unauthorized access, alteration, disclosure, destruction, and misuse.
• Restricted personnel access.
• Servers and backups.
• Firewalls and redundant security systems.
• Periodic evaluation and upgrading of security practices.
• A link to additional security information.

Risk: These statements may create expectations or representations about security controls. Kubex should ensure the referenced practices are accurate and consistently implemented.

5. Access and Deletion Rights

The revised text continues to allow customers to request review of their data and deletion, but the wording and contact process are reorganized. Requests are directed to a privacy email address.

Risk: The policy should specify applicable exceptions, verification requirements, response timelines, and whether deletion is subject to legal, security, or backup-retention obligations.

6. AI-Training Use

No express language authorizes or restricts using customer data, prompts, feedback, outputs, or personal information to train, fine-tune, evaluate, or improve AI models.

Although the revised references to “understand how you use,” “improve” services, and use feedback could potentially be interpreted broadly, they do not clearly disclose AI-model training. This ambiguity is a material risk. If AI training is intended, the policy should expressly identify the data involved, purposes, retention, de-identification, sharing, opt-out rights, and whether third-party AI providers may receive the data.

Executive Summary

The revised language substantially reorganizes and expands the privacy policy. It adds more detailed statements about data sharing, security, user controls, consent, policy updates, and acceptance of terms. It does not expressly authorize using customer data to train, fine-tune, evaluate, or improve AI models.

Important Changes and Risks

1. Third-party sharing is reframed

• The policy now states that Kubex does not “sell, trade, or rent” personal data.
• It replaces the prior general description of using information to understand service usage and improve offerings with language allowing third-party service providers to help operate the business and administer activities such as email.
• Sharing is stated to be for “limited purposes only,” but the providers, data categories, retention periods, and contractual restrictions are not identified.

Risk: The scope of “help us operate our business” is broad and may permit substantial processing by vendors. The policy does not clearly state whether vendors may use data for their own purposes.

2. Consent language is expanded and made more prominent

The revised text states that users explicitly consent to Kubex collecting and “leveraging” personally identifiable information when they:

• Select “I consent”;
• Submit a form in the Privacy Policy section of webforms;
• Opt in at an event; or
• Consent through a designated Kubex consent form.

Risk: “Leveraging” is undefined and could be interpreted broadly. Consent obtained through forms or events may not clearly explain the specific purposes, particularly if sensitive data or automated processing is involved. The language also risks treating general website use or form submission as broad consent.

3. Security disclosures are more detailed

The revision adds commitments concerning:

• Appropriate collection, storage, and processing practices;
• Restricted physical and digital access;
• Secured servers and backups;
• Firewalls and redundant security systems;
• Periodic evaluation and upgrades.

It also directs users to kubex.ai/security.

Risk: These statements may create expectations or representations about security controls. They do not specify breach-notification obligations, encryption standards, retention periods, or whether the measures apply to third-party providers.

4. User rights and communications

The revised policy adds the ability to:

• Manage email subscriptions;
• Update personal data;
• Request access to data; and
• Request deletion by contacting privacy@kubex.ai.

Risk: The process, verification requirements, response deadlines, legal exceptions, and scope of deletion are not explained.

5. Unilateral policy updates and acceptance

Kubex may update the policy at any time and encourages users to check the privacy page. Users are said to be responsible for reviewing changes, and website use constitutes agreement to the terms.

Risk: This may provide weak notice of material changes and may not substitute for legally required notice or renewed consent where processing purposes materially change.

AI-Training Analysis

No provision in the diff expressly permits customer data, personal data, prompts, inputs, outputs, feedback, or submitted content to be used to train, fine-tune, evaluate, or improve AI models. The new references to “leveraging” information and improving the user experience are ambiguous but should not be treated as clear AI-training authorization. A separate, explicit AI-data-use provision would be advisable if such processing is intended.

Summary

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

> “Added approximately 125 words to the document”

Accordingly, it is not possible to determine what legal terms changed or whether the additions create new risks.

AI Training and Data Use

No language is provided addressing whether the customer’s data may be:

• Used to train, fine-tune, or improve AI models;
• Combined with other customers’ data for model development;
• Reviewed by personnel or used for human feedback;
• Retained after termination for training or analytics;
• De-identified or anonymized before use;
• Used to train shared, public, or vendor-specific models; or
• Excluded from AI training unless the customer opts in or opts out.

The actual 125-word addition is required to assess these issues.

Other Potentially Important Changes

The missing text could also affect:

• Data ownership and license rights;
• Confidentiality obligations;
• Security and privacy commitments;
• Customer deletion and retention rights;
• Service-provider or subcontractor access;
• Liability, indemnification, and regulatory compliance; and
• The customer’s ability to terminate or restrict data processing.

Conclusion

No substantive legal change can be identified from the information provided. The full text of the addition, including any surrounding language affected by it, should be supplied for a meaningful risk analysis.

Key Changes and Risks

1. AI-model training

• No express reference to AI, machine learning, model training, model improvement, prompts, or customer-content training appears in the diff.
• The revised language does add broad consent to collect and “leverage” personally identifiable information to “enhance your experience,” but it does not clearly authorize using customer data to train AI models.
• The absence of an AI-training provision creates ambiguity: the policy does not state whether customer data, submitted content, feedback, or usage data may be used for training, fine-tuning, testing, evaluation, or improving AI systems.
• If Kubex uses customer data for AI training, a separate, specific disclosure and consent mechanism may be advisable, particularly for sensitive or confidential information.

2. Broader third-party use and sharing

• The purpose of using information changes from understanding service usage and improving websites/services to using third-party service providers to help operate the business and administer activities, including email.
• The revised text permits sharing information with those providers for “limited purposes,” but does not identify the providers, specify data categories, impose detailed contractual restrictions, or explain retention/deletion obligations.
• The prior limitation that sharing required the customer to have provided feedback appears to be replaced with a broader consent-based framework.

3. New consent mechanism

• The revision adds express language that users consent to Kubex collecting and leveraging personally identifiable information when they:
• select “I consent”;
• submit a form in the Privacy Policy section of webforms;
• opt in at an event; or
• consent through a designated Kubex consent form.
• This may create a stronger legal basis for data collection, but the scope of “enhance your experience” and “leverage” is broad and potentially unclear.
• The consent language does not clearly distinguish necessary processing from optional marketing, analytics, personalization, or AI-related processing.

4. Security disclosures

• The revision adds descriptions of security controls, including restricted personnel access, secure servers and backups, firewalls, redundant security systems, periodic evaluation, and upgrades.
• These statements may create expectations or representations that could increase liability if actual security practices differ.
• The new wording appears to address security generally but does not provide breach-notification commitments, specific retention periods, encryption standards, or international-transfer safeguards.

5. User rights and marketing controls

• The revision adds or clarifies the ability to manage email subscriptions, update personal data, request access to data, and request deletion.
• It provides an unsubscribe mechanism through emails and webpages and identifies privacy@kubex.ai for privacy inquiries.
• These rights are stated generally and may not describe applicable legal limits, response timelines, identity verification, or exceptions to deletion.

6. Policy updates and acceptance

• Kubex may update the policy at any time and encourages users to review the privacy page periodically.
• Responsibility for becoming aware of changes is shifted to the user, without a clear requirement for direct notice.
• The revision states that website use constitutes acceptance and adds consent language tied to forms, events, and designated consent documents. This may blur the distinction between notice, contractual acceptance, and legally valid privacy consent.

Summary

The diff only states that approximately 125 words were added, but does not include the actual added language.

AI Training and Data Use

• No substantive wording is provided concerning:
• Whether customer data may be used to train, fine-tune, or improve AI models.
• Whether prompts, inputs, outputs, personal information, or confidential information are retained.
• Whether customer data is shared with third-party model providers.
• Whether data is anonymized, aggregated, or de-identified before use.
• Whether the customer can opt out of AI training or request deletion.
• Whether any training-related use is limited to a particular service, purpose, or duration.

Legal and Commercial Risks

Because the added text is not included, it is not possible to identify:

• New permissions to use or disclose customer data.
• Changes to confidentiality, privacy, security, or intellectual-property rights.
• Expanded rights to retain or reuse customer content.
• New obligations imposed on the customer.
• Changes to liability, indemnification, audit, or regulatory-compliance provisions.

Conclusion

The actual 125-word addition is required for a meaningful legal analysis. Based on the information provided, no conclusion can be drawn about whether customer data may be used to train AI models or whether the contract creates any new related risks.

Executive Summary

The revised language substantially restructures the privacy notice, replacing broad statements about personalization, product improvement, communications, and feedback with a more limited—but still significant—description focused on service providers, security, consent, and user rights. It does not expressly state that customer data will be used to train AI models. However, it also does not prohibit such use or define whether “leveraging” personal information includes AI training, model improvement, profiling, or automated decision-making.

Important Changes

1. New restrictions and disclosures regarding third parties

• The policy now states that Kubex does not “sell, trade, or rent” personal data.
• It expressly permits sharing information with third-party service providers to:
• Help operate the business; and
• Perform activities such as sending email.
• Sharing is described as being for “limited purposes only,” subject to the user having given consent.

Risk: The third-party limitation is not detailed. The policy does not identify categories of providers, explain whether providers may retain or reuse data, address international transfers, or state whether providers may use data to train their own AI systems.

2. Consent language is more prominent and potentially broader

The revised policy says users provide “additional consent” to Kubex collecting and “leveraging” personally identifiable information when they:

• Select “I consent”;
• Submit a form in the Privacy Policy section of webforms;
• Opt in at an event; or
• Consent through a designated Kubex form.

Risk: “Leveraging” is undefined and could be interpreted broadly. The policy does not clearly distinguish consent for providing the service from consent for marketing, analytics, personalization, product development, or AI-related processing. Consent obtained through form submission or events may also be challenged if it is not sufficiently specific, informed, and freely given.

3. Removal or narrowing of stated business purposes

The prior language expressly referred to:

• Personalizing the user’s experience;
• Understanding service usage;
• Improving websites, offerings, and services;
• Using customer feedback to improve products and services; and
• Sending communications and updates.

Much of this wording is deleted or replaced with general operational language.

Risk: The revised policy may provide less transparency about actual processing activities, while the broad “leveraging” language could preserve flexibility without clearly explaining purposes.

4. Security disclosures added, but largely general

The revision adds statements concerning:

• Authorized access to servers and data;
• Secure backups;
• Firewalls and redundant security systems;
• Periodic evaluation and upgrades; and
• A link to Kubex’s security page.

These statements may create expectations regarding security practices but do not provide breach-notification commitments, retention periods, encryption standards, or specific safeguards.

5. User controls and policy updates

The revision adds rights to request data review or deletion and manage email subscriptions. It also states that Kubex may update the policy at any time and places responsibility on users to review changes.

Risk: It does not explain verification procedures, response timelines, legal limits on deletion, or whether changes apply to data already collected.

AI Training Assessment

No express authorization for using customer data to train, fine-tune, evaluate, or improve AI models appears in the diff. Conversely, there is no express prohibition. The undefined terms “leveraging” and “enhance your experience” create ambiguity and should be clarified if AI processing is contemplated.

Summary

The provided diff does not include the text of the approximately 125 added words. It only states that material was added, so the legal effect of the changes cannot be determined.

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;
• Used to develop products or services;
• Shared with AI providers or other third parties;
• Anonymized, aggregated, or retained for model-training purposes;
• Excluded from training by default or only excluded upon customer request; or
• Used to train models after termination of the agreement.

Because the added language is unavailable, it is not possible to determine whether the contract introduces a new customer-data training right, expands an existing right, or imposes restrictions on such use.

Other Potential Legal Changes

The missing text could also affect:

• Data ownership and licensing rights;
• Confidentiality obligations;
• Data retention and deletion;
• Security and privacy responsibilities;
• Use of subprocessors or third-party AI providers;
• Customer consent requirements;
• Liability, indemnification, and regulatory compliance; and
• The customer’s ability to opt out or terminate.

Conclusion

No reliable legal-risk assessment can be made from the information supplied. The actual 125-word addition, including any surrounding language needed to understand its context, should be provided for analysis.

Key Changes and Legal Risks

1. New express consent to collect and use personal information

• The revised language states that users give Kubex “additional consent” to collect and leverage personally identifiable information to enhance their experience.
• Consent may be given by:
• Selecting “I consent”;
• Submitting a form containing a privacy-policy section;
• Opting in at an event; or
• Using a designated Kubex consent form.
• This replaces broader language suggesting that consent was implied by providing information or feedback.

Risk: The scope of “enhance your experience,” “collecting,” and “leveraging” personally identifiable information is not clearly defined. The language may be insufficiently specific for jurisdictions requiring informed, purpose-specific consent. It also appears to combine privacy-policy acceptance with consent, which may create issues where consent must be freely given and separable from general terms.

2. Removal or narrowing of stated business purposes

The prior policy described use of information to:

• Personalize the customer’s experience;
• Understand use of services and online resources;
• Improve websites, products, offerings, and services;
• Use customer feedback; and
• Communicate with customers.

These specific purposes are largely replaced by general statements that third-party providers may help Kubex “operate our business” and administer activities such as email.

Risk: The revised language is less transparent and potentially broader because “operate our business” is vague. It may make it harder for customers to understand or challenge particular uses of their data.

3. Third-party sharing language revised

The policy now states that Kubex does not sell, trade, or rent personal data. It may share information with third-party service providers for limited business purposes, provided the user has consented.

Risk: The policy does not identify the categories of providers, whether they may retain or reuse data, or whether data may be transferred internationally. “Limited purposes” is not clearly tied to a detailed list of purposes.

4. Security disclosures expanded

New language describes:

• Restricted physical and digital access;
• Secure servers and backups;
• Firewalls and redundant security systems;
• Periodic evaluation and upgrades; and
• Additional security information at kubex.ai/security.

Risk: These statements may create contractual or regulatory expectations. If security practices do not consistently match the promises, Kubex could face misrepresentation or consumer-protection claims.

5. Data-management rights added or clarified

Customers may manage subscriptions, update personal data, request review of their data, and request deletion. An unsubscribe link is promised in emails and webpages.

Risk: The policy does not explain verification procedures, response timelines, legal exceptions, or whether deletion applies to backups and third-party providers.

6. AI-model training

No express authorization to use customer data to train, fine-tune, evaluate, or improve AI models appears in the provided diff. However, the new broad “collecting and leveraging personally identifiable information” language could be argued to encompass AI-related uses unless restricted elsewhere.

Recommendation: Add a separate, explicit provision stating whether customer data, prompts, outputs, feedback, or personal information may be used for AI training, identifying the data categories, purposes, retention, opt-out/consent mechanism, and whether data is de-identified.

No

Summary of the Diff

The diff states only that approximately 125 words were removed from the document. The specific deleted language is not provided.

AI Training and Customer Data

• It is not possible to determine whether the deleted language addressed:
• Whether the customer’s data may be used to train, fine-tune, or improve AI models;
• Whether prompts, inputs, outputs, or usage data may be retained or reviewed;
• Whether data is anonymized, aggregated, or shared with third parties;
• Whether the customer can opt out of AI training;
• Ownership or licensing rights in customer data or AI-generated outputs; or
• Security, confidentiality, or deletion obligations relating to AI systems.

• If the removed language restricted the provider’s use of customer data for AI training, its deletion could materially expand the provider’s rights or create ambiguity about permitted data use.

• Conversely, if the removed language authorized AI training or data sharing, its deletion could reduce those rights or provide the customer with greater protection.

Other Potential Risks

Because the deleted text is unavailable, it is also impossible to assess whether the amendment changes:

• Liability limitations or indemnities;
• Confidentiality obligations;
• Data protection and privacy compliance;
• Data retention or deletion periods;
• Intellectual property ownership;
• Service levels or termination rights; or
• Customer audit or regulatory rights.

Overall Assessment

The change cannot be reliably evaluated based solely on the statement that approximately 125 words were removed. The legal effect depends entirely on the content and location of the deleted language. The parties should obtain a complete redline or the prior and revised versions before approving the amendment, with particular attention to any provisions concerning customer data, model training, data retention, confidentiality, and intellectual property.

No

No

Executive Summary

The revision substantially reorganizes the privacy-policy provisions but does not expressly address use of customer data to train, fine-tune, evaluate, or improve AI models. Any AI-training permission is therefore not clearly granted or restricted by this diff.

Key Changes and Risks

1. Broader and less specific use descriptions

The policy changes from using third-party providers to “help us operate our business” and send email to using information to:

• Understand how users interact with services and online resources;
• Improve websites, offerings, and services;
• Use customer feedback to improve products and services; and
• Personalize the user experience.

Risk: “Improve” and “personalize” are broad purposes. Although they do not expressly authorize AI training, they could be interpreted as supporting analytics, automated systems, or product-development activities. The policy should state expressly whether customer content, prompts, usage data, or feedback may be used for model training or evaluation.

2. Change in third-party sharing language

The former limitation—sharing information with third parties only for specified purposes, provided the user consented—is replaced or reframed as Kubex using information for the listed purposes. The policy still states that Kubex does not sell, trade, or rent personal data and retains language permitting sharing with third parties where the user has given consent.

Risk: The revised wording is less precise about the role, scope, and obligations of service providers. It does not clearly identify whether vendors may use data for their own purposes, retain it, or use it to train their models.

3. Marketing communications

Contact information may be used to send communications and updates relating to the user’s interests. The policy adds an unsubscribe link within each email.

Risk: “Pertaining to your interests” may permit broader marketing than the prior consent-based language. The policy should distinguish transactional/service communications from promotional communications and identify the legal basis and consent mechanism where required.

4. Security provisions relocated and expanded

Security language is moved into a dedicated section and now describes safeguards against unauthorized access, alteration, disclosure, destruction, and misuse. It references physical and digital access controls, backups, firewalls, redundant systems, and periodic evaluation/upgrades, with a link to Kubex’s security page.

Risk: These are general commitments, not guarantees or detailed security obligations. The external security page may change independently unless incorporated contractually.

5. Data-access and deletion rights

The policy continues to permit users to request review of their data and request deletion, now directing requests to privacy@kubex.ai.

Risk: The deletion language does not state exceptions, response deadlines, verification procedures, or whether data in backups, logs, or model-training datasets will actually be deleted.

6. Policy updates and acceptance

Users are told to monitor the privacy policy for changes, and website use constitutes agreement. The policy also describes consent through forms, events, or selecting “I consent.”

Risk: This may permit important changes through notice rather than affirmative re-consent. Consent is not clearly separated by purpose.

AI-Training Conclusion

No express AI-training authorization, prohibition, opt-out, retention rule, or deletion mechanism appears in the diff. This omission creates material ambiguity and should be addressed directly.