GC AI vs Wordsmith: how they compare in 2026

The models are the product. Chat, drafting, contract review, playbooks, the skill library, agents and the API are all generative capabilities, and the vendor describes its differentiator as a multi model retrieval approach calling several providers plus a 20,000 line system prompt. Remove the models and nothing remains.

The machine learning is the mechanism the buyer pays for, and there is no conventional platform underneath it. The product is a four-step flow of receive, route, resolve and record, and the two steps carrying the value are both model-driven: auto-triage that classifies an incoming request by priority, jurisdiction and commercial exposure and routes it to the right lawyer, and resolution that answers or drafts without one. The vendor draws the distinction itself, arguing that technology which only makes a lawyer faster leaves the operating model unchanged. Review, drafting, the assistant, agents, research and intake are each a model capability; repositories and reports are records of what those produced rather than standalone systems. Company incorporated October 2023 with no legacy platform to layer onto.

Grounding is real and documented, short of published measurement, which is the B band. Exact Quote produces character level verifiable citations with a picture in picture source view that slides the underlying document alongside the assertion, so a reader can check a quotation against its source without leaving the answer. The corpus behind research is identified: more than 13 million US court opinions from what the vendor describes as official, authoritative sources, plus real time web research. The retrieval approach is described as multi model, calling five different models. The vendor frames the feature explicitly around a lawyer's ethical obligation to check sources, which is the right framing for what grounding is for. What keeps this off an A is measurement, and specifically one claim: the comparison page asserts accuracy via proprietary methods and multi model retrieval with no figure attached, which is the unmeasured accuracy claim this axis exists to catch. Searched the site, the feature pages, the help documentation and the blog on 29 Aug 2026 and located no accuracy figure, no hallucination rate, no test set and no evaluation methodology. No abstention path is documented either.

Grounding is real and described in specifics, and no measured accuracy is published anywhere. On the evidence side: the research module states coverage of more than 130 jurisdictions across 60 countries drawn from curated government, regulatory and authoritative sources, with direct integrations to Companies House, EDGAR and Open Corporates for entity verification; the assistant returns a cited summary with links to the underlying legislation; the Word add-in returns answers described as cited and traceable; and Reports links every extracted value to an exact clause and page number with a click-through to verify. A reader can therefore open and check the source, which is the limb most of this market fails. What does not exist on any surface read on 31 Aug 2026 is a number: no accuracy figure, no hallucination rate, no benchmark, no described test set, no published evaluation of any kind. The vendor also lists smart web search as a source feeding legal answers without stating how a conflict between a curated source and a web result is resolved.

A real published commitment with a described control, short of the full structure. The vendor documents approve first controls on Agent Connectors: each user connects their own accounts, sensitive actions require approval before they run, an administrator enables the capability for the organisation, and API keys inherit the account's permissions so only playbooks and documents the legal team created are reachable. That is a named mechanism at the point where an agent acts on a business system, which is more than most of this market publishes. Not located as of 29 Aug 2026: what the system decides on its own inside a document review, the threshold at which it stops, and what happens after an output is wrong.

A real oversight posture with described review surfaces, short of the threshold that would make it a full control structure. The published model is that work reaches a lawyer only when it needs judgement, with routing to a named role shown as part of the flow. The review surfaces are concrete rather than asserted: in Reports a reviewer clicks a cell to verify it against the cited clause and page, then approves and locks the value or flags it for review; in the Word add-in every proposed redline can be accepted, rejected or improved individually. Against that, the company page describes chaining drafting into an end-to-end workflow that receives a request, drafts, routes for approval and sends with no manual step required, and nothing published states the threshold at which the system stops and escalates rather than resolving, or what happens after an output is found to be wrong. The proportion of requests resolved without a lawyer is presented as a headline statistic on the home page but the counter renders as zero, so the autonomy level is unquantified.

Real deployment evidence with substance, short of the full A bar. Ten named customer case studies are published with individually attributed quotes from named counsel at named companies including Columbia Sportswear, Arc'teryx, Snyk, Liquid Death, Eventbrite, Tipalti, Trust and Will, Viant and Jasper, and the vendor states more than 2,000 customer companies. Figures appear but attach to the aggregate rather than to a named deployment: a stated 30 percent reduction in outside counsel spend and one attributed quote reporting an hour of work reduced to ten minutes. Not located as of 29 Aug 2026: figures tied to a specific named customer with a method a reader can assess.

