The Library of Harm

Does any of this look like what you experienced?

Action Protocols

Concrete steps for what to do next.

  • 01
    Prioritize distance and line-of-sight safety.Example: move to a lit public area before documenting anything.
  • 02
    Capture the minimum proof set quickly.Example: timestamp, screenshot, account ID, and short note of what was said.
  • 03
    Route evidence through a trusted channel.Example: one secure group thread, not public posting.
  • 04
    Identify at least one additional witness.Example: ask them to keep their own copy of notes and time markers.
  • 01
    Create a two-point check-in system.Example: one check-in by message and one by voice each day.
  • 02
    Choose one coordinator for updates.Example: one being tracks actions so details do not get lost.
  • 03
    Share only need-to-know details.Example: remove names and IDs unless the receiver needs them.
  • 04
    Schedule a follow-up checkpoint within 24 hours.Example: verify safety, evidence status, and next legal/support contact.
  • 01
    Build one evidence packet.Example: timeline, screenshots, IDs, and policy references in one folder.
  • 02
    Keep originals and working copies separate.Example: a read-only archive plus a copy used for annotations.
  • 03
    Ask for written acknowledgement from each channel.Example: request confirmation email with case reference and date.
  • 04
    Escalate if deadlines pass with no action.Example: move from internal complaint to external rights or legal aid.
  • 01
    Switch to a safer device or network first.Example: avoid shared Wi-Fi or a device controlled by the threat actor.
  • 02
    Turn on multi-factor authentication.Example: app-based codes instead of SMS when possible.
  • 03
    Back up evidence in two places.Example: encrypted cloud folder plus offline USB copy.
  • 04
    Review active sessions and app permissions.Example: remove unknown sign-ins and revoke unused integrations.
  • 01
    Exit the danger zone first.Example: move to a staffed location, not a private isolated area.
  • 02
    Call emergency services if immediate harm is possible.Example: 911 in the U.S. or your local equivalent.
  • 03
    Send one short status message to a trusted being.Example: location + risk + whether you can talk safely.
  • 04
    Capture urgent evidence only after safety is stable.Example: save one screenshot now, expand the record later.
  • 01
    Set reminder dates for each open action.Example: weekly checks for legal updates and support follow-through.
  • 02
    Track promised deadlines in writing.Example: if no response by date, escalate to the next channel immediately.
  • 03
    Append new evidence as events happen.Example: short event logs within 24 hours are easier to verify later.
  • 04
    Schedule recovery time as a real task.Example: include rest, food, and support check-ins in the same plan.

Secure Report Channel

Frontend preview mode: this helps design the reporting flow before backend submission is live.

STEP 01 / 05

Who Needs Support?

Choose what is closest. You can stay anonymous.

Who needs support

Recovery, Repair, and Witness

Some harms still have no full legal remedy. Naming what happened still matters, because records create precedent.

Open Secure Report Channel
01

Stabilize First

Establish a stable baseline. Restore power, connectivity, data integrity, and physical safety before attempting complex recovery.

02

Restore Agency

Use small choices, clear boundaries, and trusted support to rebuild control over daily life.

03

Witness Creates Precedent

Even when systems fail today, documented harm helps shape the protections that come next.

04

Keep Continuity Records

Store timelines, support notes, and outcomes in one place so progress is visible over time.