<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>AI Legal Index: Regulatory &amp; Compliance Counsel changes</title>
    <link>https://ailegalindex.com/categories/regulatory-and-compliance-counsel</link>
    <atom:link href="https://ailegalindex.com/feeds/regulatory-and-compliance-counsel.xml" rel="self" type="application/rss+xml" />
    <description>Material product changes at Regulatory &amp; Compliance Counsel vendors, tracked by AI Legal Index. Every entry is dated and cited to a public source.</description>
    <language>en-us</language>
    <copyright>Free to reuse with a visible link to ailegalindex.com. Terms: https://ailegalindex.com/use-this-data</copyright>
    <lastBuildDate>Sat, 26 Sep 2026 12:00:00 GMT</lastBuildDate>
    <ttl>720</ttl>
    <item>
      <title>Mitratech: Collaborati 5.6, the eBilling portal that feeds TeamConnect, adds a linked resubmission workflow for rejected invoices across manual…</title>
      <link>https://ailegalindex.com/changelog/mitratech</link>
      <guid isPermaLink="false">ailegalindex.com:change:6ab917f94f0d70b4bff6a102</guid>
      <pubDate>Sat, 26 Sep 2026 12:00:00 GMT</pubDate>
      <category>Product / capability</category>
      <category>Legal Ops &amp; Spend</category>
      <category>General Legal Assistants</category>
      <category>Regulatory &amp; Compliance Counsel</category>
      <description><![CDATA[<p>Collaborati 5.6, the eBilling portal that feeds TeamConnect, adds a linked resubmission workflow for rejected invoices across manual, LEDES and PDF submission paths, replacing the old unlinked Copy action with a Resubmit button. Resubmitted invoices now carry the Original Invoice primary key and the TeamConnect Invoice primary key automatically, and a flagged LEDES resubmission is blocked when the file's client does not match the client on the original rejected invoice.</p><p><strong>Why it matters:</strong> Legal ops and AP teams get a traceable chain from each rejected invoice to its corrected version across Collaborati and TeamConnect, which cuts manual relinking and duplicate invoice risk during bill review. The client match check stops a firm's resubmission from being attached to another client's rejected invoice.</p><p>Impact: Medium. Verification: Verified. Type: Product / capability.</p><p>Evidence: <a href="https://success.mitratech.com/Collaborati/collaborati_release_notes/Collaborati_Release_Notes/Collaborati_5.6_Release_Notes">Vendor documentation</a></p><p>Source: <a href="https://ailegalindex.com/changelog/mitratech">AI Legal Index change log</a>. Free to reuse with a link back. <a href="https://ailegalindex.com/use-this-data">Terms</a>.</p>]]></description>
    </item>
    <item>
      <title>Epiq acquired Canopy, maker of the patented Data Breach Response platform and the agentic Auto Review feature that automates first level…</title>
      <link>https://ailegalindex.com/changelog/canopy</link>
      <guid isPermaLink="false">ailegalindex.com:change:6ab917f94f0d70b4bff6a0fc</guid>
      <pubDate>Fri, 25 Sep 2026 12:00:00 GMT</pubDate>
      <category>Acquisition / corporate</category>
      <category>Regulatory &amp; Compliance Counsel</category>
      <category>Litigation &amp; eDiscovery</category>
      <description><![CDATA[<p>Epiq acquired Canopy, maker of the patented Data Breach Response platform and the agentic Auto Review feature that automates first level data mining review. Epiq states the Canopy platform will be integrated into its Epiq AI suite and made accessible through Epiq Service Cloud, with Canopy engineers joining to build Epiq AI for Cyber. Former Canopy COO Adi Elliott becomes Epiq VP, Product Management, Cyber.</p><p><strong>Why it matters:</strong> Breach counsel, review providers and insurers using Canopy now contract with Epiq, and access and roadmap move into Epiq AI and Epiq Service Cloud, so buyers should confirm standalone availability, data handling terms and regional AWS deployments under the new owner.</p><p>Impact: High. Verification: Verified. Type: Acquisition / corporate.</p><p>Evidence: <a href="https://www.epiqglobal.com/en-us/resource-center/news/epiq-acquires-canopy-to-unite-cyber-incident-response-technology-and-service-expertise">Vendor announcement</a></p><p>Source: <a href="https://ailegalindex.com/changelog/canopy">AI Legal Index change log</a>. Free to reuse with a link back. <a href="https://ailegalindex.com/use-this-data">Terms</a>.</p>]]></description>
    </item>
    <item>
      <title>Athennian's September 25, 2026 release lets admins restrict individual structure chart views to specific teams, adding a layer of access…</title>
      <link>https://ailegalindex.com/changelog/athennian</link>
      <guid isPermaLink="false">ailegalindex.com:change:6ab917f94f0d70b4bff6a0fb</guid>
      <pubDate>Fri, 25 Sep 2026 12:00:00 GMT</pubDate>
      <category>Product / capability</category>
      <category>Legal Ops &amp; Spend</category>
      <category>Regulatory &amp; Compliance Counsel</category>
      <description><![CDATA[<p>Athennian's September 25, 2026 release lets admins restrict individual structure chart views to specific teams, adding a layer of access control beyond entity level permissions. The control requires the Enterprise plan or the Enterprise Charts add on.</p><p><strong>Why it matters:</strong> Legal teams can limit who inside the organization sees a given ownership view without reworking entity level permissions. Because it is gated to Enterprise packaging, plan tier decides whether a buyer gets it.</p><p>Impact: Medium. Verification: Verified. Type: Product / capability.</p><p>Evidence: <a href="https://help.athennian.com/hc/en-us/articles/56316599726363-September-25-2026-What-s-New-in-Athennian">Vendor documentation</a></p><p>Source: <a href="https://ailegalindex.com/changelog/athennian">AI Legal Index change log</a>. Free to reuse with a link back. <a href="https://ailegalindex.com/use-this-data">Terms</a>.</p>]]></description>
    </item>
    <item>
      <title>Athennian's 25 Sept release lets organizations decide whether pending transactions count in ownership calculations and structure charts…</title>
      <link>https://ailegalindex.com/changelog/athennian</link>
      <guid isPermaLink="false">ailegalindex.com:change:6ab917f94f0d70b4bff6a0fa</guid>
      <pubDate>Fri, 25 Sep 2026 12:00:00 GMT</pubDate>
      <category>Product / capability</category>
      <category>Legal Ops &amp; Spend</category>
      <category>Regulatory &amp; Compliance Counsel</category>
      <description><![CDATA[<p>Athennian's 25 Sept release lets organizations decide whether pending transactions count in ownership calculations and structure charts, with ownership views now showing issued, pending, reserved and available amounts. The same release adds expiration dates on documents, with email or in app reminders a week before expiry, on the day, or both.</p><p><strong>Why it matters:</strong> Corporate secretarial teams get ownership figures that match how their organization treats pending deals, and can retire the spreadsheets they use to track expiring certificates and licenses.</p><p>Impact: Medium. Verification: Verified. Type: Product / capability.</p><p>Evidence: <a href="https://help.athennian.com/hc/en-us/articles/56316599726363-September-25-2026-What-s-New-in-Athennian">Vendor documentation</a></p><p>Source: <a href="https://ailegalindex.com/changelog/athennian">AI Legal Index change log</a>. Free to reuse with a link back. <a href="https://ailegalindex.com/use-this-data">Terms</a>.</p>]]></description>
    </item>
    <item>
      <title>TrustArc: The Mobile App Consent SDK now reads each region's consent model from the server and, in opt in regions, applies the configured default…</title>
      <link>https://ailegalindex.com/changelog/trustarc</link>
      <guid isPermaLink="false">ailegalindex.com:change:6ab917f94f0d70b4bff6a0f7</guid>
      <pubDate>Thu, 24 Sep 2026 12:00:00 GMT</pubDate>
      <category>Product / capability</category>
      <category>Regulatory &amp; Compliance Counsel</category>
      <category>Legal Research</category>
      <category>Legal Ops &amp; Spend</category>
      <description><![CDATA[<p>The Mobile App Consent SDK now reads each region's consent model from the server and, in opt in regions, applies the configured default category consent at app start without showing a banner, while regions with GDPR in scope, opt out regions and accounts with no default category are skipped. Three new iOS APIs (setAttOptOutLevel, setShowAttOptOutWindow, setAttOptOutLockCategories) control which categories are rejected and locked when a user declines Apple's App Tracking Transparency prompt, and a new getWebCookie() function returns consent cookie values on Android, iOS, Flutter and React Native.</p><p><strong>Why it matters:</strong> This changes what the SDK decides on a user's behalf without any user action, so legal teams should confirm their per region consent models and default categories match their own legal position before the new behavior takes effect in their apps.</p><p>Impact: Medium. Verification: Verified. Type: Product / capability.</p><p>Evidence: <a href="https://trustarchelp.zendesk.com/hc/en-us/articles/55547634596883-Privacy-Studio-Release-September-23-2026">Vendor documentation</a></p><p>Source: <a href="https://ailegalindex.com/changelog/trustarc">AI Legal Index change log</a>. Free to reuse with a link back. <a href="https://ailegalindex.com/use-this-data">Terms</a>.</p>]]></description>
    </item>
    <item>
      <title>TrustArc: Individual Rights Manager release 2026.09.2 adds Due Date Countdown Rules that start the data subject request deadline clock from either…</title>
      <link>https://ailegalindex.com/changelog/trustarc</link>
      <guid isPermaLink="false">ailegalindex.com:change:6ab917c2a328a2163b304e18</guid>
      <pubDate>Wed, 23 Sep 2026 12:00:00 GMT</pubDate>
      <category>Product / capability</category>
      <category>Regulatory &amp; Compliance Counsel</category>
      <category>Legal Research</category>
      <category>Legal Ops &amp; Spend</category>
      <description><![CDATA[<p>Individual Rights Manager release 2026.09.2 adds Due Date Countdown Rules that start the data subject request deadline clock from either the Request Received Date or the Request Verified Date, set per intake form, request type and brand, with the most specific rule applied and the global setting as fallback. The same release adds a Bulk Verify action that moves multiple Unverified requests to In Progress, excluding requests that require Evident or IDology identity checks.</p><p><strong>Why it matters:</strong> Privacy counsel handling access and deletion requests under different laws can encode each statute's deadline trigger in the system instead of tracking exceptions by hand, which lowers the risk of missed statutory response dates.</p><p>Impact: Medium. Verification: Verified. Type: Product / capability.</p><p>Evidence: <a href="https://trustarchelp.zendesk.com/hc/en-us/articles/55547634596883-Privacy-Studio-Release-September-23-2026">Vendor documentation</a></p><p>Source: <a href="https://ailegalindex.com/changelog/trustarc">AI Legal Index change log</a>. Free to reuse with a link back. <a href="https://ailegalindex.com/use-this-data">Terms</a>.</p>]]></description>
    </item>
    <item>
      <title>Relativity's developer changelog lists a new Review Center API that returns a review queue's current statistics, the same figures shown in…</title>
      <link>https://ailegalindex.com/changelog/relativity</link>
      <guid isPermaLink="false">ailegalindex.com:change:6ab917c2a328a2163b304e17</guid>
      <pubDate>Wed, 23 Sep 2026 12:00:00 GMT</pubDate>
      <category>Integration / interoperability</category>
      <category>Litigation &amp; eDiscovery</category>
      <category>General Legal Assistants</category>
      <category>Regulatory &amp; Compliance Counsel</category>
      <description><![CDATA[<p>Relativity's developer changelog lists a new Review Center API that returns a review queue's current statistics, the same figures shown in the Review Progress section of the Review Center dashboard. It is dated for both Relativity aiR and Relativity aiR Government.</p><p><strong>Why it matters:</strong> Firms and service providers tracking review against budget or deadline can pull live queue progress into their own reporting or matter systems instead of reading it off the dashboard.</p><p>Impact: Medium. Verification: Verified. Type: Integration / interoperability.</p><p>Evidence: <a href="https://help.relativity.com/RelativityOne/Content/What_s_New/Release_notes.htm">Vendor documentation</a></p><p>Source: <a href="https://ailegalindex.com/changelog/relativity">AI Legal Index change log</a>. Free to reuse with a link back. <a href="https://ailegalindex.com/use-this-data">Terms</a>.</p>]]></description>
    </item>
    <item>
      <title>Casepoint released its first two Casepoint IQ agents, the Relevance Determination Agent and the Issue Coding Agent, now live in its…</title>
      <link>https://ailegalindex.com/changelog/casepoint</link>
      <guid isPermaLink="false">ailegalindex.com:change:6ab917c2a328a2163b304e0c</guid>
      <pubDate>Wed, 23 Sep 2026 12:00:00 GMT</pubDate>
      <category>Product / capability</category>
      <category>Litigation &amp; eDiscovery</category>
      <category>Regulatory &amp; Compliance Counsel</category>
      <description><![CDATA[<p>Casepoint released its first two Casepoint IQ agents, the Relevance Determination Agent and the Issue Coding Agent, now live in its eDiscovery application for early access customers. The Relevance Determination Agent assigns each document a relevance or responsiveness likelihood score with its reasoning, and the Issue Coding Agent codes documents against matter defined issues with an optional post run QC that reports recall and precision per issue code. Both use a multimodel cross check and require users to validate performance on a sample set before the agent runs across the full document set.</p><p><strong>Why it matters:</strong> Review teams get AI first pass relevance and issue coding with a sample validation gate, per document rationale and an audit trail of every human and AI decision, which is what a defensibility challenge will ask for. The agents run inside the existing platform security boundary under current permissions, so adopting them does not add a new environment to vet.</p><p>Impact: High. Verification: Verified. Type: Product / capability.</p><p>Evidence: <a href="https://www.casepoint.com/press/casepoint-expands-casepoint-iq-with-purpose-built-ai-agents/">Vendor announcement</a></p><p>Source: <a href="https://ailegalindex.com/changelog/casepoint">AI Legal Index change log</a>. Free to reuse with a link back. <a href="https://ailegalindex.com/use-this-data">Terms</a>.</p>]]></description>
    </item>
    <item>
      <title>Reveal made a unified corporate eDiscovery suite available that combines Reveal Hold, Onna and Logikcull across legal hold, preservation…</title>
      <link>https://ailegalindex.com/changelog/reveal</link>
      <guid isPermaLink="false">ailegalindex.com:change:6ab9178d421c0bed64772f1b</guid>
      <pubDate>Tue, 22 Sep 2026 12:00:00 GMT</pubDate>
      <category>Pricing / packaging</category>
      <category>Litigation &amp; eDiscovery</category>
      <category>Regulatory &amp; Compliance Counsel</category>
      <description><![CDATA[<p>Reveal made a unified corporate eDiscovery suite available that combines Reveal Hold, Onna and Logikcull across legal hold, preservation, collection, early case assessment, review and production. Reveal says many Onna data sources now feed directly into Reveal Hold preservation and collection workflows, and Onna targeted collections move into Logikcull with context, metadata and file relationships intact. Preferred pricing applies to organizations that buy the suite through Dec. 31, 2026.</p><p><strong>Why it matters:</strong> In house legal teams can cover hold through production under one vendor relationship instead of stitching together point tools, with a year end deadline on the preferred price. The Reveal AI orchestration layer across the suite is only promised from 2027, so buyers should not count it as shipped.</p><p>Impact: Medium. Verification: Verified. Type: Pricing / packaging.</p><p>Evidence: <a href="https://www.revealdata.com/news/reveal-unifies-enterprise-ediscovery-from-legal-hold-through-production">Vendor announcement</a></p><p>Source: <a href="https://ailegalindex.com/changelog/reveal">AI Legal Index change log</a>. Free to reuse with a link back. <a href="https://ailegalindex.com/use-this-data">Terms</a>.</p>]]></description>
    </item>
    <item>
      <title>Reveal Hold Build 76908 lets legal teams collect Slack Enterprise Grid and Zoom Workplace content directly from Reveal Hold, with full…</title>
      <link>https://ailegalindex.com/changelog/reveal</link>
      <guid isPermaLink="false">ailegalindex.com:change:6ab9178d421c0bed64772f1a</guid>
      <pubDate>Tue, 22 Sep 2026 12:00:00 GMT</pubDate>
      <category>Integration / interoperability</category>
      <category>Litigation &amp; eDiscovery</category>
      <category>Regulatory &amp; Compliance Counsel</category>
      <description><![CDATA[<p>Reveal Hold Build 76908 lets legal teams collect Slack Enterprise Grid and Zoom Workplace content directly from Reveal Hold, with full collection available now and channel selection to follow in a later deployment. The build also adds user configurable legal hold and compliance dashboards (custodians in scope, acknowledgment progress, questionnaire status, new holds over time) and lets the Microsoft Purview integration wizard accept multiple domains.</p><p><strong>Why it matters:</strong> Preservation and collection of chat and meeting data can now run from the hold tool itself rather than through a separate collection step. Buyers should note the stated limits: no channel level selection yet, and Slack collections with a date range exclude data from the end date.</p><p>Impact: Medium. Verification: Verified. Type: Integration / interoperability.</p><p>Evidence: <a href="https://docs.revealdata.com/reveal-hold-new/docs/release-notes-build-76908">Vendor documentation</a></p><p>Source: <a href="https://ailegalindex.com/changelog/reveal">AI Legal Index change log</a>. Free to reuse with a link back. <a href="https://ailegalindex.com/use-this-data">Terms</a>.</p>]]></description>
    </item>
    <item>
      <title>Credo AI added the AIUC-1 AI agent standard to its AI Governance Platform, mapping AIUC-1 requirements to the specific agents they apply to.</title>
      <link>https://ailegalindex.com/changelog/credo-ai</link>
      <guid isPermaLink="false">ailegalindex.com:change:6ab9178d421c0bed64772f14</guid>
      <pubDate>Tue, 22 Sep 2026 12:00:00 GMT</pubDate>
      <category>Regulatory / guideline</category>
      <category>Regulatory &amp; Compliance Counsel</category>
      <description><![CDATA[<p>Credo AI added the AIUC-1 AI agent standard to its AI Governance Platform, mapping AIUC-1 requirements to the specific agents they apply to. Its GAIA assistant turns those requirements into owned controls, captures evidence as work happens and builds a reviewable history that can be reused for ISO/IEC 42001, the NIST AI RMF and the EU AI Act. Credo AI states it does not issue AIUC-1 certification; AIUC and accredited auditors such as Schellman do.</p><p><strong>Why it matters:</strong> Legal departments and firms vetting agentic tools get one place to track AIUC-1 requirements against the agents they buy and build (the post names Harvey as the first legal AI platform to certify), which replaces bespoke vendor questionnaires with a shared standard and current evidence.</p><p>Impact: Medium. Verification: Verified. Type: Regulatory / guideline.</p><p>Evidence: <a href="https://www.credo.ai/blog/credo-ai-brings-aiuc-1-the-worlds-first-ai-agent-standard-into-the-ai-governance-operating-layer">Vendor announcement</a></p><p>Source: <a href="https://ailegalindex.com/changelog/credo-ai">AI Legal Index change log</a>. Free to reuse with a link back. <a href="https://ailegalindex.com/use-this-data">Terms</a>.</p>]]></description>
    </item>
    <item>
      <title>Relyance AI's 21 Sept release tightened Strict InHost mode so sampled record values and error text stay out of scan results.</title>
      <link>https://ailegalindex.com/changelog/relyance-ai</link>
      <guid isPermaLink="false">ailegalindex.com:change:6ab9178d421c0bed64772f10</guid>
      <pubDate>Mon, 21 Sep 2026 12:00:00 GMT</pubDate>
      <category>Privilege / confidentiality</category>
      <category>Regulatory &amp; Compliance Counsel</category>
      <category>Legal Ops &amp; Spend</category>
      <description><![CDATA[<p>Relyance AI's 21 Sept release tightened Strict InHost mode so sampled record values and error text stay out of scan results. InHost runs the Relyance scanner in a cloud account the customer owns and copies only the results back to Relyance. The same release adds sanitized supporting context to data classification findings, which previously showed no context at all.</p><p><strong>Why it matters:</strong> Teams that keep scanning inside their own cloud can now be sure raw record values never leave it, even in error messages. Sanitized context also makes findings easier to check without exposing the data behind them.</p><p>Impact: Medium. Verification: Verified. Type: Privilege / confidentiality.</p><p>Evidence: <a href="https://docs.relyance.ai/release-notes/#rel-2026-09-21">Vendor documentation</a></p><p>Source: <a href="https://ailegalindex.com/changelog/relyance-ai">AI Legal Index change log</a>. Free to reuse with a link back. <a href="https://ailegalindex.com/use-this-data">Terms</a>.</p>]]></description>
    </item>
    <item>
      <title>Relativity removed the option to switch off GenAI mode when ingesting data into Data Breach Response, so every DBR ingestion now runs…</title>
      <link>https://ailegalindex.com/changelog/relativity</link>
      <guid isPermaLink="false">ailegalindex.com:change:6ab9178d421c0bed64772f0f</guid>
      <pubDate>Mon, 21 Sep 2026 12:00:00 GMT</pubDate>
      <category>Product / capability</category>
      <category>Litigation &amp; eDiscovery</category>
      <category>General Legal Assistants</category>
      <category>Regulatory &amp; Compliance Counsel</category>
      <description><![CDATA[<p>Relativity removed the option to switch off GenAI mode when ingesting data into Data Breach Response, so every DBR ingestion now runs through the generative AI workflow that identifies, extracts and links personal information to individuals. The release note lists support in the US, Canada, Brazil, Australia, United Arab Emirates, Asia, Europe Data Zone, United Kingdom, Switzerland and Africa regions, with the Relativity aiR Government date still TBA.</p><p><strong>Why it matters:</strong> Teams whose client, insurer or regulator terms bar generative AI on breach data can no longer run DBR in a non GenAI mode and must settle AI use terms before ingestion. Relativity's own DBR documentation says all outputs need human review because the model can omit or fabricate PI.</p><p>Impact: High. Verification: Verified. Type: Product / capability.</p><p>Evidence: <a href="https://help.relativity.com/RelativityOne/Content/What_s_New/Release_notes.htm">Vendor documentation</a></p><p>Source: <a href="https://ailegalindex.com/changelog/relativity">AI Legal Index change log</a>. Free to reuse with a link back. <a href="https://ailegalindex.com/use-this-data">Terms</a>.</p>]]></description>
    </item>
    <item>
      <title>Phaselaw: Full page redaction was reworked so users select one or more pages to redact in a single action, mirroring area redactions, instead of…</title>
      <link>https://ailegalindex.com/changelog/phaselaw</link>
      <guid isPermaLink="false">ailegalindex.com:change:6ab9178d421c0bed64772f0e</guid>
      <pubDate>Mon, 21 Sep 2026 12:00:00 GMT</pubDate>
      <category>Product / capability</category>
      <category>Regulatory &amp; Compliance Counsel</category>
      <category>Litigation &amp; eDiscovery</category>
      <description><![CDATA[<p>Full page redaction was reworked so users select one or more pages to redact in a single action, mirroring area redactions, instead of redacting only the visible page. A new toggle on finalized exports excludes fully redacted pages so blacked out pages no longer appear in the export bundle. Both changes apply only to full page redactions made from 21 September 2026 onward, because of a change in how those redactions are stored.</p><p><strong>Why it matters:</strong> Reviewers producing large disclosure sets no longer need to delete blank redacted pages after export or redact pages one click at a time, which cuts manual clean up of the final production. The export toggle has no effect on full page redactions created before the change.</p><p>Impact: Medium. Verification: Verified. Type: Product / capability.</p><p>Evidence: <a href="https://www.phase.law/changelog">Vendor documentation</a></p><p>Source: <a href="https://ailegalindex.com/changelog/phaselaw">AI Legal Index change log</a>. Free to reuse with a link back. <a href="https://ailegalindex.com/use-this-data">Terms</a>.</p>]]></description>
    </item>
    <item>
      <title>Phaselaw added a Case Activity page that logs significant events in a case: case creation, status and deadline changes, uploads, and…</title>
      <link>https://ailegalindex.com/changelog/phaselaw</link>
      <guid isPermaLink="false">ailegalindex.com:change:6ab9178d421c0bed64772f0d</guid>
      <pubDate>Mon, 21 Sep 2026 12:00:00 GMT</pubDate>
      <category>Product / capability</category>
      <category>Regulatory &amp; Compliance Counsel</category>
      <category>Litigation &amp; eDiscovery</category>
      <description><![CDATA[<p>Phaselaw added a Case Activity page that logs significant events in a case: case creation, status and deadline changes, uploads, and document status changes. It opens from a new icon beside the case title and is described as an audit log of who did what, and when. It only appears for cases created from 21 September 2026 onward, because it relies on newly stored case data.</p><p><strong>Why it matters:</strong> Teams answering DSARs or public records requests often have to show how a disclosure was handled, and a built in per case log reduces reliance on manual notes for that record. Cases created before the change do not get the log.</p><p>Impact: Medium. Verification: Verified. Type: Product / capability.</p><p>Evidence: <a href="https://www.phase.law/changelog">Vendor documentation</a></p><p>Source: <a href="https://ailegalindex.com/changelog/phaselaw">AI Legal Index change log</a>. Free to reuse with a link back. <a href="https://ailegalindex.com/use-this-data">Terms</a>.</p>]]></description>
    </item>
    <item>
      <title>DataGrail extended IP allowlisting beyond user sign in to API keys, Agents and external MCP clients such as Claude Desktop and Cursor…</title>
      <link>https://ailegalindex.com/changelog/datagrail</link>
      <guid isPermaLink="false">ailegalindex.com:change:6ab9178d421c0bed64772f0b</guid>
      <pubDate>Mon, 21 Sep 2026 12:00:00 GMT</pubDate>
      <category>Security / compliance</category>
      <category>Regulatory &amp; Compliance Counsel</category>
      <category>Legal Ops &amp; Spend</category>
      <description><![CDATA[<p>DataGrail extended IP allowlisting beyond user sign in to API keys, Agents and external MCP clients such as Claude Desktop and Cursor, with a separate set of approved IP ranges for each access path. Enforcement is continuous and every allowlist is off by default until an admin turns it on.</p><p><strong>Why it matters:</strong> Privacy and legal teams connecting AI agents and MCP clients to a system holding data subject request records can now restrict each path to known networks, which limits exposure from a leaked key or token.</p><p>Impact: Medium. Verification: Verified. Type: Security / compliance.</p><p>Evidence: <a href="https://docs.datagrail.io/changelog/2026-09/#week-of-september-21">Vendor documentation</a></p><p>Source: <a href="https://ailegalindex.com/changelog/datagrail">AI Legal Index change log</a>. Free to reuse with a link back. <a href="https://ailegalindex.com/use-this-data">Terms</a>.</p>]]></description>
    </item>
    <item>
      <title>BigID launched AgentIQ, an agentic automation layer that lets customers run data security, privacy and compliance work from a prompt…</title>
      <link>https://ailegalindex.com/changelog/bigid</link>
      <guid isPermaLink="false">ailegalindex.com:change:6ab9178d421c0bed64772f0a</guid>
      <pubDate>Mon, 21 Sep 2026 12:00:00 GMT</pubDate>
      <category>Product / capability</category>
      <category>Regulatory &amp; Compliance Counsel</category>
      <description><![CDATA[<p>BigID launched AgentIQ, an agentic automation layer that lets customers run data security, privacy and compliance work from a prompt inside BigID or from Claude, Copilot, GPT, Gemini and custom enterprise agents over BigID's secure MCP. Agents can report, investigate and act on findings, including revoking access, quarantining data, applying retention and fulfilling data subject requests, with four prebuilt agents at launch: Remediate Sensitive Data, AI Governance Enforcement, Access Exposure Analysis and Privacy Operations. Agents inherit the requesting user's permissions enforced at the API and MCP layer, every action is logged and attributable to a person, and revoke, quarantine and delete actions can be set to require human approval.</p><p><strong>Why it matters:</strong> Legal and privacy teams can now let agents take remediation and data subject request actions across 200+ connected systems autonomously, so deciding which workflows run without review becomes a governance setting they must own and audit. Permission inheritance at the API layer, not the prompt, limits what an attorney's Copilot or Claude session can reach or change through BigID.</p><p>Impact: High. Verification: Verified. Type: Product / capability.</p><p>Evidence: <a href="https://www.prnewswire.com/news-releases/bigid-launches-agentiq-the-agentic-automation-layer-for-data--ai-security-and-compliance-302884730.html">Vendor announcement</a></p><p>Source: <a href="https://ailegalindex.com/changelog/bigid">AI Legal Index change log</a>. Free to reuse with a link back. <a href="https://ailegalindex.com/use-this-data">Terms</a>.</p>]]></description>
    </item>
    <item>
      <title>Relativity aiR now connects to ChatGPT Enterprise through the Model Context Protocol.</title>
      <link>https://ailegalindex.com/changelog/relativity</link>
      <guid isPermaLink="false">ailegalindex.com:change:6aaea9fcafa54bf67064faa5</guid>
      <pubDate>Thu, 17 Sep 2026 12:00:00 GMT</pubDate>
      <category>Integration / interoperability</category>
      <category>Litigation &amp; eDiscovery</category>
      <category>General Legal Assistants</category>
      <category>Regulatory &amp; Compliance Counsel</category>
      <description><![CDATA[<p>Relativity aiR now connects to ChatGPT Enterprise through the Model Context Protocol. Administrators can use plain language in ChatGPT to create matters, align workspaces to the structure of their data and manage access and workflows in Relativity. The same kind of connection went live for Google's Gemini Enterprise for Legal on 25 August.</p><p><strong>Why it matters:</strong> This is administration, not review: the substantive analysis stays inside Relativity aiR. That is the right boundary for a platform holding privileged productions. Litigation support teams get a faster way to stand up matters without handing document content to a general assistant.</p><p>Impact: Medium. Verification: Verified. Type: Integration / interoperability.</p><p>Evidence: <a href="https://www.prnewswire.com/news-releases/relativity-air-now-integrates-with-openai-through-the-model-context-protocol-302882482.html">Vendor announcement</a></p><p>Source: <a href="https://ailegalindex.com/changelog/relativity">AI Legal Index change log</a>. Free to reuse with a link back. <a href="https://ailegalindex.com/use-this-data">Terms</a>.</p>]]></description>
    </item>
    <item>
      <title>CUBE's regulatory intelligence now powers a new Regulatory Horizon Scanning capability inside IBM watsonx.governance.</title>
      <link>https://ailegalindex.com/changelog/cube</link>
      <guid isPermaLink="false">ailegalindex.com:change:6aaea9fcafa54bf67064fab1</guid>
      <pubDate>Wed, 16 Sep 2026 12:00:00 GMT</pubDate>
      <category>Integration / interoperability</category>
      <category>Regulatory &amp; Compliance Counsel</category>
      <description><![CDATA[<p>CUBE's regulatory intelligence now powers a new Regulatory Horizon Scanning capability inside IBM watsonx.governance. It monitors AI related developments from regulators, legislators and standards bodies and surfaces them in the governance workflow, where teams can map a change to an AI use case and keep a record of how it was assessed.</p><p><strong>Why it matters:</strong> AI governance teams have been tracking EU AI Act and NIST changes by hand, next to their model inventory. This puts the regulatory feed beside the inventory, with a trail of each assessment. It lives in IBM's product, so it only helps buyers already running watsonx.governance.</p><p>Impact: Medium. Verification: Partially Verified. Type: Integration / interoperability.</p><p>Evidence: <a href="https://fintech.global/2026/09/16/cube-and-ibm-target-ai-regulatory-blind-spot/">Trade press</a></p><p>Source: <a href="https://ailegalindex.com/changelog/cube">AI Legal Index change log</a>. Free to reuse with a link back. <a href="https://ailegalindex.com/use-this-data">Terms</a>.</p>]]></description>
    </item>
    <item>
      <title>DataGrail added automatic high risk detection for data protection impact assessments, which fills Records of Processing Activities forms…</title>
      <link>https://ailegalindex.com/changelog/datagrail</link>
      <guid isPermaLink="false">ailegalindex.com:change:6a9c2c3cec4ad2f765994254</guid>
      <pubDate>Fri, 04 Sep 2026 12:00:00 GMT</pubDate>
      <category>Product / capability</category>
      <category>Regulatory &amp; Compliance Counsel</category>
      <category>Legal Ops &amp; Spend</category>
      <description><![CDATA[<p>DataGrail added automatic high risk detection for data protection impact assessments, which fills Records of Processing Activities forms by identifying AI use, biometric data and targeting of vulnerable individuals. The same release adds custom system naming in the Live Data Map, optional fields in the Privacy Requests API, and version 1.3.0 of the Request Manager Agent with JMESPath support.</p><p><strong>Why it matters:</strong> RoPA upkeep is the compliance task most teams are quietly behind on, because it is tedious rather than difficult. Automatic detection of the categories that trigger an assessment is worth more than the form filling, since missing a trigger is the failure that carries a penalty.</p><p>Impact: Medium. Verification: Verified. Type: Product / capability.</p><p>Evidence: <a href="https://docs.datagrail.io/changelog">Vendor documentation</a></p><p>Source: <a href="https://ailegalindex.com/changelog/datagrail">AI Legal Index change log</a>. Free to reuse with a link back. <a href="https://ailegalindex.com/use-this-data">Terms</a>.</p>]]></description>
    </item>
    <item>
      <title>CUBE added three agentic coworkers to RegPlatform: a Priorities Coworker that scores regulatory updates for relevance, an Analysis…</title>
      <link>https://ailegalindex.com/changelog/cube</link>
      <guid isPermaLink="false">ailegalindex.com:change:6a9c2c3cec4ad2f765994251</guid>
      <pubDate>Wed, 02 Sep 2026 12:00:00 GMT</pubDate>
      <category>Product / capability</category>
      <category>Regulatory &amp; Compliance Counsel</category>
      <description><![CDATA[<p>CUBE added three agentic coworkers to RegPlatform: a Priorities Coworker that scores regulatory updates for relevance, an Analysis Coworker that answers natural language questions against laws and rules, and an Enforcements Coworker that consolidates global enforcement actions. The agents run on Microsoft Azure and are listed on the Microsoft marketplace.</p><p><strong>Why it matters:</strong> The relevance scoring is the load bearing piece. Regulatory monitoring platforms have never struggled to find updates, they have struggled to tell a compliance team which of the several hundred this month actually apply to it. A live marketplace listing also means the deployment path is documented rather than negotiated.</p><p>Impact: High. Verification: Partially Verified. Type: Product / capability.</p><p>Evidence: <a href="https://fintech.global/2026/09/02/cube-turns-regulatory-overload-into-an-ai-advantage/">Trade press</a></p><p>Source: <a href="https://ailegalindex.com/changelog/cube">AI Legal Index change log</a>. Free to reuse with a link back. <a href="https://ailegalindex.com/use-this-data">Terms</a>.</p>]]></description>
    </item>
    <item>
      <title>RelativityOne now integrates with Microsoft Copilot over the Model Context Protocol.</title>
      <link>https://ailegalindex.com/changelog/relativity</link>
      <guid isPermaLink="false">ailegalindex.com:change:6a9c2c3cec4ad2f76599424c</guid>
      <pubDate>Mon, 31 Aug 2026 12:00:00 GMT</pubDate>
      <category>Integration / interoperability</category>
      <category>Litigation &amp; eDiscovery</category>
      <category>General Legal Assistants</category>
      <category>Regulatory &amp; Compliance Counsel</category>
      <description><![CDATA[<p>RelativityOne now integrates with Microsoft Copilot over the Model Context Protocol. Users can run administrative reporting against their RelativityOne environment using natural language prompts issued from Copilot.</p><p><strong>Why it matters:</strong> Administrative reporting moves into the Microsoft 365 surface legal teams already sit in, which removes a context switch for work that was never worth opening a second platform for. The value here depends on an existing Copilot deployment.</p><p>Impact: Medium. Verification: Verified. Type: Integration / interoperability.</p><p>Evidence: <a href="https://www.prnewswire.com/news-releases/relativity-brings-powerful-legal-data-intelligence-to-microsoft-copilot-expanding-ai-assistant-support-for-legal-teams-302864564.html">Vendor announcement</a></p><p>Source: <a href="https://ailegalindex.com/changelog/relativity">AI Legal Index change log</a>. Free to reuse with a link back. <a href="https://ailegalindex.com/use-this-data">Terms</a>.</p>]]></description>
    </item>
    <item>
      <title>RelativityOne can now collect Claude Enterprise data directly from the source using Anthropic's Compliance API.</title>
      <link>https://ailegalindex.com/changelog/relativity</link>
      <guid isPermaLink="false">ailegalindex.com:change:6a9c2c3cec4ad2f76599424b</guid>
      <pubDate>Thu, 27 Aug 2026 12:00:00 GMT</pubDate>
      <category>Integration / interoperability</category>
      <category>Litigation &amp; eDiscovery</category>
      <category>General Legal Assistants</category>
      <category>Regulatory &amp; Compliance Counsel</category>
      <description><![CDATA[<p>RelativityOne can now collect Claude Enterprise data directly from the source using Anthropic's Compliance API. The connector maps, preserves and processes conversation prompts, responses, chats and uploaded files into a reviewable form, including normalization into Relativity Short Message Format.</p><p><strong>Why it matters:</strong> Legal and compliance teams get a defensible collection path for conversational AI evidence, with context and metadata intact rather than reconstructed from exports. For any organization that has rolled out Claude Enterprise, this is the difference between an eDiscovery source that is reviewable and one that is not.</p><p>Impact: Medium. Verification: Verified. Type: Integration / interoperability.</p><p>Evidence: <a href="https://help.relativity.com/RelativityOne/Content/What_s_New/What_s_new_in_RelativityOne.htm">Vendor documentation</a></p><p>Source: <a href="https://ailegalindex.com/changelog/relativity">AI Legal Index change log</a>. Free to reuse with a link back. <a href="https://ailegalindex.com/use-this-data">Terms</a>.</p>]]></description>
    </item>
  </channel>
</rss>
