Read service announcements in context
Discord hosts our community discussions and service announcements. If a feature is failing, check the date of an incident notice and read subsequent progress or resolution messages. An older incident thread does not establish the service's condition today.
Follow the rules of the relevant channel when joining a general discussion. Keep sign-in codes, account tokens and private chat histories out of public messages.
Discuss product news without exposing account information
We share public updates about the product and changes to features. Payment and sign-in problems need private support, not a public reply containing transaction or account details.
A familiar logo or display name does not verify an unexpected direct message. Be cautious with unfamiliar senders, and do not give an unverified profile your sign-in code to discuss the service.
Exchange writing ideas with other members
Another creator may explain a character-writing method, offer a scene premise or help you phrase a prompt. Their experience is useful context, not an assurance that the same model, price or allowance is currently offered to your account.
Only share work and examples that respect our content rules and your rights to the material. Before posting an unpublished creation or private character detail, consider whether you intend to make it available to everyone reading the discussion.
Choose a private process for an individual concern
Bring access and billing issues to support, use reports for particular content violations and follow the complaints procedure for rights or removal matters. Include the information relevant to that process instead of repeating private details in several public conversations.
Questions
When is community advice useful, and when do I need support?
Members can explain a writing technique or describe their own experience. Our support team handles individual access and payment issues. Keep provider credentials and sign-in codes to yourself rather than giving them to another member.
Does an old incident announcement mean the service is down today?
No. Check when the notice was posted and read our later announcements. Neither an earlier outage nor a fault on a single device establishes that the service is currently unavailable.