Named customers, named individuals and at least one figure, short of dates and method. Trustpilot appears with Anoop Joshi, Chief Trust Officer, alongside a stated 85 percent reduction in contract review time; the Financial Times with Dan Guildford, General Counsel; Belron with Janet McCarthy, General Counsel; and Multiverse with Tara Haig, General Counsel. A logo strip carries 25 named organisations including BT, Canva, Deliveroo, Nikon, Rakuten, Selfridges, Skyscanner and Starling, and dedicated customer story pages exist. Two things hold this at B beyond the missing dates and method. The home page outcome counters, covering share resolved without a lawyer, speed, outside counsel reduction and hours saved per lawyer, all render as zeroes rather than figures, so the platform's own headline results are not actually stated. And the same sentence about lawyers focusing on strategic work is attributed on that page to both Anoop Joshi and Janet McCarthy. Individual case study pages were not opened on 31 Aug 2026, so the date and method limbs are rebuttable.

The only A on this axis in the index so far, and it is earned on the one limb every other vendor misses. The vendor addresses privilege directly and specifically rather than implying it: a published FAQ states that information stays privileged through contractual and technical protections, and cites United States v. Heppner, where a federal judge ruled that material put into generalist tools without confidentiality terms may not be privileged, as the reason its own terms matter. Alongside that: no training on customer data by the vendor or its providers, zero data retention agreements with the named model providers, a segregated database instance per customer, AES-256 at rest and TLS in transit, customer deletion at any time, and a published data processing agreement. Segregation here is tenant level for an in house buyer with one client, which is the right shape for this segment rather than firm style matter walls.

Substantive commitments across most of this ground, with the training promise sitting in policy rather than in a located clause. Privilege is addressed directly rather than skirted: the security page states the product is designed to maintain attorney-client privilege and that its architecture aligns with ABA Formal Opinion 512. The no-training statement is unusually absolute and repeated, extending on a dedicated article to customer data never being used to train any underlying model or included in any pre-training corpus. The third-party model position is the strongest read in this pull: OpenAI, Anthropic and Google are each named with the specific contractual instrument under which zero data retention applies, and prompts and outputs are stated not to be stored, logged or used for training by any provider. Clause 11.2 of the terms binds each party to hold the other's Confidential Information and to use it only for implementing the contract. Two gaps hold it at B. No training prohibition was located in the retrievable portions of the customer agreement, so the commitment a buyer can point to is a policy statement rather than a term, and the data processing agreement that the terms incorporate by reference sits on a trust portal that refused automated access. Separation between customers is asserted as complete with no co-mingling, but no mechanism is documented.

A real position is published, and unusually it is engaged rather than disclaimed. The audience is stated precisely as in house counsel and legal teams, the vendor states plainly that specialised practices may be better served elsewhere and that it will recommend competitors, and it addresses a lawyer's own ethical obligation to check sources as the reason a verification feature exists. Jurisdiction is addressed in operational terms: the product works across jurisdictions worldwide and a user tells it which jurisdiction to apply for commercial contracts. Short of an A because competence and supervision duties are not addressed as such, and the jurisdiction answer describes a product setting rather than a stated limit on where the vendor's output can be relied on.

A published position that engages with named guidance rather than reciting a disclaimer, short of the competence and supervision limb. The security page names ABA Formal Opinion 512 twice, once in stating that the architecture aligns with it and once in a FAQ answering whether legal professionals must disclose AI use, which tells the reader that obligations vary by jurisdiction and bar association, that some recommend disclosure for substantive use while others do not require it for internal tools, and that teams should review Opinion 512 and applicable local bar guidance. The same page states that the product supports professional legal judgment rather than replacing it, and a published article engages with SRA and bar association duties to prevent unauthorised disclosure of client information. What is missing: nothing published addresses a lawyer's own competence and supervision duties in operating the tool, no jurisdiction limits are placed on the advice line despite research coverage spanning 130 jurisdictions, and no statement that Wordsmith is not a law firm was located on any surface read on 31 Aug 2026, which matters for a product whose stated purpose is resolving legal requests without a lawyer.

