Chirp works because it stays credible. These rules keep it a record, not a pile-on.

Chirp is for:documenting your own experience (or, with a source, a publicly reported one) of a platform’s support failure — wrongful or automated suspensions, lockouts and verification loops, billing errors, hacks and account takeovers, glitches, and dead-end support.

File honestly.

• Describe what happened to you, in your words. Don’t state things as proven fact that you can’t back up.
• Attach what you have — screenshots, ticket numbers, dates, what you already tried. Evidence raises a case above the default “unverified.”
• One real problem per case. Don’t file the same issue many times to inflate it.

Don’t:

• Name or expose private individuals. Criticize the company and your experience with it — never a specific support agent, employee, or other private person by name, photo, or contact info. This is removed on a fast track.
• Post private information — anyone’s real name (for non-public people), home address, phone number, account email, or anything that could identify or endanger a person.
• Brigade or target a person. Backing a case is documenting a shared problem, not organizing a mob against anyone.
• Post illegal content, malware, account-cracking instructions, impersonation, spam, or scams.
• Sexualize or endanger minors — ever. This overrides everything and is reported to the appropriate authorities.
• Misrepresent who you are or file on someone’s behalf without citing a public source.

Embedded/linked content counts too. Anything you embed or paste is subject to the same rules and the same removal controls.

Breaking these can get a case hidden or removed and an account restricted. Child-safety violations are acted on immediately.