← Back to blog

AI & Content · September 20, 2026 · 8 min read

Who Owns AI-Generated Content? The 5 Clauses to Read Before You Subscribe

Every AI writing tool promises you own the output - the five clauses that decide what that promise is actually worth sit elsewhere in the contract.

By FluxWriter Team

AI content ownership is settled by your vendor's terms of service long before copyright law gets a say, and the clause that decides it usually runs about four lines. Most subscribers skim past it, assume "you own your output" covers everything, and find the gaps at renewal or during a sale. This covers the five clauses that control your content, the wording worth questioning, and what to ask for instead.

Why "You Own Your Output" Says Less Than It Sounds

Nearly every AI writing tool prints some version of that line on its pricing page, and the sentence is doing only one job. It tells you who holds whatever rights the vendor has to give. It says nothing about whether those rights exist in the first place.

Those are separate questions. Registration guidance published by the United States Copyright Office in 2023 treats material produced by a machine without human authorship as ineligible, while the human-authored parts of the same work stay registrable. A vendor assigning you the output hands over whatever is actually there — for a paragraph generated and published untouched, that may be very little.

That sounds worse than it is. Registration matters when you want to sue somebody for copying your post. It has no bearing on whether you can publish the piece, rank it, or sell the site it sits on.

What actually bites is quieter. The ownership sentence says nothing about what the vendor keeps doing with the briefs you type into it. It is equally silent on who pays when an output echoes somebody else's work, and on what survives the day you cancel. Those four clauses vary far more between vendors than the ownership line does.

Clause 1: The Ownership Grant Itself

Read this one for two words: assign and conditioned. A clause that assigns ownership outright beats one granting you a licence to use the output, however broad and perpetual that licence sounds.

Then check what the grant depends on. Ownership conditioned on "an account in good standing" or "fees paid in full" means a billing dispute can, on paper, put 300 published posts back in play. You want the version that survives termination — conditional wording costs a vendor nothing to leave in.

Watch the carve-outs too. A vendor reasonably retains rights to its own templates, prompt libraries and interface copy, and that is its product rather than yours. The one to argue about reaches your finished article, such as a right to reuse published posts as marketing samples.

Read the paragraph, not the pricing page.

Take the vendors you are actually deciding between and read each contract the same way:

The middle column is where a cheap subscription gets expensive later, and the expense arrives as billed legal hours rather than a larger invoice — reckon on $250 to $600 an hour for somebody who reads content contracts for a living. One entry is never a dealbreaker. Four stacked tells you how that vendor behaves in a dispute.

Clause 2: What the Vendor Trains On

Your prompts are inputs, and in nearly every contract the inputs sit under a different paragraph than the outputs. Owning the article does not stop the brief behind it being retained and reused.

The wording to find is the purpose clause. "To provide and improve our services" is the standard phrasing, and improve is the word carrying the training permission. A narrower clause limits use to delivering the service you paid for.

The broad version usually sits on entry tiers in the $20 to $50 a month band. The opt-out and a stated retention limit appear nearer $60 to $150 per seat — check rather than assume, because plenty of vendors offer it on every tier and never advertise it.

The exposure here is rarely theft of your blog post. It is confidentiality. An open-ended training permission is the clause a client's procurement team finds, and that conversation goes badly even when nothing has gone wrong.

Ask for: an opt-out you can point to in writing rather than a toggle buried in settings, a retention period measured in days rather than "as long as necessary", and a data processing agreement if you sell into the EU or UK. A vendor that cannot produce those does not have them.

Clause 3: Indemnity and the Cap Underneath It

Several large AI vendors now offer intellectual property indemnity, and that is a real improvement on where the market sat in 2023. It is also narrower than the headline suggests.

The conditions cluster. Cover is usually written for unmodified output, so a heavy editing pass can put you outside it — the exact thing a good review process tells you to do. It tends to be a business-tier benefit, not something attached to the plan you are on. Then there is the cap.