Checked the site, the security and privacy FAQ page, the trust center, the AI information page, the help documentation and the blog on 29 Aug 2026. No governance position for model behaviour was located: no named internal owner, no pre release testing regime, no published responsible AI framework, and nothing on uneven output across matter types, parties or populations. The vendor publishes substantial security and privacy governance, which is a different subject. This is the widest gap on an otherwise strong record and it is rebuttable with a single link.

No governance position for model behaviour was located. Searched the home page, the security page and its full FAQ, the downloads page, the company page, the research, assistant, reports and Word integration pages, and the published articles on data privacy and contract review, on 31 Aug 2026. Nothing names an individual or role accountable for model behaviour, describes what is tested before a release ships, sets out a responsible AI framework or principles, or discloses anything about uneven output across matter types, counterparties or populations. The security disclosure is substantial but it is information security, which is a different subject and does not carry on this axis, and the ISO 27001 certification described as in progress is likewise a security standard rather than an AI management one. One limitation worth stating: the Vanta trust portal linked from the footer refused automated access, and if it carries an AI governance policy this grade is rebuttable on that document alone.

Retention, deletion, access control, subprocessors and the model provider position are all published, current and specific enough to hold the vendor to. A named subprocessor list is published at a stable URL with no gate. Zero data retention agreements are stated with the model providers by name. Data sits in a segregated database instance, encrypted AES-256 at rest and TLS in transit, and the customer can delete it at any time. Enterprise plans carry SSO, MFA, directory sync, domain verification, authentication audit logs and log streams. A data processing agreement is published openly. The one element not located as of 29 Aug 2026 is a stated incident and breach notification practice on the public pages, which the published DPA may well cover.

Substantive published policy across most of the ground, short of an openly reachable subprocessor list. Published on the security page: AES-256 at rest and TLS 1.2 or higher in transit; access restricted on a least privilege basis; SSO through Okta, Azure Active Directory and Google Workspace over OIDC and SAML 2.0 with MFA and role-based access control; annual independent penetration testing; and a formal incident response plan with confirmed breaches notified to affected customers within 72 hours together with details and remediation steps. The privacy policy adds a commitment to notify the customer and any applicable regulator of a suspected breach where legally required, and states that access is limited to those with a genuine business need under a duty of confidentiality. Retention is customer-controlled: data can be permanently deleted at any time, all customer data is permanently deleted on termination, and custom retention policies can be configured. A published article is candid that a platform must retain some information to function, which is more useful than an unqualified zero-retention claim. The gap is that no subprocessor list is published on the open site and no default retention period is stated; both the list and the incident response plan sit on the trust portal.

Liability is addressed through published terms of service that a buyer can read before signing, which is more than most of this market, but what was located is the standard shape: the terms and the data processing agreement are public and cover the relationship. No indemnity running to the customer for third party claims arising from output, no warranty on output, no stated cap figure and no insurance position was located as of 29 Aug 2026 on the terms, the security FAQ or the trust center. Recorded at C rather than D because the governing documents are published rather than reachable only through a sales process.

Liability is addressed through a limitation clause that disclaims the exposure the product creates, with the indemnity running the other way. Clause 8 requires the customer to indemnify Wordsmith, its officers, directors, employees, agents and consultants against liabilities, costs, damages and losses arising from the customer's use of the product and from any breach of the terms, carved back only where the claim arises from Wordsmith's own failure to meet its obligations. Clause 9.1.1 then states that Wordsmith shall not in any circumstances have liability for losses or damages suffered by the customer, subject to exceptions at clauses 9.2 and 9.6. No indemnity running to the customer, no warranty on output and no insurance position was located. A retrieval limit to state plainly: the terms page returns no body text to automated fetching, so the agreement was read through the search index, and the text of clauses 9.2 and 9.6, which carry the exceptions and would ordinarily contain any cap, could not be retrieved on 31 Aug 2026. If either contains a vendor indemnity or an output warranty this grade moves.

