Secure Drop Intake Paused

SECURE
DROP

Public submissions are paused for now. This page still explains the intake path, the current storage boundary, and the source protections that need to be stronger before public intake opens back up.

Back to Directory Read Standards

What this route is for

Use this page for documents, screenshots, spreadsheets, and primary source material that help build a real public-record case file.

What happens next

A valid intake should create a dossier name, narrative, classification flag, and evidence bundle that can move into the internal review queue.

Current guardrail

Public intake stays paused until metadata stripping, safer source guidance, and stronger review rules are in place.

Public intake paused

The route is visible, but the public inbox is still gated

The secure-drop foundation is in place, but public intake remains paused until source-handling policy, metadata stripping, and review workflow hardening are stronger. The form stays visible so the submission structure is clear before it goes fully live.

Submission Form

Secure Drop Structure

The form fields remain visible so the intake structure is legible while public uploads stay paused.

When this route reopens, it will collect dossier name, narrative, reliability, classification, and encrypted evidence files through the same fields shown here.

Dossier Name / Subject

Narrative / Why This Matters

Source Reliability

Classification

Evidence Upload

Upload Path Staged

The upload surface stays here as a placeholder while public intake is paused.

inventory_2

Submission workflow staged

The upload surface is visible for review, but public uploads are disabled

Public uploads are currently disabled.

Submission acknowledgement

Public submissions are paused. This panel remains here so the intake rules and source-handling posture are visible before the route goes live again.

I understand this route currently explains the intake process but is not collecting public submissions yet.

Status: public submissions paused

Before You Send

Make The Reviewer's Job Easier

A clean intake is easier to verify and much safer to handle. These checks matter more than sounding dramatic.

Remove anything you do not need to share. Keep the file set tight and relevant.

Explain what the evidence is, how you got it, and why it matters before assuming the files speak for themselves.

Do not use this form for emergencies, threats, or time-critical safety incidents.

If you are sharing a claim about someone, include the records that let us verify it.

Hardening Roadmap

What Still Needs To Improve

This is the restraint layer for the secure-drop route. It makes the unfinished security work explicit instead of pretending the page is stronger than it is.

Automatic EXIF, GPS, and document-author metadata scrubbing.

Safer public instructions for source anonymity and operational security.

Stronger intake triage rules before materials move into active reporting.

Source Protection

How The Current Intake Is Meant To Protect Sources

These are the concrete guardrails already visible on the route, plus the next protections the page still owes sources before calling itself fully hardened.

Private storage boundary

Uploaded evidence is written to private server storage that is not exposed as a public file directory. That storage boundary is already separated from the public site.

Metadata hardening next

Automatic EXIF, GPS, and author-metadata stripping is still on the security roadmap. Public intake should stay conservative until those protections are stronger.

Encrypted at rest

When intake is enabled, uploaded files are encrypted on the server before storage. Key handling stays off the public site.