clause.watch Contracts Recent changes Start monitoring

Monitored company

Feedier

clause.watch tracks 2 legal documents published by Feedier (feedier.com), re-reading each one every six hours. Below is what each document covers, in plain English.

Privacy Policy

1,212 characters · Read the original

We monitor this document. A plain-English summary has not been published for it yet.

Terms & Conditions

1,212 characters · Read the original

Site 436 — Document Overview

Important qualification

The supplied material does not appear to be a privacy policy, terms of service, or other legal agreement. It consists primarily of website CSS, a “404” error message, and JavaScript code that loads third-party analytics and tracking tools. It does not identify the site operator, provide contractual terms, or explain applicable law.

Accordingly, the document does not establish clear user rights or obligations. The conclusions below are limited to what can be inferred from the code.

1. Data Collection & Usage

The document does not expressly describe what personal information is collected or how it is used. However, the code contains several tracking or analytics integrations:

  • Ahrefs Analytics: A script is loaded from analytics.ahrefs.com using a site-specific data key.
  • Snitcher/Radar: A script is loaded from cdn.snitcher.com and configured to communicate with radar.snitcher.com. Snitcher-type services commonly support website visitor identification, lead generation, analytics, and organization-level tracking, although those purposes are not stated here.
  • Google-style data layer event: The code records a demo_form_submitted event when a particular HubSpot form is submitted.
  • Radar event framework: The code references functions such as track, identify, group, alias, trackForm, pageview, giveCookieConsent, and related functions. These suggest capabilities for collecting browsing, interaction, form, and potentially identity-related information.

The actual data collected—such as IP address, device details, browser information, pages viewed, cookies, identifiers, or form contents—is not specified.

2. User Rights

No rights are stated. The document does not explain whether users may:

  • Access or obtain a copy of their information
  • Correct or delete data
  • Object to processing
  • Restrict processing
  • Withdraw consent
  • Opt out of analytics or targeted tracking
  • Request data portability

It also provides no privacy contact, request procedure, retention period, or information about rights under laws such as the GDPR, UK GDPR, CCPA/CPRA, or other applicable regimes.

3. Third-Party Sharing

The code clearly causes information to be sent to third-party service providers, including:

  • Ahrefs
  • Snitcher/Radar
  • Potentially HubSpot or another form-processing provider, inferred from the form callback identifier

The document does not explain what information is shared, why it is shared, where providers are located, how long they retain data, or whether they may use it for their own purposes. Users should review the privacy policies of these providers separately.

4. AI/ML Training

There is no statement addressing whether user data is used to train artificial-intelligence or machine-learning models. This cannot be determined from the supplied material.

5. Key Obligations and Restrictions

No user obligations, prohibited conduct rules, account terms, intellectual-property provisions, or acceptable-use requirements are provided. The CSS only affects website presentation; it does not create meaningful user responsibilities.

6. Liability & Disputes

There are no provisions concerning:

  • Warranties or disclaimers
  • Limitation of liability
  • Indemnification
  • Governing law
  • Arbitration or court jurisdiction
  • Dispute procedures
  • Class actions
  • Service availability

The “404” message indicates that the requested page was unavailable, but it does not itself limit liability or create contractual terms.

7. Changes

No procedure is provided for changing a privacy policy or terms. The document does not say whether users receive notice through email, website updates, banners, or continued use.

Practical Risk Summary

The principal risk is lack of transparency. Tracking scripts are present, but the supplied document does not disclose the data practices needed for informed consent or legal compliance. Users should avoid submitting sensitive information until they can locate the site’s actual privacy policy and terms, confirm opt-out choices, and identify the organization responsible for processing the data.

Change history

2026-08-19 · Terms & Conditions

shrank 79.9% · Observed by clause.watch

Summary

The diff indicates that approximately 334 words were removed, but it does not identify which provisions were deleted. Without the original and revised language, it is not possible to determine the precise legal or commercial effect of the changes.

Potential Legal and Commercial Risks

The removal of contractual language may have eliminated or narrowed:

  • Customer protections, warranties, or service commitments.
  • Restrictions on the provider’s use or disclosure of customer data.
  • Confidentiality, security, or data-retention obligations.
  • Liability allocation, indemnities, or audit rights.
  • Termination rights or post-termination data-deletion requirements.
  • Compliance obligations relating to privacy, cybersecurity, or applicable law.
  • Definitions or exceptions that limit the scope of other provisions.