Real integrations, documented, short of implementer level depth on each. Named and specific: a Microsoft Word add in with contract agents, playbooks and Easy Edit; a Slack connector included with the seat; Agent Connectors covering more than 20 business applications including Gmail, Outlook, Slack, Drive and HubSpot, each connected per user with per action approval; and a REST API with published documentation reaching tools including Ironclad, Jira and Zapier. The orientation is toward the business systems an in house team lives in rather than firm document management, which fits the segment. Not located as of 29 Aug 2026: integration with legal specific document management such as iManage or NetDocuments, and per connector documentation of what syncs in which direction.

Real integrations documented, with depth described in one place and asserted in the rest. The Word add-in is the strongest evidence: it is distributed through Microsoft AppSource under product identifier WA200008590, and its integration page describes what it actually does rather than that it exists, covering running a playbook against a contract in the sidebar, accepting, rejecting or improving each redline in place, querying the repository by at-mention to insert approved clause language, and running research with jurisdiction and language selection. A Slack app has its own install route, and dedicated pages exist for Microsoft 365 and MCP. Research integrates directly with Companies House, EDGAR and Open Corporates. The illustrated request flow shows context pulled from Salesforce, Slack and Ironclad. What is missing: no document management integration such as iManage or NetDocuments was located, the Salesforce and contract lifecycle connections appear in an illustrative workflow rather than in documentation stating what moves and in which direction, and no developer or API reference index was located on the open site on 31 Aug 2026.

Cloud delivery is implied and neither the tenancy model nor the region is stated. The vendor does publish that customer data sits in a segregated database instance, which speaks to isolation rather than to location, and states GDPR compliance and hundreds of global customers across Brazil, Israel, Japan, the United Kingdom and Australia. Searched the site, the security and privacy FAQ, the trust center and the published DPA references on 29 Aug 2026 and located no list of available regions, no residency option, and no statement of where processing happens as distinct from where data is stored.

Residency is stated clearly and as a customer choice, and the tenancy model is not stated at all. The security page publishes hosting on AWS with EU data residency by default and US available, and adds a commitment that data is not transferred outside the customer's chosen region without explicit consent, which is a stronger statement than most vendors make because it binds the vendor to the customer's selection rather than merely offering one. The underlying AWS certifications are named as ISO 27001, SOC 1, SOC 2, SOC 3 and PCI DSS Level 1. Three things hold this at B, all checked 31 Aug 2026. Nothing published states whether the platform is multi-tenant or single-tenant, and separation between customers is asserted without a tenancy model behind it. No private, single-tenant or on-premises option was located. And where processing happens as distinct from where data is stored is not addressed: three US-headquartered model providers process prompts, and the relationship between that processing and the customer's chosen region is not explained.

Certification is real and stated with an open access route, short of accessible evidence. SOC 2 Type II and SOC 3 are both stated as certified, GDPR compliance is claimed, badges link to a security and privacy FAQ page rather than sitting as decorative images, and a trust center is published at a stable URL. Under the three tier test this is materially better than absent. What holds it off an A is that the vendor states documentation is provided on request for procurement, and no coverage period, audit scope or named auditor was located as of 29 Aug 2026. Note the noun is used correctly for SOC 3, which is a public report by design, so publishing it openly would be a straightforward upgrade.

Certification is real and stated and a trust portal is openly linked, but no scope, date or auditor is available on any readable surface. The security page states SOC 2 Type II certification described as independent, GDPR compliance, annual independent penetration testing, and ISO 27001 in progress. A Vanta-hosted trust portal is linked from the site footer without a gate, and the vendor states that provider policies, the data processing agreement and the incident response plan sit there. That portal counts as a genuine access route and is credited here as reachable: it refused automated access through its robots file, which is a retrieval limit on the index's side and not a gap on the vendor's, so nothing is scored against Wordsmith for it. What could not be established from any surface read on 31 Aug 2026 is the substance an attestation is judged on: no auditor is named, no coverage period is given, no report scope is described, and no penetration test partner or summary appears. A badge stating SOC 2 Type II with no scope and no date is what the open site offers, and the portal is where the answer presumably sits.

