⚠️This article has been marked as incomplete. Sourcing or verifiability needs additional work.
A moderator needs to check the page before this notice can be removed. Visit the
noticeboard or the
#appeals channel in either
Zulip or
Discord to request removal.
More info ▼
Articles must provide verifiable, credible evidence for their claims and avoid relying on forum posts, personal blogs, or other unverifiable sources. You can help by replacing weak citations with reputable reporting, corporate communications, receipts, repair logs, or independent investigative coverage that demonstrates the systemic relevance required by the Mission statement and Moderator Guidelines.
❗This article is a stub. You can help by expanding it.
A moderator needs to check the page before this notice can be removed. Visit the
noticeboard or the
#appeals channel in either
Zulip or
Discord to request removal.
More info ▼
An article may be flagged as a stub when it is missing major elements needed to make it useful to a reader. You can help by adding missing sections, verifiable sources, relevant company policies and communications, etc. to make the article more complete.
Short summary of the incident using references.[1] Usually 2-3 sentences that summarize the contents or the article. When writing the article, insert text in the space below this box, and then delete this tip box (and the other tip boxes below). In the visual editor, just click on a box and press backspace to delete it. In the source editor, simply delete the double curly brackets, and the text inside them.
Add your text below this box. Once this section is complete, delete this box by clicking on it and pressing backspace.
Background
Information about the product/service history to provide the necessary context surrounding the incident
Add your text below this box. Once this section is complete, delete this box by clicking on it and pressing backspace.
[Incident]
Change this section's title to be descriptive of the incident.
Impartial and complete description of the events, including actions taken by the company, and the timeline of the incident coming to the public's attention.
Add your text below this box. Once this section is complete, delete this box by clicking on it and pressing backspace.
[Company]'s response
If applicable, add the proposed solution to the issues by the company.
Add your text below this box. Once this section is complete, delete this box by clicking on it and pressing backspace.
Lawsuit
If applicable, add any information regarding litigation around the incident here.
Claims
Main claims of the suit.
Rebuttal
The response of the company or counterclaims.
Outcome
The outcome of the suit, if any.
Add your text below this box. Once this section is complete, delete this box by clicking on it and pressing backspace.
Consumer response
Summary and key issues of prevailing sentiment from the consumers and commentators that can be documented via articles, emails to support, reviews and forum posts.
Add your text below this box. Once this section is complete, delete this box by clicking on it and pressing backspace.
References
Add a category with the same name as the product, service, website, software, product line or company that this article is about.
The "Incidents" category is not needed.
Add your text below this box. Once this section is complete, delete this box by clicking on it and pressing backspace.