The risk depends heavily on whether the deleted wording was replaced elsewhere or merely removed. A deletion may be neutral if the same obligation appears in another section, but it may materially shift risk to the customer if protections were removed without replacement.

AI Training and Customer Data

The supplied diff does not include the deleted text, so it is impossible to determine whether the changes affect:

  • Whether customer data may be used to train, fine-tune, or improve AI models.
  • Whether prompts, inputs, outputs, or usage data may be retained for model development.
  • Whether data is used for generalized models or only customer-specific models.
  • Whether the customer must opt in or may opt out of AI training.
  • Whether de-identification, aggregation, or anonymization is required.
  • Whether human reviewers or third-party providers may access data for training.
  • Whether the provider must delete training data or models after termination.
  • Whether customer data may be used to create derived data, analytics, or model weights.

Recommended Review

Obtain the full before-and-after text, particularly provisions concerning:

1. Data ownership and license grants

2. Permitted uses of customer data

3. AI training or model improvement

4. Confidentiality and security

5. Retention and deletion

6. Third-party/subprocessor access

7. Liability and indemnification

Until the deleted language is reviewed, the principal concern is that customer protections—including restrictions on AI training—may have been removed or weakened.

2026-08-19 · Privacy Policy

shrank 79.9% · Observed by clause.watch

Summary of Important Changes

Overall Character of the Diff

This diff appears to involve website source code rather than contractual legal terms. It contains CSS, HTML/error-page text, analytics scripts, and tracking configuration. No provisions concerning customer rights, data ownership, confidentiality, privacy, or artificial-intelligence training are visible.

Notable Changes and Risks

1. Error-page and user-facing content

The diff introduces or exposes text such as:

  • “No feedback available”
  • “404”
  • “Oops... Even our best feedback couldn't find this page”
  • “Return to home”

Risk: If deployed incorrectly, this could replace normal page content or create broken/error pages. The wording is also informal and may be inappropriate for a customer-facing production environment.

2. Third-party analytics and tracking

The diff includes scripts for:

  • Ahrefs Analytics, using an externally hosted script and a data key.
  • Snitcher/Radar, using an external CDN and profile identifier.
  • A dataLayer event recording a HubSpot form submission.

Risks:

  • These services may collect visitor identifiers, IP addresses, device information, browsing activity, or form-interaction data.
  • The diff does not show user consent, opt-out functionality, a privacy notice, data-processing terms, retention limits, or restrictions on international transfers.
  • Loading external scripts creates security and supply-chain risks, particularly where scripts are dynamically fetched from third-party domains.
  • Form-submission tracking may involve personal data and should be reviewed for GDPR/UK GDPR, ePrivacy, CCPA/CPRA, and other applicable-law compliance.
3. Potential exposure of configuration identifiers

The code contains analytics keys and identifiers, including an Ahrefs data key and a Snitcher profile ID.

Risk: These may not be secret credentials, but publishing them can enable unauthorized attribution, misuse of tracking configurations, or unwanted association with the company’s analytics accounts. They should be classified and rotated if sensitive.

4. CSS and layout changes

The diff adds or restores extensive styling for:

  • Focus indicators and accessibility
  • Text truncation
  • Responsive visibility
  • Spacing and typography
  • Buttons, icons, and containers

Risk: These changes are primarily technical, but could affect accessibility, mobile rendering, content visibility, and the appearance of legally important notices or consent controls.

AI Model Training and Customer Data

No change relating to AI training is identifiable in this diff. It does not contain language authorizing, prohibiting, or limiting the use of customer data, prompts, submissions, feedback, or other content to train, fine-tune, evaluate, or improve AI models.

However, the analytics and form-tracking code may collect customer or visitor data. The underlying third-party terms and privacy documentation should be reviewed to determine whether those providers use collected data for model training or other secondary purposes.

Between 2023-12-01 and 2024-09-12 · Privacy Policy

shrank 31.1% · Reconstructed from Internet Archive captures

Summary

The diff states that approximately 334 words were removed, but it does not identify which provisions were deleted or provide the surrounding text.