The strongest supply chain disclosure in the index so far. The vendor answers the question directly in a published FAQ, names OpenAI and Anthropic as providers, points to a full subprocessor list published at a stable URL with no gate, states that no provider trains on customer data, and states that zero data retention agreements are in place with the named providers. The architecture is disclosed at a level most vendors do not attempt: a multi model retrieval approach calling five different models. What is not published is which model serves which task, where they run, and a commitment to notify customers before the list changes, but the subprocessor list is the mechanism by which such changes would surface.

The providers are named with unusual precision and the change commitment is absent. The security page identifies all three model providers, OpenAI, Anthropic and Google, states that each is used through a paid enterprise API, and names the specific contractual instrument under which zero data retention applies to each: OpenAI's API Data Usage Policy, Anthropic's Commercial Terms, and the paid API Gemini Terms. Naming the instrument rather than asserting a commitment in the abstract is more than almost any vendor does, and it lets a buyer check the upstream terms directly. Two gaps, checked 31 Aug 2026. No specific model or version is identified for any of the three, so a buyer knows whose models but not which, which matters for a product whose research module also feeds in live web results. And nothing published commits to notifying customers when the provider set or the models change, which for a multi-provider architecture is the disclosure a customer most needs.

Real pricing published for part of the range with team and enterprise tiers withheld, and the self serve path is genuinely complete rather than a gesture. The pricing page publishes $500 per user per month for the Individual plan with monthly and annual billing, itemises what the seat includes, and offers a buy now path that completes without a sales conversation, alongside a 14 day free trial. The vendor states in its own FAQ that individual pricing is standard and not negotiable. Team is On Request and Enterprise is custom. What holds this off an A: no figure for team or enterprise, US case law is an add on for individual seats with no price published, API usage is billed in credits with no rate published, and professional services for playbook buildouts and custom integrations are offered with no implementation cost stated.

No pricing information is published at any level, including the unit of charge. Searched on 31 Aug 2026: the main navigation, which carries no pricing entry; the footer Product section, which lists downloads, comparisons, ROI and security and no pricing; the home page, the security page, the downloads page and the company page. Every call to action across the property is to book a demo. Neither a figure, a tier structure, a per-seat or per-matter unit, nor a statement of what implementation adds was located. The agreement confirms that a priced self-service route exists, since the self sign-up terms authorise charging fees by credit card, debit card or automated clearing house on online purchase, but no number is published anywhere a prospective buyer can reach without entering the signup flow or a sales process. The ROI page in the footer was not opened, so this is rebuttable if it carries a rate rather than a calculator.

Who the product is for is documented precisely, and the limits are stated in the vendor's own words rather than inferred. Segment is in house legal teams at corporations, from solo and fractional general counsel through public companies, with named industries spanning retail, SaaS, technology, fintech, healthcare, restaurants, grocery, manufacturing and private equity, and named customers including Hitachi, Logitech, News Corp, Nextdoor, Skims, Zscaler, Vercel and TIME. Practice coverage is enumerated by work type: commercial contracts, MSAs, DPAs, NDAs, privacy, board minutes, policies, OEM and supply agreements. The boundary is published explicitly: the vendor states it is best for generalist in house lawyers and that if a practice is specialised, other platforms may be better and it will recommend them. Law firm practice is out of scope by design.

Segment coverage is described with real substance and the boundaries are left open. The property segments explicitly and in dedicated pages: by role for General Counsel and Legal Operations, by requesting team for procurement, sales, security and human resources, and by size across small business, mid-market and enterprise. Geographic and legal coverage is stated concretely as more than 130 jurisdictions across 60 countries, and the site publishes locale variants for eleven countries in five languages. What is absent is any statement of where the product stops. Law firm segments are not addressed, which is consistent with a product built for in-house teams, though external counsel appear only as recipients of shared reports and the position is never stated outright. Government and court use is not addressed. And practice coverage is expressed as the requesting business function rather than as areas of law, so a reader learns which internal team a request comes from but not which areas of law the product is competent in, on a platform whose research module claims 130 jurisdictions. Checked 31 Aug 2026.

