CrushOn vs Character.AI public-profile privacy should begin with the information you plan to expose. A character description, a hidden definition and a private conversation concern different surfaces. One visibility setting should not be used to answer all of those questions.
Official sources were reviewed on October 8, 2026. This guide proposes a public-information review and does not inspect provider servers or claim that every account exposes identical controls.
Inventory the public surface
Use an original adult fictional radio host. The character needs a stage name and program premise, not a real phone number or private address. Read the card through the supported ordinary viewing route and list the visible fields.
Inspect the current CrushOn card and creator controls. Character.AI documents character visibility and separate definition visibility rules. Use the stated scope of each setting rather than guessing from its label.
| Surface | Question to ask |
|---|---|
| Character name and card | What can a visitor read? |
| Creator profile | Which identifiers appear? |
| Definition | What setup can another user inspect? |
| Shared excerpt | What does your own sharing action reveal? |
| Conversation processing | Which provider policy governs sent text? |
Remove private drafting information
Before publishing, review every public-facing field for personal details and copied feedback. Keep private planning notes outside the released description. If an image is used, confirm your permission for that specific publication context.
A character can be entirely fictional and still expose a creator’s personal information through careless field choices. Visibility controls cannot remove information that you deliberately place in a visible description.
Check access and definition independently
Determine whether a character can be discovered through browsing, reached through a link or accessed under a restricted setting. Then inspect which definition fields are visible. An unavailable control is a result to record, not a reason to invent an equivalent option.
Do not assume that hiding one long definition field hides every attribute. Character.AI’s documentation distinguishes definition exposure from character access; inspect the current shared surface after saving.
Treat shared transcripts as another publication
If you publish an excerpt to demonstrate the radio-host role, review the excerpt separately. Use a short original fictional exchange and remove unrelated personal context. Public-card settings should not be assumed to protect a screenshot you share yourself.
Provider handling of the conversation requires a separate policy review. This article has not verified storage, moderation access or backup deletion and makes no backend confidentiality guarantee.
Choose by understandable exposure
Choose the service whose current controls let you match the intended audience and inspect the information being released. Keep the original master brief privately and check the published result before promoting it.
Does a public character mean all chats are public?
Do not infer that. Character access and individual conversation disclosure are separate questions.
Does a private card establish complete confidentiality?
No such guarantee follows from discoverability alone. Review provider data policies independently.