logz

Structured Summary of Important Changes

1. Consent and Privacy-Request Features

• The consent notice now includes additional placeholders for:
• A data-subject request (DSR) form URL (#DSR_FORM_URL_TEXT#), potentially improving access to rights-request mechanisms.
• Global Privacy Control (GPC) banner and notification text (#GPC_BANNER_ICON#, #GPC_TOAST_TEXT#).
• Consent selections and category details, including “Necessary,” “Preferences,” “Statistics,” and “Marketing.”
• The notice appears to support cross-domain consent, with placeholders identifying the number and list of domains to which consent applies.
• The revised notice includes additional Cookiebot/IAB Transparency and Consent Framework placeholders covering purposes, features, legitimate interests, and partners.

Risk: These are largely template-driven changes. Their legal effectiveness depends on whether the placeholders are populated correctly, whether GPC signals are honored automatically, and whether consent is genuinely granular, informed, and withdrawable.

2. Expanded or Changed Tracking Technologies

• The declaration adds, removes, or changes numerous cookies and storage technologies involving:
• Logz.io
• Amazon
• LinkedIn
• Microsoft
• Google
• ZoomInfo
• Wistia
• Spotify/Anchor
• Twitter/X
• Cloudflare
• Marketo, HubSpot, Calendly, and other providers
• Several technologies are newly described as supporting:
• Cross-site or multi-site visitor tracking
• Advertising personalization
• Marketing-campaign measurement
• CRM and event/product promotion
• Embedded-content interaction tracking
• A/B or multivariate testing
• Some technologies move between categories or have revised descriptions, including changes from statistical/analytics purposes to marketing or preference purposes.

Risk: Reclassification can affect the consent requirement. Marketing, behavioral advertising, cross-site tracking, and non-essential analytics generally require prior consent in many jurisdictions. The controller should verify that these technologies do not load before consent and that vendor disclosures are accurate.

3. Retention and Storage Changes

• Several items change from session-based storage to persistent storage.
• Some preference data is retained for 7 days, while certain identifiers remain persistent or are stored in HTML Local Storage or IndexedDB.
• New or revised device, installation, storage, and session identifiers appear.

Risk: Persistent identifiers and local storage may continue tracking after browser-session termination and may be harder for users to detect or delete. Retention periods and purposes should be justified, disclosed, and consistently enforced.

4. AI Model Training

• No express change addresses the use of customer or visitor data to train, fine-tune, evaluate, or improve AI models.
• The diff contains no clear authorization or prohibition concerning AI training, model development, or sharing data with AI providers.
• Analytics, marketing, interaction, and embedded-content data may nevertheless be collected under the revised cookie framework. If such data is later used for AI purposes, the current wording may not provide sufficiently specific notice or legal basis.

Risk: Confirm separately that the privacy policy, vendor terms, and data-processing agreements address AI training, including opt-out rights, data minimization, anonymization, retention, and third-party use.

Summary of Important Changes

1. Privacy Policy scope expanded

The policy now expressly covers:

• Individuals who visit or access the website;
• Customers and business partners who are licensed to access or use the services.

This is a meaningful expansion from a policy focused primarily on website visitors. It suggests the policy is intended to address customer-related personal data, but the excerpt does not explain what customer data is collected, how it is processed, retention periods, or the respective roles of Logz.io and its customers under data-protection laws.

Risk: Customers may need to determine whether the policy adequately supplements their agreement, data-processing addendum, or security terms. The excerpt does not clarify whether customer-submitted logs or service data are treated as customer-controlled data, company-controlled data, or both.

2. New or revised cookie-consent presentation

The updated content includes a more detailed consent interface with:

• “Allow all,” “Customize,” “Allow selection,” and “Deny” options;
• Separate categories for Necessary, Preferences, Statistics, and Marketing cookies;
• “Do not sell or share my personal information” language;
• Cross-domain consent functionality;
• Numerous advertising, analytics, tracking, and fraud-prevention cookies involving providers such as LinkedIn, Microsoft, Google, HubSpot, Marketo, Twitter/X, ZoomInfo, Wistia, Spotify, and others.

Risks:

• Extensive third-party tracking and marketing activity may involve international transfers and profiling.
• The policy should clearly identify the legal bases, purposes, recipients, retention periods, and opt-out mechanisms for each category.
• The presence of “Do not sell or share” language may create obligations under applicable U.S. state privacy laws.
• The diff contains duplicated entries and unresolved placeholders such as [#IABV2_TITLE#] and [#BULK_CONSENT_DOMAINS#], which could indicate an implementation or disclosure defect.

3. Increased AI and product-marketing content

The website now promotes:

• “OrionIQ”;
• An “agentic observability” platform;
• “AI Agent” functionality;
• “AI-powered Insights”;
• “AI-powered RCA” (root-cause analysis).

These additions appear to be marketing and navigation changes rather than contractual data-use provisions.

4. AI-model training implications

No express change was identified authorizing Logz.io to use customer data, logs, telemetry, prompts, outputs, or other service data to train AI models. The excerpt contains no language addressing:

• Training, fine-tuning, or evaluating AI models;
• Whether customer data is used to improve products or AI features;
• De-identification or aggregation;
• Human review;
• Customer opt-out rights;
• Ownership of inputs and outputs;
• Use of third-party AI providers.

Key risk: The new AI product references may create ambiguity if the operative terms elsewhere permit broad “service improvement” uses. The AI terms and customer agreement should be reviewed to confirm that customer data is not used for model training without clear notice, contractual authorization, and appropriate controls.

Summary

The provided diff only states:

> “Added approximately 3259 words to the document”

It does not include the actual added language, deleted language, or replacement text. As a result, it is not possible to reliably determine:

• What contractual terms changed;
• 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 new rights to retain, anonymize, aggregate, or commercialize data were added;
• Whether confidentiality, security, privacy, intellectual-property, or liability provisions changed;
• Whether the customer received any opt-out, deletion, or usage-control rights; or
• Whether the changes create new compliance or indemnification obligations.

AI-training analysis

No conclusion can be drawn about AI model training from the information provided. The statement that approximately 3,259 words were added does not reveal whether those additions:

• Permit use of customer content or personal data to train general-purpose or service-specific models;
• Limit training use to de-identified, aggregated, or anonymized data;
• Require customer consent or provide an opt-out;
• Allow human review or vendor access for model improvement;
• Grant the provider ownership or a broad license over inputs, outputs, or derived data; or
• Impose retention, deletion, or security safeguards.

Information needed

Please provide the actual redline text, including the added provisions and any surrounding sections. In particular, the following clauses would be important:

• Data use and processing;
• Artificial intelligence or machine learning;
• Confidentiality;
• Intellectual property and licenses;
• Privacy and security;
• Subprocessors and third-party services;
• Data retention and deletion; and
• Liability, indemnity, and compliance obligations.

Without the substantive text, any assessment of legal risk would be speculative.

Summary of Important Changes

1. Terms of Use substantially rewritten

The prior language focused on the customer providing “User Data” to Logz.io servers and Logz.io analyzing that data through the “Logz.io Platform.” The revised language instead states that the Terms of Use and any applicable Order Form govern use of Logz.io’s “various services.”

Key implications

• The contractual scope is broader and less tied to a specific platform.
• The revised language expressly covers use by the customer’s Authorized Users.
• The Order Form is now expressly incorporated into the governing contractual framework, which may create additional obligations or conflicts that must be reconciled with the online terms.
• The earlier reference to analyzing User Data remains conceptually relevant, but the revised structure appears to relocate or redefine that concept.

2. Services expanded to include APIs and MCP

The revised definition of “Services” expressly includes:

• Application programming interfaces (APIs); and
• Model Context Protocols (MCP) that Logz.io may make available.

This is a material expansion because MCP functionality may permit AI systems or connected tools to access, retrieve, process, or act on customer data. Customers should confirm:

• What data an MCP connection can access;
• Whether third-party tools or models receive the data;
• Who is responsible for configuring permissions and preventing unauthorized access; and
• Whether separate product terms or security requirements apply.

3. AI features added to the Logz.io Platform

The revised text states that the Logz.io Platform includes “AI features” and that those features may be offered to users. It also adds that use or misuse of AI Features will be subject to additional terms, although the excerpt is incomplete.

Risk

The change brings AI functionality within the contractual service scope but does not, in the provided text, explain:

• Whether customer data or prompts may be used to train, fine-tune, or improve AI models;
• Whether data is retained by Logz.io or third-party AI providers;
• Whether inputs or outputs are shared across customers;
• Whether customer data is anonymized or de-identified;
• Whether customers can opt out of model training; or
• Who owns AI-generated outputs.

4. AI-model training: no express authorization visible

The diff does not show an express provision authorizing Logz.io to use Customer Data to train general-purpose or other AI models. It also does not show an express prohibition on such use.

Accordingly, the revised inclusion of AI Features creates uncertainty rather than a clearly expanded training right. Customers should obtain written confirmation that Customer Data, prompts, logs, and outputs will not be used for model training or product improvement except as expressly authorized in the Order Form or a data-processing agreement.

5. Cookie and tracking changes

The cookie notice appears updated or re-rendered, with expanded references to advertising, analytics, and tracking providers, including Google, Microsoft, LinkedIn, HubSpot, ZoomInfo, Twitter/X, Vimeo, Spotify, Marketo, and others. It includes “Allow all,” customization, denial, “Do not sell or share,” and Global Privacy Control-related placeholders.

The cookie declaration is dated August 4, 2026, while the Terms are revised August 3, 2026. The increased third-party tracking ecosystem may create additional privacy, consent, international-transfer, and data-sharing obligations.

No

No

Summary of Changes

The diff only states that approximately 221 words were removed from the document. It does not identify which provisions were deleted or provide the replacement text.

Legal and Commercial Impact

Because the deleted language is not shown, it is not possible to determine reliably whether the changes:

• Reduce or expand either party’s rights or obligations;
• Remove warranties, indemnities, liability limitations, or termination rights;
• Change confidentiality, security, privacy, or data-retention obligations;
• Affect ownership or licensing of customer data, outputs, or intellectual property;
• Alter governing law, dispute resolution, payment terms, or service levels; or
• Shift risk from the provider to the customer.

The removal of text may itself be significant, particularly if the deleted provisions contained customer protections, compliance commitments, or restrictions on the provider’s use of data.

AI Training and Customer Data

No specific conclusion can be drawn about AI-model training from the information provided. The diff does not show whether any language was deleted concerning:

• Use of customer data to train, fine-tune, or improve artificial-intelligence or machine-learning models;
• Whether customer data may be used for product development, analytics, or service improvement;
• Whether data is aggregated, anonymized, or de-identified before use;
• Customer consent, opt-out, or objection rights;
• Restrictions on using customer content to train models serving other customers;
• Ownership of model inputs, outputs, or derived data; or
• Deletion of customer data from training datasets or model-related systems.

If the removed text previously prohibited or limited AI training, its deletion could materially expand the provider’s rights to use customer data. Conversely, if the deleted text authorized such use, its removal could improve the customer’s privacy position. The actual wording is required to assess this.

Recommended Next Step

Obtain the redlined text or the full “before” and “after” versions. The statement that 221 words were removed is insufficient to identify the legal effect or any change to AI-training rights.

Summary of Important Changes

1. Consent and privacy-rights functionality

• The consent banner now includes additional Cookiebot placeholders for:
• A data-subject request (DSR) form URL: [#DSR_FORM_URL_TEXT#]
• Global Privacy Control (GPC) banner and toast messaging: [#GPC_BANNER_ICON#] and [#GPC_TOAST_TEXT#]
• The number of cookies displayed in certain categories has changed, including:
• Necessary cookies: 49 to 50
• Statistics cookies: 20 to 19
• Unclassified cookies: 16 to 11
• A cross-domain consent section has been added or retained, allowing consent to apply across listed domains. The legal and operational scope of this feature depends on which domains are ultimately populated in [#BULK_CONSENT_DOMAINS#].

Risk: The GPC and DSR functionality appears to be template-based. If the placeholders are not correctly configured or connected to operational processes, the website may inaccurately represent users’ opt-out or data-access rights.

2. Cookie and tracking changes

The declaration substantially changes the listed cookies, storage technologies, descriptions, providers, and purposes. Notable changes include:

• Marketing and campaign-tracking cookies have been modified, including changes involving utm_campaign, utm_term, utm_content, and utm_medium.
• Several analytics and tracking entries have been reclassified or replaced with cookies and local-storage identifiers.
• Some storage periods changed from session-based or seven-day storage to persistent storage, including:
• Redux/local-storage website settings
• Spotify/Anchor-related caching
• Various local-storage identifiers
• A/B testing or multivariate-testing functionality is now described for utm_content, including changing website content to identify the best variation.
• Marketing descriptions now expressly refer to collecting preferences or interactions with web-campaign content for CRM, event, or product promotion.
• Additional or revised third-party providers and trackers appear, including Microsoft, LinkedIn, ZoomInfo, Twitter, Wistia, Google, Spotify/Anchor, and others.
• Some entries remain “pending,” “unclassified,” or have incomplete provider descriptions.

Risks:

• Persistent identifiers and expanded third-party tracking may increase profiling, cross-site tracking, and regulatory consent obligations.
• Reclassification of cookies between necessary, preference, statistics, marketing, and unclassified categories could affect whether prior consent remains valid.
• The declaration may be inaccurate or incomplete if cookies are set before consent, providers are omitted, or “pending/unclassified” items are not promptly classified.
• A/B testing and CRM-related tracking may involve behavioral profiling and should be clearly disclosed and appropriately consent-gated.

3. AI-model training

No express change concerning the use of customer or visitor data to train, fine-tune, evaluate, or improve AI models was identified in this diff. The changes concern cookie consent, analytics, advertising, CRM tracking, storage, and privacy-request functionality. They do not add an AI-training authorization, prohibition, or data-use limitation.

However, the expanded tracking and profiling disclosures could indirectly affect data supplied to analytics or marketing vendors. The underlying privacy policy and vendor terms should be reviewed separately for any AI-training rights.

Yes