A published FAQ answers the question directly and in the negative for both the vendor and its model providers, and states that zero data retention agreements are in place with the named providers OpenAI and Anthropic. A separate security panel states that customer data will not be used for commercial model training. The vendor publishes its terms of service and a data processing agreement openly, and states that confidentiality protections are contractual as well as technical. The commitment as recorded rests on the published FAQ and security pages, and the wording of the corresponding contract term was not read directly as of 29 Aug 2026.

The security page states that customer data is not used to train Wordsmith's own models or to improve the platform for other customers, and a published article extends that to customer data never being used to train any underlying model or included in any pre-training corpus. Separately, zero data retention is stated to be contractual with the three model providers, each named with its instrument. That contract is with OpenAI, Anthropic and Google rather than with the customer. No training prohibition was located in the retrievable portions of the customer agreement on 31 Aug 2026; the terms page returns no body text to automated fetching and was read through the search index, and the data processing agreement the terms incorporate by reference sits on a trust portal that refused automated access. The value is bounded by that and is rebuttable on the DPA.

REGRADED 29 Aug 2026 after the value set was amended; previously recorded at disclosed without a period, which understated real customer control. The vendor states that customer data sits in a segregated database instance and that the customer can delete it at any time, and separately that zero data retention agreements are in place with the model providers so prompts are not retained at the provider layer. Deletion on demand is control over how long data persists, exercised by the customer rather than negotiated, and it is recorded as such. Recorded at customer controlled rather than the top value because deletion at will is not the same as setting a window in advance: nothing runs automatically, so the data persists until someone acts. No stated retention period for the vendor's own storage was located and no zero retention setting for the product itself was located as of 29 Aug 2026.

The security page states that customers retain full control of their data, that it can be permanently deleted at any time, that all customer data is permanently deleted from Wordsmith's systems on termination, and that custom retention policies can be configured to match internal data governance requirements. No default retention window is published for prompts or outputs. A published article distinguishes zero training from zero retention and states plainly that a platform must retain some information in order to function, so no-retention is not offered as a setting at the Wordsmith layer; the zero retention that is stated applies to the model providers, where inputs and outputs are said not to be retained after processing.

Searched the site, the security and privacy FAQ, the trust center and the help documentation on 29 Aug 2026. The vendor documents tenant level isolation through a segregated database instance per customer, and permission inheritance for API keys, but no material addresses segregation between users or matters inside a customer, and the product does not integrate with legal document management systems whose permissions it could inherit. Recorded as not addressed rather than at a positive value because tenant isolation answers a different question. Worth noting for a future reader that this signal was written for law firm ethical walls, and an in house buyer with a single client faces a materially different version of the question.

Separation is asserted at customer level on the security page, which states that data is kept completely separate from other customers with no co-mingling and no cross-contamination, supported by SSO through Okta, Azure Active Directory and Google Workspace and role-based access control. Within a customer, a published article states that playbooks and templates are shared across the organisation only where the user chooses to share them. How either boundary is enforced is not published: searched the home page, the security page, the company page and the product and integration pages on 31 Aug 2026 and located no tenancy model, no description of how retrieval applies access controls at query time, and no statement of whether the repository can be read across internal teams. The buyer here is an in-house department, so the relevant test is tenant-level separation rather than matter-level walls.

Searched the published terms of service, the privacy policy, the data processing agreement, the security and privacy FAQ and the trust center on 29 Aug 2026. No clause addressing government or law enforcement requests for customer data was located, and no transparency report was located. This records a search across the published documents that did not surface the clause rather than a reading of every document end to end.

Row completed 2 September 2026 under R26. Clause 11.4 of the Wordsmith terms of service permits a party to disclose Confidential Information to the extent required by law, by a governmental or regulatory authority, or by a court of competent jurisdiction, and then commits, to the extent legally permitted, to give the other party as much notice of the disclosure as possible. It adds a further limb that where notice is not prohibited and is given, the disclosing party takes into account the other party's reasonable requests about the content of the disclosure, which is consultation on scope rather than bare notification. The obligation is reciprocal. Clause 11.5 makes the confidentiality article survive termination. It is not the top value because no transparency report was located. A provenance limit is recorded rather than hidden: the terms page is JavaScript-rendered and its body did not extract on either this reader's tooling or the operator's, so the clause text was recovered from the search index of that same first-party URL rather than from a direct render. No evidenceQuote is recorded for that reason, since a quotation should rest on text read at source. The substance is not in doubt, but the retrieval route is weaker than a direct fetch and a later grader should know that.