Key Legal Implications
  • Changes cannot be reliably analyzed: Without the deleted language, it is impossible to determine whether the revisions affect liability, confidentiality, intellectual property, data protection, termination, warranties, or other legal rights.
  • Potential loss of customer protections: Deleted language could have limited the provider’s rights, imposed security obligations, restricted data use, or provided remedies to the customer.
  • Potential expansion of provider rights: If deleted language contained restrictions or consent requirements, its removal could broaden the provider’s discretion.
Customer Data and AI Training
  • The available diff contains no specific information about customer-data use or AI model training.
  • It is therefore not possible to determine whether the changes:
  • Permit or prohibit using customer data to train, fine-tune, or improve AI models;
  • Change whether customer data, prompts, outputs, or usage metadata may be used;
  • Remove consent, opt-out, anonymization, or aggregation requirements;
  • Change ownership or licensing rights in data or model outputs; or
  • Affect deletion, retention, security, or confidentiality obligations.
Recommended Review

To perform a meaningful legal analysis, provide either:

1. The actual deleted text; or

2. The complete before-and-after versions of the affected provision(s), preferably with deletions and additions visible.

Particular attention should be given to provisions mentioning customer data, content, prompts, inputs, outputs, service improvement, machine learning, artificial intelligence, model training, analytics, anonymization, aggregation, or de-identified data.

Between 2019-12-24 and 2020-09-24 · Privacy Policy

shrank 19.1% · Reconstructed from Internet Archive captures

The wording changed. No written summary was produced for this revision.

Between 2019-11-15 and 2020-08-11 · Terms & Conditions

shrank 2.9% · Reconstructed from Internet Archive captures

Executive Summary

The diff does not appear to contain contractual language. It primarily shows changes to website CSS, a 404/error-page message, and third-party analytics scripts. No provisions addressing customer data, artificial intelligence, machine learning, model training, data ownership, confidentiality, or privacy rights are visible.

Key Changes

1. Website styling and accessibility

The deleted material contains CSS comments and styles concerning:

  • Font rendering and browser compatibility
  • Keyboard focus indicators
  • Inherited colors and typography
  • Rich-text margins
  • Responsive layout and container alignment
  • Text truncation (“line clamp”)
  • Visibility on tablet and mobile devices
  • Icon sizing and hover effects

These changes appear operational or visual rather than contractual. They do not themselves alter customer rights or obligations.

2. Error-page and content changes

The diff includes an error-page message:

> “No feedback available… 404 … Even our best feedback couldn’t find this page. Return to home”

This could affect the user experience, but it does not create an apparent legal commitment or change data-use terms.

3. Third-party analytics and tracking

The replacement content adds or preserves scripts associated with:

  • Ahrefs Analytics, using an account/data key
  • Snitcher/Radar, using an API endpoint, CDN, namespace, and profile ID
  • A HubSpot form-submission event sent to window.dataLayer

These additions may result in collection or sharing of website-visitor information, such as page views, identifiers, referral information, form-submission events, or device/browser data. Depending on the surrounding privacy notice and user consent framework, this may create privacy and compliance considerations under laws such as the GDPR, UK GDPR, CCPA/CPRA, or similar regimes.

The scripts also introduce third-party dependencies and potential risks relating to:

  • Disclosure of visitor data to analytics providers
  • Cookies or similar tracking technologies
  • International data transfers
  • Vendor security and retention practices
  • Whether consent is obtained before tracking
  • Whether form-submission events reveal personal or sensitive information

AI Training and Model Use

No change concerning AI training is identifiable. The diff contains no language stating that customer data, prompts, inputs, outputs, feedback, account information, or usage data may be used to train, fine-tune, evaluate, or improve AI models.

It also contains no apparent opt-out, data-retention, ownership, confidentiality, or deletion terms relating to AI systems. Any AI-related provisions may exist elsewhere in the agreement or privacy documentation and should be reviewed separately.

Recommended Review

Confirm that the privacy notice and consent mechanism accurately disclose the newly added analytics tools, their purposes, data recipients, retention periods, and international transfers. Also verify that no separate contractual or online terms incorporate these scripts or analytics practices by reference.

Watch this company's contracts

We re-read these documents every six hours and email you when the wording changes.

Start monitoring free