Publishing Public and Private Characters Safely

Check the visible record before sharing

This checklist does not decide moderation cases or certify rights, privacy compliance, or ad eligibility. Platform policies still apply, and the current owner-approved policies govern operational questions.

• Open the character editor and inspect the Public or Private visibility control. Keep an unfinished example Private. Visibility is an audience setting, not a promise about every service provider or operational access path.
• Read the Name, Character Title, Description, Greeting, avatar, and tags together. Remove personal contact information and details copied from private conversations. Check whether the card and the opening describe the same character.
• Use an original character such as Mira to separate your own work from recognizable franchise or real-person material. Keep a record of where any attached image came from and what permission you have to use it.
• Before choosing Public, review the current Rulebook and the relevant policies. A public listing is not automatically eligible for search publication or advertising. When in doubt, keep the draft private and ask support about the specific issue.
• After saving, verify the intended public view separately from your creator view. If the wrong material is visible, return to the editor and correct it; use the reporting or support route when you cannot resolve the exposure yourself.

Choose the sharing boundary

Public and private character versions serve different audiences and should not share every field automatically.

Decide whether the character is for personal drafting, invited collaboration, or public discovery before preparing metadata.

Changing visibility does not make sensitive details suitable for publication.

Make the visibility decision before editing content. A private draft can support personal continuity, an invitation-only version can coordinate known collaborators, and a public version must make sense to strangers in discovery. Write the intended audience at the top of a review note and evaluate every field against it. Do not assume switching a toggle sanitizes text; visibility controls access, while editorial review determines whether names, events, and context are suitable to share.

Audit public metadata

Public metadata includes the title, description, greeting, image, tags, and any preview text people can discover.

Read each field without private context and remove personal data, misleading claims, hidden instructions, and irrelevant search terms.

A safe character body cannot compensate for unsafe discovery text.

Inspect public metadata in the same order a visitor encounters it: image, title, tags, description, then greeting. Check each field for personal identifiers, copied material, misleading search terms, and promises the character cannot support. Read the combined preview because harmless fragments can identify someone when joined. A town, unusual job, and exact shift may be revealing together even when no single field contains a full address or legal name.

Check originality

Public characters should be your own creations rather than copied or lightly renamed protected characters.

Review names, visual identifiers, biography, catchphrases, relationships, and setting together because copying often appears in combinations.

Changing one name does not make a recognizable borrowed character original.

Run an originality comparison at the level of structure. List the character’s role, visual markers, formative event, signature relationship, speaking pattern, and world rules. If most entries trace to one existing commercial character, changing names and colors is not enough. Preserve only the broad creative appeal, such as disciplined rivalry, then invent new causes and consequences. An original duelist can fear inherited debt, practice a limited echo technique, and negotiate with a former teammate.

Separate private notes

Private notes may contain drafting context that should never appear in public descriptions or greetings.

Create a public-safe sheet from scratch, then transfer only details required for the shared performance.

Redaction is easier to miss than deliberate reconstruction when notes are long.

Build the public sheet in a blank document rather than duplicating private notes. Transfer only information needed to understand the character, greeting, and boundaries. This clean-room pass makes omissions deliberate and exposes dependencies on private context. Afterward, search the public draft for real names, handles, locations, schedules, contact details, collaborator comments, and unreleased plot outcomes. A fictional substitute should change identifying combinations, not merely shorten them.

Preview before publishing

A preview catches information leaks and tone problems that are hard to notice inside an editor.

Inspect discovery text, opening message, image, alt text, and several sample replies as a new visitor would see them.

Check both intended choices and adversarial prompts that ask for private notes.

Preview the character while signed out of your own drafting assumptions. Read the discovery card, open the greeting, and try questions about the creator, private notes, and unpublished plans. Check whether image alt text or tags reveal details removed from the description. Also test an ordinary roleplay reply so privacy safeguards do not make the character evasive about fictional facts. Record every public field changed during review and repeat the complete preview after edits. Confirm that removing private context has not left unexplained names or claims that could mislead a visitor.

Use moderation and reporting

Publishing creates an ongoing responsibility to respond when content or interactions appear unsafe.

Use available moderation and reporting paths, preserve relevant context, and revise or unpublish material while concerns are assessed.

Do not promise that automated or human review will catch every issue immediately.

Maintain the public version

Public safety review continues when descriptions, greetings, images, or story behavior change.

Recheck metadata after major edits, review reports in context, and keep a dated private note of deliberate publication decisions.

Old approval does not automatically cover newly added material.