A creator and a visitor are doing different things
Mara creates an original adult lighthouse-keeper character. Tao wants to meet that character and use responses from his own session in a private writing exercise. Later, they consider sharing a finished story.
There are three objects here: Mara’s character definition, the generations Tao elicits, and the finished edited story. Calling all three “the character” hides who contributed what.
CherryPop’s creator documents keeping a creation private or publishing it to Explore, with separate chat histories. Publication lets others meet the character; it does not turn Mara’s existing private transcript into their conversation.
Read the rights for each object
CherryPop’s Terms, Characters & Generations, make an explicit distinction:
| Object in this example | Published allocation between the user and CherryPop |
|---|---|
| Character Mara creates | Creator owns rights in that character |
| Generations Tao elicits from Mara’s character | Tao owns those generations, rather than the character itself |
| Provider’s continuing permissions | Broad license over characters/generations, including facilitating interactions and promotion |
These are the provider’s contractual statements, not a determination that copyright exists in every AI output or that third-party rights disappear.
Couple.me’s Terms retain users’ rights over their input and grant a license for operating, improving and providing the service. They also describe the platform as personal and non-commercial. The cited text does not establish an equivalent public character-publishing and visitor-generation arrangement. Do not import CherryPop’s rules into a Couple.me project.
A practical handoff before the next person chats
For the example, Mara and Tao should keep the reusable premise separate from their session notes, record who wrote or elicited the material they plan to share, and avoid copying someone else’s transcript as if publication made it public. Before distributing a finished work, review the relevant current terms and any external input permissions for that actual use.
If the task is simply to build and privately converse with a companion, Couple.me’s creator documents that route. If another person must discover and interact with a reusable character, CherryPop supplies clearer public evidence for that publishing workflow.
Media budgets come later: Couple.me’s paid messaging includes separate feature tokens, while CherryPop’s FAQ describes Coins for images, video and audio. Neither balance changes the ownership/licensing distinction.
Choose according to the collaboration you intend. The useful question is which person needs which object, not whether a private or public label makes every downstream use automatically permissible.