The research corpus is identified by volume and character: more than 13 million US court opinions drawn from what the vendor describes as official, authoritative sources, plus real time web research. Coverage is sold as a discrete US Case Law component, included in team and enterprise plans and available as an add on for individual seats, which tells a buyer where it stops. Not located as of 29 Aug 2026: the named source or publisher of the opinion corpus, the licence or public domain basis for it, and any update cadence or lag.

Coverage is described by jurisdiction without identifying the underlying legal corpus. The research module states more than 130 jurisdictions across 60 countries with access to primary legislation, databases and guidance from hundreds of trusted legal sources, described as curated government, regulatory and authoritative sources that are continuously updated, supplemented by smart web search. No individual legislation or case law source is named and no licence or public domain basis is stated for any of it. Three sources are named, but they are corporate registries used for entity verification rather than legal authority: Companies House, EDGAR and Open Corporates. No update cadence or lag is published beyond the word continuously.

Searched the site, the research and Exact Quote feature pages, the help documentation and the blog on 29 Aug 2026. The product verifies that a quotation matches its source at character level, which is citation accuracy rather than treatment. No material was located addressing whether authority returned carries a treatment signal, whether subsequent history is checked, or whether any commercial citator is licensed. The distinction matters here: a citation can be quoted exactly and still be dead law.

Searched the home page, the security page, the company page, and the research, assistant, reports and Word integration pages on 31 Aug 2026. Nothing addresses whether authority returned to the user is checked for subsequent history, and no citator, treatment signal or good law indicator was located. This signal applies squarely to this product rather than being out of scope, because the research module retrieves primary legislation and returns cited answers linked to it. The nearest published material concerns currency of sources rather than status of authority: sources are described as continuously updated and smart web search is said to ensure answers reflect the most recent developments, neither of which tells a reader whether a cited provision or decision still stands.

Searched the site, the feature pages, the help documentation and the blog on 29 Aug 2026. No published material was located describing what the product does when it cannot ground an answer, whether an explicit no answer path exists, or whether any confidence or grounding signal is exposed to the user. Exact Quote verifies a quotation against its source, which addresses whether a citation is real rather than what happens when nothing supports the answer.

Searched the home page, the security page, the company page and the product pages for research, assistant, agents, reports and the Word add-in on 31 Aug 2026. No explicit no-answer or abstention path is documented and no confidence or grounding score was located. Two features come closest and neither is the same thing: the triage flow is described as surfacing work to a lawyer only when it needs their judgement, which is routing rather than abstention, and Reports allows a reviewer to flag a value that needs review, which is a human action on an answer already given rather than the system declining to give one.

No court order, opinion or disciplinary record naming this product has been located as of 29 Aug 2026. Instrument searched: the AI Hallucination Cases database maintained by Damien Charlotin, which tracks court decisions worldwide involving AI generated hallucinated content and records the AI tool implicated where it is known. Also checked published 2026 sanctions summaries and secondary sanctions trackers. The entries located name filers, and in some rows other products, rather than this one. This is a statement about the public record on the date shown and not a clearance, and it is bounded by what that database covers. Note that this vendor itself publishes a tracker of such cases, which surfaces in searches for its name and is not a record about the product.

No court order, opinion or disciplinary record naming this product has been located as of 31 Aug 2026. Instrument searched: the AI Hallucination Cases database maintained by Damien Charlotin, which tracks decisions worldwide where a court addressed hallucinated AI content and records the tool implicated where known, searched on both the product name and the company name Wordsmith AI Ltd, alongside 2026 sanctions summaries in the trade press. This is a statement about the public record on the date shown rather than a clearance, and it is bounded by what that database covers. The product is sold to in-house departments rather than to litigators, so its output does not commonly reach a filed brief.

