Furries PH Docs
Dashboard
Report system docs

Best Practices

Evidence Handling

How to capture, reference, protect, and review screenshots, logs, links, witness notes, and identity evidence.

First created Last updated

reportsevidenceprivacybest-practices

Overview

Evidence handling is the privacy-aware process of capturing enough proof for review without spreading unnecessary personal data. The Report System stores evidence references in markdown-ext fields and identity links through person profiles.

Evidence workflow

flowchart TD
  capture["Capture source evidence"] --> classify["Classify screenshot, log, link, witness, identity, or prior record"]
  classify --> redact["Remove unrelated sensitive data where appropriate"]
  redact --> record["Record in evidence or notes field"]
  record --> verify["Verify authorized reviewers can access it"]
  verify --> maintain["Check links during record maintenance"]

Evidence inputs

InputWhat belongs thereSafety check
EvidenceScreenshots, links, logs, photos, files, or named evidence locations.Confirm access and avoid exposing unrelated people.
Victim statementAffected person’s account.Preserve wording and consent expectations.
Witness notesWitness context and follow-up pointers.Keep witness contact data limited.
Prior historyOlder confirmed reports or warnings.Mark uncertainty and source.
Reported person identity fieldsNames, handles, email, location.Add only relevant, reasonably verified identifiers.
Person Profile aliasesIdentity signals across reports.Do not link reports based on weak similarity alone.
Appeal reasonNew evidence or context for network-ban review.Keep it factual and reviewable.

Review checklist

CheckWhy it matters
Source is reachableReviewers need access later.
Timestamp is clearChronology affects status, severity, and action.
Context is includedScreenshots without platform/channel context can mislead.
Privacy is limitedUnrelated DMs, minors, legal names, and contacts need extra care.
Evidence matches labelsViolation categories and severity should match source material.
Links render in DetailMarkdown should not hide broken or unsafe links.

End-to-end operator runbook

  1. Collect evidence: Save or reference source material before memory fades.
  2. Reduce exposure: Remove unrelated sensitive content where safe to do so.
  3. Describe source: Add date, platform, channel/event context, and who supplied it.
  4. Verify access: Open the rendered Detail page as an authorized reviewer.
  5. Maintain links: Re-check high-risk evidence during review or closeout.

Common mistakes

Do not paste private identity or contact details into multiple fields just because they are available. Add the minimum needed for safety review and keep the source report as the authority.

All docs