Most vendors cap total liability at the fees you paid over the preceding 12 months. A few have deliberately removed that ceiling for copyright claims, and the difference is worth more than any other line on the page. Do the arithmetic once — at $50 a month the cap is $600, an hour or two of the advice you would need to use it.

Indemnity signals that the vendor takes the risk seriously. Treating it as insurance is a mistake.

The control that actually reduces your exposure costs nothing. Run every finished piece through a plagiarism check and a factual review before it publishes, and keep the dated draft showing the edit happened. Contractual cover is the last resort, not the plan.

Clause 4: What You Keep After You Cancel

Cancellation clauses are where the gap between "your content" and "your account" gets expensive. Posts already published to your own site stay live on infrastructure you control — but whether you still hold the rights to them is exactly what the cancellation clause decides. Everything still sitting inside the tool is a different matter.

Start with the export window, where 30 to 90 days after cancellation is the defensible range and some tools cut access at midnight on the renewal date. Then check what the export contains: drafts, briefs and your prompt library, or only the pieces you already pushed live. The second version is close to useless, because the briefs are the part you cannot cheaply recreate.

The word to search for is co-terminous. Any licence you hold ends when the contract does — defensible for software, indefensible for the 200 articles you paid to produce.

Fix: run a full export in month 1, not month 12. If it is painful while you are a happy paying customer, it will be impossible on the way out.

Clause 5: The Model Terms Sitting Underneath

Most AI writing tools are not model builders. They are interfaces sitting on top of two or three foundation models, and no vendor can grant you more than its own upstream agreement lets it grant.

That has a consequence you can check without a lawyer. A vendor unwilling to name the models it runs on cannot show you that its upstream contract permits commercial use at your volume, or that your data is excluded from training at that level. That is the asymmetry — a downstream opt-out is worth nothing if the model provider keeps the material anyway.

Model retirement is the other half. Foundation models get deprecated, notice periods vary widely between providers, and anything beyond a year of guaranteed availability is a planning assumption rather than a commitment. Avoid building a house voice only one model can reproduce.

A vendor that names its models and publishes a sub-processor list has done the work. A "proprietary engine" nobody will describe is also an answer.

FAQ

Can I copyright a blog post my AI tool wrote?

The human-authored portions, yes. Text generated with no meaningful human contribution sits outside registration under current United States guidance. Your structure, your edits, your examples and your own data all count as authorship, which is one more argument for a real review pass before anything publishes.

My client is paying for the content — who owns it?

Your client agreement decides what you have promised your client, but it cannot hand over more than your vendor's terms actually give you — so read both before you answer. The trap is granting a client full ownership of material you only hold a licence to. Confirm that your tool assigns rather than licenses before signing a work-for-hire clause you cannot actually honour.

What if the vendor changes its terms after I have published 300 posts?

Whether a change reaches you, and from when, depends on the contract itself — so treat this as a checklist, not a rule. Find the change-notice clause and how much notice it promises; the effective-date language; whether continued use is treated as acceptance; any survival clause; and whether the new terms say anything about output you produced before the change. If a change touches training permissions, the licence to your output or the indemnity, get qualified advice before renewing. Diary a terms review once a year either way.

The Practical Takeaway

Spend 20 minutes before the next renewal, not after it. Open the terms page, search for five words — assign, licence, training, indemnify and terminate — and read the paragraph around each. Write the answers into a note beside the monthly price, because a $29 tool with a co-terminous licence costs more than a $79 tool that assigns outright. None of this is legal advice, and a library of 200 articles is worth one billed hour of somebody qualified. Start with whichever tool holds most of what you have already published.

If you are producing content at volume and want the ownership question settled up front, tools like FluxWriter can help by publishing straight into a site you control rather than holding the library on their side — but reading the clauses, and deciding which risks you are willing to carry, is still your job.

← All posts