A dedicated intake
Publish the intended organization’s intake route and make its purpose clear.
Sealed Tip
Give people an intake link for encrypted tips or supporting material. Keep the submission route separate from an ordinary email inbox or public feedback wall.
No phone number or email required for core Hat use.

The useful difference
Publish the intended organization’s intake route and make its purpose clear.
The documented tip flow encrypts content before delivery to the recipient.
Define who reviews submissions, how recipients verify the route and what retention rules apply.
How it works
Set up the supported Intake Hat and review its public link.
Explain acceptable material, response expectations and the risks outside the encryption boundary.
Authorized recipients use the supported retrieval flow and follow their own handling procedures.
Know the boundary
Encryption does not guarantee anonymity or protection from retaliation. Content, attachments, devices, traffic and details volunteered by the submitter may identify a source. For high-risk situations, review the threat model before submitting.
Review the security evidenceQuestions, answered
Open City of Hats to review the controls available for your client, content and plan. The app shows applicable requirements before you proceed.
Verify the recipient, use a supported device and choose appropriate access and retention rules. Review the Security Evidence Center for boundaries and evidence status.
City of Hats is free to use. Feature availability and limits vary by plan and client. Premium is optional; review current limits in the app or on the plans page.
Explore what matters next
Start with a Hat
Start free. Choose your controls as the work requires them.