ClaimMaster vs PatentPal: how they compare in 2026
ClaimMaster and PatentPal both help patent drafters turn claims into application text. ClaimMaster is a Word add in that proofreads claims and specifications and adds optional AI drafting, while PatentPal generates a specification, figures and abstract from the claims. ClaimMaster leaves the customer in control of where client text goes. The software runs on the user's computer, sends text to a model only on command, and lets the customer choose OpenAI, Anthropic, its own Azure endpoint or a model running locally. It names those models, gives privilege waiver as its design reason, and publishes its prices, tiers and discounts. PatentPal states a short data position. Its terms say patent documents are processed in memory on AWS in the United States and shared with no other third party. Its site has no product page, and both of its legal documents date from 2022.
Which one fits
Choose ClaimMaster if
- You want to choose which model sees a client's application, or none at all. ClaimMaster sends text only on your command, directly from your computer to OpenAI, Anthropic, your own Azure OpenAI endpoint or a local model through Ollama, with no ClaimMaster servers in between.
- You want claims and specifications proofread inside Word. ClaimMaster's rule based checks review claims, specifications and Office Action responses, generate Office Action shells and USPTO forms, and download file wrappers and family data from the USPTO and EPO.
- You want a warranty and a trial before buying seats. ClaimMaster's license warrants the software conforms to its specifications, with repair or replacement during the subscription and a prorated refund if a defect cannot be fixed, and it offers a 30 day full trial with per user monthly or annual plans and volume discounts.
Choose PatentPal if
- You already have claims and want the specification written. PatentPal generates flowcharts and block diagrams, a detailed description of each figure, and the abstract and summary from your claims, with saved profiles that follow a drafter's or firm's preferred phrasing.
- You need unfiled inventions kept out of storage. PatentPal's terms state that patent documents are processed in memory and not otherwise stored, and that their contents and generated output go to no third party other than AWS for processing.
- You want the advice line in a dedicated clause. PatentPal's terms state that no attorney client relationship arises from using the service and that its output is not legal advice and not a substitute for a qualified attorney.
At a glance
All 15 axes, side by side
The same grid applied to every vendor in the index, graded from public sources. Hover a grade to see what the letter means on that axis.
AI Centrality
How much of the product is actually AI. Whether the machine learning is the mechanism the buyer is paying for or a feature layered onto conventional software, and whether the vendor is specific about which is which.
ClaimMaster's core is rule based. Proofreading of claims, specifications and office action responses, template drafting of sections and flowcharts, office action shells, USPTO forms and patent data downloads all run without a language model. The +Drafting and +Shells add ons bring the generative tools: drafting and rewriting text, figure descriptions, an LLM chat, office action analysis and, since version 2026.5, optional LLM proofreading with custom prompts.
PatentPal takes a set of claims and produces the specification language, the figures, the detailed description of each figure and the abstract, and there is nothing else in the offering: no repository, no search, no docketing, no matter management. The founder's own account on the About page describes the origin as writing the code for an initial summary generator and watching pages of writing appear at the push of a button. Without the model there is no product.
Citation Accuracy and Hallucination Disclosure
Whether the vendor publishes measured accuracy on citations and assertions, grounds output to primary sources, and says plainly what its system does when it does not know. Legal has a documented public record of fabricated citations reaching filed briefs, so an untested claim of accuracy is not evidence.
Drafting tools can run retrieval augmented generation over a local workspace of selected sections from earlier applications, retrieved by meaning, and users can supply example documents to reduce hallucinations. Users are told to review responses for factual correctness, especially at higher creativity settings. Output does not cite the passages it drew on, and no accuracy figure or test is published.
The terms state that the company makes no guarantees or warranties on the outcome of a patent application or on the quality of its output, including the generated language, and do not warrant that the service will be accurate, reliable or free of errors. There is no accuracy figure, test set or evaluation, no description of how generation is constrained, and hallucination is not addressed under any name. Nothing describes the relationship between the input claims and the generated specification, and generated support that does not match the claims creates written description problems. The navigation carries only About and an external Medium blog, so the site has no product or technology page.
Autonomy and Oversight Model
What the system decides on its own, what a lawyer must approve, and whether the vendor documents where the review point sits. A tool that drafts under review and a tool that files without one are different products and different risks.
Every LLM feature in ClaimMaster sends data only after the user presses a button, and the user controls exactly what is sent. Drafted text can be previewed and edited before insertion, and each prompt carries a creativity setting. LLM proofreading in version 2026.5 needs an explicit opt in at both the administrator and the user level, and all GPT features can be switched off for a whole firm on request. Nothing limits what the output may be used for or describes a review step before filing.
The published framing is generation in one click, with the founder describing pages of writing produced at the push of a button, and the value proposition is that the drafter does not do this work. The terms place the whole burden on the user in three ways: no attorney client relationship arises, output is not legal advice or a substitute for advice from a qualified attorney, and the service is used solely at the user's own risk. None of those describes a mechanism. Nothing published identifies a review point in the workflow, describes a confidence or uncertainty signal, states which parts of a draft a professional must check, or addresses what happens when generated support conflicts with the claims. The profile feature that tailors phrasing is a configuration control rather than a review surface.
Operational and Outcome Evidence
Named, dated evidence that the product works in production at real firms or legal departments. Case studies with figures and identified customers count. Unattributed testimonials and launch announcements do not.
Thousands of patent professionals use the product, ClaimMaster says, at some of the largest corporations and law firms as well as smaller firms and solo practices, and the site quotes satisfied users without names. It was built by a practicing patent attorney and a former USPTO examiner. No named firm, dated result or method is published.
The About page publishes investor and competition standing: a financing round led by Foothill Ventures, first place among 190 startups affiliated with Harvard at the Harvard China Forum, top five among 43 at the Harvard New Venture Competition, and first place among 15 startups at Plug and Play. Those concern the company rather than the product in practice. No customer is named, no logo strip appears, no testimonial is published, no case study exists and no figure for time or cost saved is attached to anyone. The privacy policy reserves the right to publicize that a user's company is a PatentPal customer, with an opt out on request, which implies customers without naming any.
Privilege and Confidentiality Posture
How client confidences are handled: attorney client privilege and work product treatment, segregation of one client matter from another, whether client data trains any model, and what the vendor commits to in writing rather than in marketing.
ClaimMaster warrants that the add in collects and transmits no user data, apart from patent number lookups, term definitions and LLM prompts sent at the user's request. It gives the risk of waiving attorney client privilege in cloud processing as the reason for running locally. LLM prompts go straight to the chosen provider with no intermediate server, ClaimMaster trains no models on customer data, and it has not opted in to OpenAI data sharing and says it never will. Each user's documents stay on that user's machine, private endpoints and local models are available, and all GPT features can be turned off for a firm. These commitments sit on the security and help pages, not in the license agreement.
An unfiled invention disclosed to a third party can destroy novelty, and the terms address storage and third parties. On storage, the privacy policy states that patent documents are processed in memory and not otherwise stored, and that neither the documents nor content generated from them is retained except as necessary to provide the service. On third parties, both documents state that the contents of patent documents and any generated output are shared with no third party other than for processing on Amazon Web Services, which answers what an underlying provider may see. Processing is stated to occur wholly in the United States over HTTPS. Nothing addresses training on customer content. Nothing addresses privilege or attorney work product, on a product handling unfiled applications. Segregation is covered only by a prohibition on sharing an account, with no role or permission model described.
UPL and Professional Responsibility Posture
Whether the vendor is clear that it supplies a tool rather than legal advice, who its audience is, and how it addresses unauthorized practice of law, competence and supervision duties, and jurisdiction limits. ABA Formal Opinion 512 is the reference point. Where the advice line is not the duty a product raises, the axis is read through the nearest professional duty it does raise: judicial conduct rules and the reviewing duty for products sold only to courts, and the duty to bill for time actually spent for products that draft time entries.
The license agreement makes the user solely responsible for content created with the software, which sells to patent attorneys, agents and paralegals. The help pages tell users to review LLM responses for factual correctness and to decide whether each provider's policies meet their obligations. Nothing states whether the product gives legal advice, and nothing addresses competence or supervision duties, USPTO guidance on AI use, or jurisdiction.
The terms give attorney client relationships and legal advice their own heading. They state that the services are not provided as part of an attorney client relationship, that using them does not create one, and that information received is not legal advice or a substitute for advice from a qualified attorney. The product generates text that goes into a filed instrument. Nothing describes what a professional must check before filing, and no rule of professional conduct or duty of candor to the patent office is named. No jurisdiction limit is stated, although the product generates specification language in the United States style. Nothing states who may use the service beyond a representation of authority to bind an entity.
AI Governance and Bias Disclosure
Published governance over model behavior: who owns it inside the vendor, what is tested before release, and what is disclosed about disparate output across matter types, parties, or populations.
No AI governance position is published. It uses base models from OpenAI, Azure OpenAI and Anthropic, or local models, without fine tuning them. Nothing describes how its prompts and AI features are tested before release, who answers for them, or how output quality varies across technologies.
PatentPal writes text into filed patent applications, and no responsible AI statement, governance framework, named owner accountable for model behavior, description of evaluation or testing before release, published result or bias statement is published. The navigation carries About and an external blog only, and the two legal documents, both dated 1 August 2022, make up the rest of the published site. Neither addresses how the model is developed, monitored or corrected.
AI Safety and Data Stewardship
Retention, deletion, access control, and what happens to prompts and documents after they are processed. Whether the vendor states its subprocessors and its incident practice, or leaves the buyer to assume.
The add in runs locally, keeps proofreading reports on the user's computer and collects no work product. Prompts go from the user's machine straight to the configured model over HTTPS, with no ClaimMaster server in between. ClaimMaster says data sent through the API is processed and not retained, while its summary of OpenAI's policy notes that provider's 30 day abuse monitoring retention. Files uploaded to a provider during a chat are deleted when the session ends and can be deleted earlier from the add in. Private Azure endpoints, a customer's own API keys and local models change who processes the data. No breach notification or incident practice is published.
Retention is addressed in specific technical terms: patent documents are processed in memory and not otherwise stored beyond what is needed to provide the service. Subprocessors are named by data type. Account and website information may be shared with Amazon Web Services, Google, LinkedIn and Stripe, the contents of patent documents go to no third party other than AWS, and payment data is handled by Stripe rather than stored. Access control is described only as HTTPS in transit, with no encryption at rest, no multi factor authentication, no role model and no logging stated. No incident or breach notification practice is published, and there is no security page on the site. Both documents carry an effective date of 1 August 2022, and the site footer still reads copyright 2022.
AI Liability and Recourse
What the vendor stands behind contractually when its output is wrong. Indemnities, caps, carve outs, insurance, and whether any of it is published or only reachable through a negotiated agreement.
Conformance to specifications at purchase and freedom from known malware are warranted in ClaimMaster's license agreement. Bugs are repaired, the software updated or replaced at no charge during the subscription, and a prorated refund applies when a defect cannot be fixed. Indirect and consequential damages are excluded, including any loss of confidentiality from sending data to a third party model service, and no aggregate cap is stated. The user is solely responsible for content created with the software and indemnifies ClaimMaster against misuse, and no vendor indemnity covers output.
The terms disclaim all warranties, state that no guarantee or warranty is given on the outcome of a patent application or on the quality of the generated language, and record that the service is used solely at the user's own risk. The limitation excludes not only indirect, incidental, special, consequential and exemplary damages but direct damages as well, without stating any cap, so there is no figure for the floor of a customer's recourse. No indemnity runs in either direction, and no insurance position is published. The allocation is short and published in full. The terms address the outcome of the patent application specifically, which is the loss a drafter fears.
Practice Systems Integration Depth
How deeply the product reaches into the systems legal work already lives in: document management such as iManage and NetDocuments, Word and Outlook, contract lifecycle management, matter management, e-billing, and court filing systems.
Microsoft Word, where drafting happens, is where ClaimMaster runs. Its help files document downloading bibliographic data, file wrappers, family trees and PDFs from the USPTO Open Data Portal, Patent Center and EPO, with background downloads for large patent and IDS lists. They also cover configuring OpenAI, Azure OpenAI, Anthropic and local LLM endpoints, and LLM summaries in the patent viewer. Bibliographic data for forms and shells can be imported from Private PAIR XML or from docketing tools as CSV, and no live connection to a docketing, document management or IP management system is described.
There is no integrations page, API reference or developer documentation, and the site consists of About, an external Medium blog, a login and two legal documents. No document management system, IP management system, docketing platform or patent office filing interface is named. Export to Word and to Visio or PowerPoint is described consistently in reviews by others but appears on none of the vendor's site pages, and it is export rather than integration. The product runs as a separate application at draft.patentpal.com, and nothing describes how drafts move between it and the systems a firm already runs.
Deployment Model and Data Residency
Where the software runs and where the data sits. Multi tenant cloud, single tenant, private deployment, on premises, and whether region of residence is a published option or an enterprise conversation.
Installation is per user, on each Windows computer, with documents processed locally, and installs on shared servers need separate licenses. LLM calls go from the user's machine to OpenAI, to Azure OpenAI or a customer's own Azure endpoint, to Anthropic, or to a model running locally through Ollama. OpenAI's servers are stated to be in the United States. Where the private OpenAI, Azure and Anthropic models that ClaimMaster configures for subscribers run is not stated.
All data processing is done in the United States, according to the terms, and both the terms and the privacy policy identify Amazon Web Services as the environment where patent documents are processed, with data sent over HTTPS. Nothing states whether the platform is single tenant or multi tenant, no dedicated or private option is offered, no AWS region is named, and nothing distinguishes where processing happens from where anything is stored, although processing in memory makes the storage question largely moot by design.
Security Certifications and Trust Center
Independent attestation a buyer can pull without a sales call: SOC 2, ISO 27001, penetration test summaries, a trust center with current reports and named scope rather than a badge image.
No SOC 2 report, ISO certification or audit is named for ClaimMaster. Its security page rests on local execution, and the API keys users store for private models are encrypted.
No independent security attestation is published, and no certification is claimed. No SOC 2, ISO or other framework is named, there is no auditor, no report at any access tier including on request, no mention of penetration testing, and no trust center or security page. The site navigation carries About and an external blog, and the footer carries the two legal documents and an email address. The only related material points at the host rather than the vendor. The terms direct users to Amazon's service terms, customer agreement and privacy notice and state that Amazon is similarly committed to data privacy, which describes AWS's posture and does not carry over to PatentPal.
Model Supply Chain Disclosure
Which models sit underneath, whose they are, where they run, and whether the vendor commits to telling customers when that changes. A legal buyer inherits every dependency it cannot see.
OpenAI's GPT models (GPT-5 among them), Azure OpenAI, Anthropic's Claude models and local models through Ollama all connect to ClaimMaster, which runs no proprietary models. It configures private, stateless OpenAI, Azure and Anthropic models for subscribers, and customers can bring their own keys or Azure endpoints. Calls go directly from the user's computer to the provider. Model support changes appear in release notes, such as the October 2026 updates for recent Anthropic, OpenAI and Ollama API changes, and no notice of changes is committed.
Both published documents state that the contents of patent documents and any generated output are shared with no third party other than for processing on Amazon Web Services. Read with the statement that processing happens in memory, that implies generation runs on models PatentPal controls within its own AWS environment. No model, version or family is named, no outside model or inference provider is identified, no AWS region or service is specified, and no commitment to notify customers if the model or its hosting changes is published. Naming the cloud says where the software runs, not whose model writes the specification. Both documents are dated 1 August 2022, before the current generation of language models.
Commercial Transparency
Whether a buyer can learn what this costs without entering a sales process: published rates, the unit being charged, what sits behind an enterprise tier, and what implementation adds.
ClaimMaster publishes per user prices for every tier, billed monthly or annually with 20 percent off annually. Lite costs $20 a month on annual billing ($24 monthly), or $30 with shells and forms; QA costs $30; Pro costs $35, $45 with shells, $65 with drafting and $75 with both ($90 monthly). Volume discounts are 5, 10 and 15 percent at 5, 16 and 41 seats, checkout is self service through SoftwareKey, and auto renewal can be cancelled at any time. Users download and activate the add in themselves after a 30 day trial of the full version, and firms deploying widely can get a custom installer and online training by arrangement.
No pricing information is published at any level, including the unit of charge. There is no pricing page: the navigation carries About and an external Medium blog, and the footer carries the terms, the privacy policy and an email address. Nothing states whether charging is per seat, per application, per generation or per subscription period, and no figure, band or range appears anywhere. The terms establish only the shape of the commercial relationship, not its cost. Payment is required before the services start, for example at the beginning of each subscription period, all payments are final and not refundable, and prices and payment terms may be updated at any time, with changes applying going forward. A trial and a price point appear in software directories and reviews written by others, not by the vendor.
Firm and Practice Coverage
Who the product is actually built for. AmLaw, midlaw, small firm and solo, in house departments, government and courts, and which practice areas are supported rather than merely claimed.
Patent attorneys, agents and paralegals at firms and companies of every size use ClaimMaster, and in house attorneys use it to check outside counsel's work. Drafting covers electrical, software, mechanical and biochemical technologies. Its shells and forms are built for USPTO practice, office action analysis now reads non United States and non patent citations, and EPO data can be downloaded. It runs in Word on Windows. Where the generative tools perform less well is not stated.
Nothing published describes who the product serves, what technology fields it handles, which jurisdictions its output is written for, or where it stops. The About page says the company builds software to generate language for patent applications automatically and describes the founder's background as a patent attorney, and the terms contemplate agreement by a law firm, company or other entity. There is no segment page, practice page, firm size, treatment of in house or government users, or statement of limits, and the site has no product page.
The 12 legal signals, side by side
Recorded rather than graded. These are the questions a practitioner has to answer before a tool touches a client matter, and the answers are taken from public material only.
Client Data in Training
Can material a lawyer puts into this product be used to train a model?
ClaimMaster never receives document content, since the add in runs locally, and its data policy page says it trains no models on customer data. It has not opted in to OpenAI data sharing, and it summarizes the OpenAI, Azure OpenAI and Anthropic API terms, which bar training on API data. The license agreement addresses only feedback submitted to ClaimMaster, not training. The drafting page's invitation to train models on a firm's own data refers to example documents passed into prompts.
Neither the terms nor the privacy policy mentions training or model improvement. They address storage and sharing tightly: patent documents are processed in memory and not otherwise stored except as necessary to provide the service, and their contents and any generated output are not shared with any third party other than for processing on Amazon Web Services. Those constrain what happens to a document without stating whether it contributes to model improvement, and a document processed in memory can still inform a model during that processing. The site has no security or product page.
Prompt and Output Retention
How long does the product keep what a lawyer typed, and can that be set to zero?
ClaimMaster keeps no prompts or outputs, because the add in runs on the user's computer. Prompts sent to OpenAI's API may be kept up to 30 days for abuse monitoring under OpenAI's policy, which ClaimMaster quotes, while its own summary says API data is not retained. Files uploaded during a chat are deleted when the session ends. A customer can route prompts to its own Azure endpoint or to a local model, keeping them off any provider.
The privacy policy states that patent documents are processed in memory and not otherwise stored. Neither the documents nor content generated from them is retained except as necessary to provide the software services, and the terms repeat the commitment. No period is stated because the position is that nothing is kept. The phrase except as necessary to provide the services is undefined, nothing states how long that need lasts for a draft in progress, no deletion route or confirmation is offered, and zero retention is not offered as a setting the customer can choose. Both documents carry an effective date of 1 August 2022.
Ethical Walls and Matter Segregation
Does retrieval respect the firm’s ethical walls, or can the model read across them?
Each ClaimMaster user works on a local computer with no shared matter store, so documents never pool between users. No permissions at matter level are described for document workspaces or prompt templates shared across a firm.
The only access provision is a prohibition in the acceptable uses section of the terms on sharing an account with any other person or entity, which allocates responsibility rather than describing separation. Nothing states whether the platform is single tenant or multi tenant, no role or permission model is described, no administrator function is mentioned, and nothing addresses how one drafter's work is kept from another's inside a firm account.
A patent firm routinely drafts for competing clients in the same technology field. Processing in memory reduces the exposure without answering the question.
Third Party Request and Subpoena Notice
If someone subpoenas the vendor for a firm’s data, does the firm hear about it first?
Under its license agreement, ClaimMaster may disclose information provided by or about the user, or about their use of the software, under lawful process or law enforcement requests. No commitment to notify the user is made. ClaimMaster holds no document content, which limits what it could disclose.
Legal obligations and enforcement of the terms of service are stated grounds on which PatentPal may share information it collects, with no notice commitment to the customer and no discretion over notice reserved. The privacy policy states separately that the contents of patent documents and any generated output are not stored or shared with any third party other than for processing on Amazon Web Services, and that sentence carries no carve out for legal process on its face.
So the clause on compelled disclosure plainly reaches account and website information, and its application to the patent documents themselves is left unresolved by the drafting. No transparency report is published.
Primary Law Corpus Provenance
Where does the law in this product come from, and does the vendor have the right to use it?
ClaimMaster's AI works on the user's own documents and workspaces of earlier applications, with no legal corpus behind its answers. Its downloading tools draw public USPTO and EPO patent data, separate from the generative tools.
The privacy policy states that PatentPal may collect publicly available patent data and other information from public sources, without naming any of it. No database, patent office feed, publisher or aggregator is identified, no jurisdictional coverage is described, no update schedule is given, and no licensing basis is stated. The product's main input is the user's own claims, from which the specification is generated.
Good Law Verification
Does the product tell you when the authority it just cited has been overruled?
Patent text is what the generative tools draft and analyze, with no legal authority cited. Office action analysis annotates prior art by column and line, and no check of whether cited law is still good is described.
The product does not retrieve or cite prior art, case law or patent status. It generates specification language, figures and an abstract from claims the drafter supplies, so nothing is checked for subsequent history.
Refusal and Uncertainty Behavior
What does the product do when the answer is not in the corpus?
Users preview drafted text before insertion and are told to check it for factual correctness. What the tools do when the source material cannot support a draft is not described, and no confidence signal is shown.
Nothing describes an abstention path, a state for declining to answer, a confidence or coverage signal against generated text, or any flag where a claim element lacks adequate support in the generated description. The published framing presents generation of a complete draft in one click, and the terms handle the risk by disclaimer, stating that no warranty is given that the service will be accurate, reliable or free of errors and that use is solely at the user's own risk. The site has no product page, and the company also runs a blog on Medium.
Fabricated Citation Record
Does a public court record exist addressing fabricated or hallucinated legal citations in output from this product?
The AI Hallucination Cases database, Damien Charlotin's record of court decisions on hallucinated AI content, has no entry for ClaimMaster. ClaimMaster drafts patent application text and office action responses for filing with the USPTO.
The AI Hallucination Cases database kept by Damien Charlotin holds no entry naming PatentPal or PatentPal Inc. The product generates specification prose from claims rather than citing authority.
Bar Guidance Alignment
Has the vendor engaged in public with the ethics opinions its buyers are bound by?
The risk of waiving privilege in cloud processing is discussed on the security page without citing any guidance. No ethics opinion, USPTO guidance on AI use, court order or bar guidance is referred to.
The terms carry a dedicated clause stating that no attorney client relationship arises from use of the service and that its output is not legal advice and is not a substitute for advice from a qualified attorney. No bar association, patent bar, regulator, rule of professional conduct or ethics opinion is named. Nothing addresses the duty of candor to the patent office or the drafter's own obligations when filing generated text over their signature.
Billing and Fee Posture
Does the vendor address what happens to the bill when the work takes an hour instead of six?
The drafting page tells patent professionals to beat their hours budget and reduce costs to clients. How work drafted with AI should be billed or disclosed to clients is not addressed.
The About page describes the aim as giving time back to the attorney so it can be directed toward maximizing client value, a purpose statement rather than a quantified saving, and no figure for time or cost saved appears anywhere. Nothing addresses what happens to a fixed drafting fee or a billed hour when specification writing is automated, and no record of AI assisted work for each matter is described. Patent drafting is often billed at a flat fee per application.
Outside Counsel Guideline Readiness
Can a firm get this vendor through a client’s AI clause without a bespoke negotiation?
Document text reaches only the model the customer selects, OpenAI, Azure OpenAI, Anthropic or a local model, directly from the user's computer. ClaimMaster's data policy page sets out each provider's data use and retention terms and links them. ClaimMaster itself processes no content, so it publishes no data processing agreement.
The privacy policy names the third parties that receive information, by data type. Account and website information may go to Amazon Web Services, Google, LinkedIn and Stripe, while the contents of patent documents and any generated output go to no third party other than AWS. Both documents are public. No model or model provider is identified, and there is no data processing agreement, no consent or notification pack, and no security documentation at any access tier. The cloud and the marketing vendors are named, and the model that sees the invention is not.
Court Disclosure Support
If a judge’s standing order requires an AI disclosure, can the product produce one?
Output goes into patent applications and office action responses filed with the USPTO. Nothing records which text a model produced, and disclosing AI use to the Office or a court is not addressed.
Nothing describes an export, log or audit trail recording which text was generated, which model produced it, what the drafter changed before filing, or when any of it happened. Processing happens in memory, so nothing is retained to export from. Generated specification text is filed over a practitioner's signature at a patent office, and a firm may need to account for how a description was prepared. No disclosure guidance or template is published.
The questions both sides leave open
Derived from the records above rather than written, so it cannot favor either vendor. Take these into both conversations and ask each side the same question.
- AI Governance and Bias Disclosure
- Security Certifications and Trust Center
- Ethical Walls and Matter Segregation
- Primary Law Corpus Provenance
- Good Law Verification
- Refusal and Uncertainty Behavior
- Court Disclosure Support
In summary
ClaimMaster
ClaimMaster, from ClaimMaster Software LLC of Maryland, is a Microsoft Word add in for patent attorneys, agents and paralegals. It proofreads claims, specifications and Office Action responses, automates drafting of sections, figures and flowcharts, and generates Office Action shells and USPTO forms. It also downloads USPTO and EPO data. Its optional drafting add ons connect to OpenAI, Anthropic, a private Azure OpenAI endpoint or a local model. ClaimMaster runs on the user's computer and sends text to a model only on command, with no ClaimMaster servers in between. According to the AI Legal Index, it sells per user tiers with volume discounts, from $20 a month on annual billing.
PatentPal
PatentPal, from PatentPal Inc., founded in Silicon Valley and led by former patent attorney Jack Xu, generates the supporting text of a patent application from the claims a drafter supplies. It produces flowcharts and block diagrams, a description of each figure, and the abstract and summary, with saved profiles for preferred phrasing. According to the AI Legal Index, PatentPal's terms state that patent documents are processed in memory on AWS in the United States and shared with no other third party, and that its output is not legal advice.
Questions buyers ask
ClaimMaster vs PatentPal: which is better for patent drafting?
ClaimMaster adds optional AI to a proofreading and drafting add in and publishes more on data handling, models and licensing. PatentPal is built entirely around generating a specification from claims and states a tight in memory processing position. Practitioners who want to pick their own model have more to read from ClaimMaster. From the AI Legal Index, based on each vendor's own published materials as of September 27, 2026. No vendor pays for placement.
Does ClaimMaster send patent text to the cloud?
Only when the user tells it to. ClaimMaster runs locally and does not transmit work product when proofreading. Its generative features send selected text directly from the user's computer to the chosen provider, OpenAI, Anthropic or the customer's own Azure OpenAI endpoint, or keep it on the machine with a local model. It says its OpenAI account is not opted in to data sharing. From the AI Legal Index, based on each vendor's own published materials as of September 27, 2026. No vendor pays for placement.
Does PatentPal store or train on patent documents?
PatentPal's terms and privacy policy state that patent documents are processed in memory and not otherwise stored, except as necessary to provide the service, and that their contents and generated output are shared with no third party other than AWS. Neither document addresses training either way. Both carry an effective date of 1 August 2022. From the AI Legal Index, based on each vendor's own published materials as of September 27, 2026. No vendor pays for placement.
How are ClaimMaster and PatentPal priced?
ClaimMaster prices per user per month, billed monthly or annually with 20 percent off annual billing. It sells Lite, QA and Pro tiers with drafting add ons, volume discounts of 5 to 15 percent and a 30 day free trial. On annual billing, seats run from $20 a month for Lite to $75 for Pro with drafting and shells. PatentPal's terms say payments are non refundable. From the AI Legal Index, based on each vendor's own published materials as of September 27, 2026. No vendor pays for placement.
Neither vendor paid for inclusion, placement or a grade, and neither reviewed this page before it published. Everything on it comes from public material on the dates shown. How the index grades.
Three points stand out. PatentPal's terms exclude direct as well as indirect damages without stating a cap, and warrant nothing about the quality of generated language. Those are published terms. Neither vendor names a security certification. ClaimMaster's data commitments sit on help and security pages rather than in its license. Neither vendor reviewed this page.