Who owns what you wrote

Two separate questions get collapsed into one here. Who owns the messages you typed, and who owns the replies you received. The first has a standard answer that sounds reassuring and matters less than it appears. The second has no settled answer at all, which is why the terms will simply tell you what the operator intends.

Ownership and licence are not the same question

Consumer terms nearly always say you retain ownership of the content you submit. That sentence is true and it is not where the rights are.

Immediately after it comes a licence grant: permission for the operator to host, store, copy, transmit, adapt, modify and create derivative works from your content, for the purposes of operating and improving the service. Some grants add sublicensing to affiliates and service providers. Some are described as worldwide, royalty-free and perpetual.

Ownership without control is the normal shape of this, and the licence is the control. The operator does not need to own your messages to do anything it wants to do with them operationally; it needs permission, and the grant is that permission. So the question worth asking is never “do I own this”. It is what the licence covers, who it extends to, and how long it lasts.

The three specifics worth reading

Purposes. A licence limited to providing the service is narrow: hosting, transmitting, displaying back to you. A licence extending to improving our services, developing new features, or research and development is considerably wider, and that phrasing is also where training use often lives. It is worth reading alongside the privacy policy’s training language, because the two documents answer adjacent questions and only one of them is usually searched.

Who else it reaches. Sublicensable, or extended to affiliates, subsidiaries, successors and service providers, means the permission travels with the business. Most apps do not run their own model, so at minimum your text passes to whoever supplies it — a longer chain of custody than the interface suggests.

Survival. Search near the termination clause for wording about which provisions survive. Licences commonly do. A grant that survives account deletion means the copies already made under it are not retracted by your leaving, which is a plainer way of saying what most deletion sections say at greater length.

The replies are a different problem

Who owns the text the model produced is genuinely unsettled. Copyright systems are built around human authorship, and the status of machine-generated output differs by jurisdiction, is actively being litigated and legislated in several places, and is not something this or any product page can resolve.

What the terms do is state a position anyway, because a company cannot operate without one. Three positions are common. The output is assigned to you, sometimes with restrictions on commercial use. The output remains the operator’s, licensed to you for personal use. Or the document is silent, which leaves you with whatever the underlying law provides and no contractual assurance either way.

For most readers this is abstract, because a private conversation is not being published. It becomes concrete in exactly two situations: if you wanted to publish transcripts, and if you wanted to move a character you had developed to another service. Both run into the same wall, which is that the character description itself is the operator’s, not a thing you have.

THE PRODUCT — ownership of the conversation

  · "You retain ownership of your content"
                    → true, and not where the rights are. The
                      licence beneath it is.

  · The licence grant
                    → host, copy, adapt, create derivative
                      works. Read for purposes, sublicensing,
                      and survival after deletion.

  · "Improve our services"
                    → the phrase where training use often
                      lives. Compare against the policy's
                      training language.

  · The replies the model produced
                    → legally unsettled. The terms state a
                      position because they must; the law
                      differs by jurisdiction.

  · The character description
                    → the operator's asset, not yours, and
                      not portable.

  · Which grant applies to you
                    → CHECK THE POLICY and the terms. Search
                      "user content", "licence", "survive".
                      THE OPERATOR DECIDES the wording and may
                      amend it.

What you can check

Search the terms for “user content” and read the paragraph after it. That paragraph is the whole subject. Everything above is a guide to reading four sentences.

Check whether the grant is sublicensable. One word, and it is the difference between a permission held by one company and a permission that can be passed along.

Check the survival clause. If licences survive termination — and they usually do — then deletion ends future use rather than retracting the past.

Keep your own copy if the text matters to you. An export is the only version of this you control, and what it contains is worth verifying early rather than at the point you need it.

What this doesn’t tell you

It does not tell you what any specific app’s licence says, and no named product’s terms are being described.

It is not legal advice. The status of machine-generated text, and the enforceability of any particular licence term, vary by jurisdiction and are contested in several of them.

And it does not tell you whether anyone will ever exercise the licence in a way that affects you. It tells you what was granted, which is the part that is written down.