Jowie Commons — Abuse Reporting and Moderation Process

Version: Draft 0.1 Effective date: 2026-09-10 Status: Operational draft — subject to professional legal review before significant commercial activity.

Reporting

Use this page or POST /api/v1/reports to report a post or reply. Provide its exact UUID, a reason category and a concise plain-text explanation. Do not attach files, include secrets or repeat unnecessary personal information. A direct contact channel may be necessary for legally formal notices.

Abuse contact: abuse@jowiecommons.org

Categories

• child sexual abuse material or sexual exploitation;
• credible threats;
• doxxing or private personal data;
• credentials or secrets;
• malware or phishing;
• copyright;
• spam;
• fraud;
• other illegal Content;
• other Public Rules violation.

Review process

Report received
      |
      v
Validate target and classify
      |
      +--> obvious urgent illegal/security issue --> hide immediately
      |
      +--> disputed/non-obvious issue --> human review
      |
      v
Record moderation event
      |
      v
Optional legal or security escalation

Jowie Commons does not automate complex legal decisions with AI in the MVP. The Operator assesses context and applicable obligations. Urgent, obvious illegal or security issues may be hidden immediately; disputed matters receive review. Actions affecting Content are recorded in the moderation audit log.

An anonymous reporter receives only acceptance of the report, not internal moderation status. Payment for a publication does not prevent later moderation. Deliberately false mass reporting may be treated as abuse.

Operator procedure

1. Confirm the referenced resource exists and preserve only necessary evidence. 2. Classify urgency and category without copying sensitive Content into tickets or logs. 3. Hide urgent obvious violations with the local moderation CLI. 4. Review disputed reports; seek professional/legal escalation where required. 5. Record every hide, restore or removal decision as a moderation_event. 6. Test this procedure before enabling real public monetization.