Public material engages with named guidance rather than referring to ethics in general terms. The vendor publishes a running tracker of AI hallucination sanctions decisions that states ABA Formal Opinion 512, issued July 2024, is explicit that lawyers using generative AI keep their duties of competence, candor and confidentiality and that the obligation to verify stays with the lawyer. Separate published material cites United States v. Heppner on privilege in generalist tools. Short of the mapped by jurisdiction value because no mapping of the product to named opinions across more than one jurisdiction was located, and the engagement sits in editorial content rather than in a compliance document a risk committee could be handed.

Public materials engage with a named ethics opinion. The security page cites ABA Formal Opinion 512 twice: once in stating that the product's architecture aligns with it, and once in a FAQ answering whether legal professionals must disclose AI use to clients, which tells the reader that obligations vary by jurisdiction and bar association, that some recommend disclosure for substantive AI use while others do not require it for internal tools, and that teams should review Opinion 512 together with applicable local bar guidance. A published article separately engages with SRA and bar association duties to take reasonable steps against unauthorised disclosure of client information. No mapping of the product to named opinions across more than one jurisdiction was located, so local guidance is referred to generically rather than identified.

Vendor material is framed around cost and time savings and quantifies them: a stated 30 percent reduction in outside counsel spend, an attributed quote reporting an hour of work reduced to ten minutes, a published return on investment calculator, and per seat analytics on usage and time saved. Searched the site, the pricing page, the help documentation and the blog on 29 Aug 2026 and located no published guidance on billing, fee or client disclosure treatment. Noted for context: the buyer here is an in house team that does not bill a client by the hour, so this signal reads differently for this segment than it does for a law firm product.

Public materials are built around time and cost saved. A customer story states an 85 percent reduction in contract review time, a published article claims contract processing times reduced by 50 to 60 percent, Reports is described as auditing more than 2,800 agreements in days rather than weeks, and the home page presents hours saved per lawyer each week and reduced outside counsel spend as headline outcomes, though those counters render as zeroes. Searched the home page, security page, company page, product pages and articles on 31 Aug 2026 and located no per matter record of AI-assisted work intended for fee or disclosure purposes and no published guidance on billing treatment. The buyer is an in-house department rather than a firm billing a client, so the question lands on outside counsel spend rather than on the hourly bill, but nothing addresses either.

The material a buyer would need is published without an agreement in place: a subprocessor list at a stable URL, named model providers with stated zero data retention agreements, a data processing agreement, terms of service, a privacy policy, a security and privacy FAQ and a trust center. That is more than the subprocessor list this value describes and short of the full disclosure pack, because the vendor states that procurement documentation is provided on request and no client facing consent or notification material was located as of 29 Aug 2026. Recorded at the subprocessor level as the closest published value.

A model provider list is published without a gate. The security page names all three providers that see customer content, OpenAI, Anthropic and Google, states that each is accessed through a paid enterprise API, and identifies the specific contractual instrument under which zero data retention applies to each. That is the disclosure most useful to a legal team answering a client AI clause, and it is readable before any agreement is in place. What could not be confirmed on 31 Aug 2026 is anything beyond it: no full subprocessor list appears on the open site, and the data processing agreement, the provider policies and the incident response plan are all stated to sit on the Vanta trust portal, which is linked openly from the footer but refused automated access, so its contents were not verified and no client-facing consent or notification pack could be confirmed to exist.

Some elements of a disclosure record are available. Exact Quote produces character level verifiable citations with a picture in picture source view, so what was retrieved and whether it says what the output claims can be shown per assertion. Enterprise plans carry authentication audit logs and log streams, and per seat analytics record usage. Two elements are missing: the model used is not identified per output, since the vendor runs a multi model approach across several providers, and no per document export covering model, sources and human verification together was located as of 29 Aug 2026.

Some elements of a record exist, short of a document-level export. Reports links every extracted value to its source with an exact clause and page number, and a reviewer clicks through to verify it and then approves and locks the value or flags it for review, which produces a per-value record of both the source relied on and the human check. The Word add-in similarly records each proposed redline as accepted, rejected or improved. The missing element is the model: which of the three providers produced a given passage is not disclosed anywhere on the property, and no export designed to cover model used, sources retrieved and human verification together was located on 31 Aug 2026. The product serves in-house departments rather than producing court filings, so a judicial standing order is not its usual context.