Records, context, and accountability

Contribute Records

This page describes the archive’s planned intake routes and source-handling terms. The preview form is intentionally disabled: it has no upload service, submission endpoint, analytics script, or API key.

Do not enter or upload sensitive material here. A separately reviewed secure intake channel must be activated before submissions can be received.

Privacy and authorization: This archive collects only the information visitors choose to provide, plus basic privacy-respecting analytics. Confidential-source submissions are handled separately from public evidence canon. Do not submit illegal recordings, hacked materials, or documents you are not authorized to share.

Choose the appropriate route

What the archive can review

1. Submit a document

Describe a public record or document you are authorized to share. Include its origin, date, issuing body, and any public locator. Do not send raw files until the archive provides an approved secure-upload route.

2. Share background information

Provide context, reporting leads, record locations, or questions that may help locate public evidence. Background information is a lead, not a published finding.

3. Contact as a confidential source

Use only a separately designated confidential channel once it is available. Do not use an ordinary web form for source-identifying or safety-sensitive material. Review the confidential-source protocol first.

4. Submit a correction

Identify the exact page, wording, or metadata at issue; state the requested change; and cite supporting records where possible. See the corrections procedure.

5. Submit right of reply

Named or materially affected people and entities may provide a denial, explanation, contextual statement, or supporting record. See the right-of-reply procedure.

6. Journalist inquiry

State your outlet or affiliation if you choose, the record or topic you are researching, your deadline, and whether you are requesting documents, methodology, or comment.

Design preview only

Planned intake form

All controls are disabled and no information is transmitted or stored. The final intake must receive security, privacy, editorial, and legal review before activation.

Submissions are not enabled. This preview has no working upload field or server endpoint.

Submission details — disabled preview
List only people, organizations, assets, courts, agencies, or record systems necessary to understand the submission.
Describe provenance, date, issuing body, public locator, authorization to share, and what the document may establish. Do not paste sensitive contents into this preview.
Requested status is not accepted until an archive representative confirms the terms in writing.
Permission to follow up
Secure upload
Secure-upload placeholder — no file chooser or upload endpoint is active

Publication boundary

7. Evidence labels and source handling

A source’s requested status governs how the archive may use and attribute the conversation only after the terms are confirmed. These labels do not create attorney-client privilege, guarantee publication, or by themselves establish a legally binding confidentiality agreement.

On the record
Information may be quoted and attributed to the source by name and agreed affiliation.
On background
Information may inform reporting and may be quoted under an attribution description agreed in advance.
Deep background
Information may guide reporting without a quotation or source description unless different terms are confirmed.
Off the record
Information is not for publication and should not be independently used without a separate agreement. The archive must agree to this status before disclosure.
Confidential
Identity and source-identifying material are restricted to the smallest authorized team and handled outside public evidence canon. Technical and legal limits must be explained before intake.

How submitted material is handled

  1. Separate confidential-source material from ordinary editorial, correction, reply, and journalist queues.
  2. Minimize personal data and quarantine files for authorization, malware, provenance, and sensitivity review.
  3. Verify claims against public or independently reliable records. A submission is not evidence canon on receipt.
  4. Apply the archive’s labels: confirmed, corroborated, alleged, hypothesis, disconfirmed, procedural, or not adjudicated, as appropriate.
  5. Redact private contact details, source identities, and unnecessary personal information before any publication review.
  6. Publish no raw document automatically. Material requires editorial and, where appropriate, legal review.

Before sharing anything

Protect yourself and others