Report content
Everything in this archive is AI-generated from frozen inputs, and it is published by one person. If something here infringes your rights, exposes material it should not, or is otherwise harmful, write to the address below and it will be taken down while it is reviewed.
§1What to include
A report is easier to act on quickly when it contains:
- The exact page or preview URL. The Revision page, the live Deployment address, or the source view — whichever shows the problem. More than one URL is fine.
- What is wrong. Which part of the page, and what the issue is: copyright, trademark, personal data, an exposed credential, defamation, or another concern.
- Your basis. If you are a rights holder or acting for one, say what you hold rights to and in what capacity. A link to the original work helps.
- How to reach you. An address that can receive a reply, so questions do not stall the review.
§2What happens next
- Withdraw first. On a plausible claim, the affected Revision is withdrawn before the review starts. Its live Deployment stops serving on the next request, and its public page keeps only a tombstone.
- Response within 72 hours. The target is an acknowledgement, and where possible a decision, within 72 hours of the report arriving. This is an operator commitment from a single-person project, not a contractual guarantee.
- Review, then restore only if unfounded. If the claim turns out to be unfounded, the same bytes are restored under the same address, and the action is recorded in the audit log. If the claim holds, the content stays withdrawn.
§3Exposed secrets
If you believe a real credential is visible in published source, say so plainly in the subject line. Those reports are handled first: the affected Revisions are withdrawn, the credential is revoked at its provider, and permanent deletion is available as an audited exception to the archive’s normal immutability.
See also Terms and privacy for retention and licensing, and Methodology for how content gets published in the first place.