Jump to any public page from mobile without losing the side-rail structure on desktop.
This page explains the current contact model honestly: there is not a broad public inbox yet, the secure-drop route may be paused, and source protection rules come before convenience.
These pages exist to make the publication model legible instead of burying legal and trust information in a dark corner.
If a source intends to send sensitive documents, the correct question is not just where to send them, but whether the intake and handling model is actually safe enough yet. That is why the public secure-drop route is visible even when public intake is paused. The site would rather be explicit about the boundary than pretend a risky inbox is acceptable.
For now, the strongest public accountability path is still the publication itself: source stacks, story pages, and the operations page that explains how updates and corrections are supposed to work. That is not a permanent replacement for a reader contact channel, but it is the current honest state of the site.
A broad public contact inbox is not live yet. The project is still prioritizing source protection, review workflow, and public-facing standards before opening another intake surface. When a public contact method goes live, it should be narrow, legible, and consistent with the same privacy and source-handling rules described elsewhere on the site.
Use the secure-drop page to check whether protected intake is open, the operations page to understand publication rules, and the stories or investigations pages to inspect the actual sources behind any claim. That is less convenient than a polished contact form, but it is more honest than implying a communications channel exists before the team is ready to operate it safely.