Lovescape Public Character vs Private Conversation: Different Visibility
Read Lovescape’s published distinction between a shared fictional character profile and separate conversations, without treating a visibility setting as a complete privacy guarantee.
Lovescape’s public explanation distinguishes a public character profile from each user’s separate conversation. Its profile help says sharing depends on public visibility. Those are provider statements about what users can see, not an independent guarantee about all provider processing or retained copies. Identify the specific object and current setting before sharing a link.
A fictional character profile and a conversation with that character are different objects. Lovescape’s profile help ties sharing to public visibility. Its privacy and safety explanation separately discusses user conversations.
The distinction is useful when a profile link is visible to someone else. It prevents that observation from being expanded into an unsupported conclusion about every private exchange.
Name the object you are checking
A profile may contain its name, description and selected profile media. A transcript contains the actual exchange in a conversation. A copied link and a screenshot are also different forms of sharing: a screenshot can expose whatever its sender includes, regardless of a profile’s access control.
Before sharing anything, identify which object is involved and which parts of it contain information you intend others to see. Use fictional details rather than real personal data for a visibility check.
What the provider says
The safety post says other users of a public character have their own conversations and cannot see yours through that public character. This is a provider claim about ordinary-user visibility. We have not authenticated two accounts or audited the access controls.
Do not infer that publishing a profile necessarily publishes its creator’s entire transcript. Equally, do not infer that a private profile prevents the creator from separately sharing a screenshot or copying text elsewhere.
Keep another privacy question separate
Whether an ordinary visitor sees an object is different from what the service processes to operate or moderate it. A visibility switch alone does not establish training use, staff access, retention or the handling of a support report.
If those questions matter, ask about their specific scope and consult the current applicable policy. A public-profile observation cannot serve as evidence for every backend privacy claim.
Make a minimal observation
For a harmless fictional profile, record its current visibility state and the surface actually observed by the intended viewer. If something unexpected appears, identify the field or object rather than calling the entire account public.
Do not publish a sensitive conversation as proof of a privacy concern. Use the official private support channel with the relevant reference and a minimal description.
A useful conclusion is precise: this profile field was visible in this context, while the conversation has its own documented scope. That is more defensible than treating a public character, a private chat and provider processing as one universal privacy setting.
Sources and verification
This guide distinguishes published documentation from examples and observations. Feature access, policies and account screens can change; the linked source governs its own terms.