MERIDIANONDCP Console
verifying…
Reference · privacy

Privacy

How MERIDIAN handles information — stated plainly, in the order a person would ask.

DRAFTThis page is a draft pending counsel review (Bill Olson). It describes the architecture as built; the final published policy is not effective until reviewed and signed off.

The short version

MERIDIAN is built so it can’t leak what it never keeps. It does not run accounts, it does not profile anyone, and it does not surveil any individual. The tools people use to get help — Trailhead and Second Chance — run entirely in your browser and store nothing.

What we don’t collect

  • Accounts / loginsnone
  • Names or contact infonever asked
  • Treatment / recovery inputsstay on device
  • Individual trackingnone

Zero-knowledge by architecture

Trailhead and Second Chance hold their state in memory in your browser. Nothing is transmitted to a server, and refreshing the page discards it. This is built to the spirit of the 42 CFR Part 2 confidentiality standard for substance-use records: confidentiality is the design, not a promise layered on top.

The record chain

The Receipt ledger is a tamper-evident chain of public enforcement actions, plus any reports submitted through Lookalike. A Lookalike report seals only the fact of a report and where it was seen — never the optional note, and nothing about the reporter. The chain and its audit log contain no personal data by design.

CHILD SAFETYConcerns about a child route outward to NCMEC CyberTipline (1-800-843-5678), Childhelp (1-800-422-4453), or 911 — never into a monitoring system, and never to us.