Rushchat’s FAQ says the chats and characters you create are private unless you choose to publish them. Its website privacy policy also says user content from character chats may be used to train AI models. Both statements can matter at the same time: a private audience setting does not, by itself, exclude provider processing.
Do not translate “private” into “no one at the service can process this” or “my messages can never contribute to training.” This guide separates those questions using the current published pages. It does not claim to have inspected the provider’s internal systems.
Start with the audience question
Audience privacy concerns who can discover or view a character or conversation through the service. A public character listing, a link shared with someone else and an unpublished creation can have different audiences.
The FAQ’s private-unless-published statement is useful here. Before publishing a character, review the description and any attached material as if an unknown reader might see it. Remove details that belong to a real person or reveal your own contact information.
A character written for your private use may contain shorthand that makes little sense publicly. Rewrite those notes for the intended audience instead of assuming a public toggle is the only preparation required.
Then ask what the provider processes
Service processing is a different layer. Generating replies requires handling the messages you send. The website policy describes user-content, account, technical and transaction data, together with a range of operational and commercial purposes.
Most significantly for this question, it expressly says chat user content may be used to train AI models. The policy does not make the private-character audience setting an opt-out from that statement. We did not verify a separate account control that changes the training rule, so this article does not invent one.
If this distinction changes whether you want to use the service, decide before entering sensitive material. Waiting until after a long disclosure leaves you with a more complicated data request.
Use a three-column information map
Make a simple map before starting an account or character:
| Information | Why you would enter it | Safer substitute |
|---|---|---|
| A workplace problem | Give the scene believable tension | An invented employer and a changed situation |
| A real street address | Establish a meeting place | A fictional district or public landmark |
| A private person’s biography | Create a consistent character | An original adult character with invented history |
| A payment dispute | Ask support to locate a purchase | A receipt reference in the official support channel |
The purpose is not to make every conversation vague. It is to keep useful fictional specificity while removing unnecessary real-world identifiers.
Do not submit health, legal or financial records simply because a character sounds sympathetic. An entertainment conversation does not become a professional confidential relationship through its tone.
Treat sharing as another separate event
A private conversation can become public through your own screenshot, exported text or social post. Check the whole image before sharing: account names, other open tabs and notifications can reveal information unrelated to the story.
The privacy policy also describes social-media interactions and information provided through public areas. Do not assume that posting a support complaint in a public community is equivalent to emailing an official support address.
If you need help with a broken feature, start with a redacted error and a short description. The relevant facts are often the time, device, account reference and failure behaviour, not the intimate content of the conversation.
If you want to leave or ask about data use
The website privacy policy describes email-based account closure and routes for privacy enquiries. State clearly whether you are asking about data access, deletion, a processing choice or a subscription problem; those are not interchangeable requests.
Use the current official contact shown in the policy and retain the acknowledgement. Do not infer a deletion deadline, a complete erasure guarantee or a training reversal from a short support reply unless the provider explicitly confirms that scope.
The practical decision is personal but concrete: can the fictional task be completed without entering information you would not want a service provider to process? If not, choose a different tool or a less sensitive version of the task before continuing.
Sources and scope
Official pages checked October 29, 2026. Examples and worksheets are original editorial material. No account-recovery, memory, payment or reporting operation is represented as tested.