Follow our announcements on Discord
We use Discord for community discussion and service announcements. When something is not working, look for a dated incident update and its follow-up messages. A discussion of a previous incident does not tell you the current condition of the service.
Choose the relevant channel and follow its rules when asking a general question. Keep account tokens, sign-in codes and private conversation histories out of the discussion.
Keep public feedback separate from account details
Our public updates cover product news and feature changes. If your concern involves a payment or sign-in, take it to support instead of including account or transaction information in a public reply.
Treat an unfamiliar direct message cautiously even when its sender uses a recognizable name or logo. An unverified profile does not need your sign-in code in order to discuss our service.
Learn from other creators
Community members can offer a scene idea, explain how they write a character or suggest a clearer prompt. Their experience is not a promise that a model, price or account allowance is still available to you on the same terms.
Share original work and examples only within the content rules and the rights you hold. Do not include private character details or unpublished material in a public discussion unless you mean to make that information available.
Bring private matters to the right process
Our support team handles access and payment questions. Content reports identify particular violations, while complaints cover rights and removal requests. Send the references and details that process needs rather than spreading the same private issue across several public threads.
Questions
What kind of help can another community member provide?
They can discuss their experience or explain a writing approach, but account-specific access and payment matters need our support team. Never hand another member your provider credentials or sign-in code.
How should I interpret a post about an earlier outage?
Read its date and compare it with our current announcements. An old incident, or a problem reported on one device, is not evidence that the service is unavailable now.