Contact

We’re early. If you’re a privacy-minded developer, researcher, advisor, or funder who wants to help build the post-surveillance web, we’d love to hear from you.

Primary Channels

• General & Partnerships — hello@journalfoundation.org

  Short proposals, partnership ideas, intros.

• Specifications & Engineering — specs@journalfoundation.org

  Protocol/RFC feedback and reference implementation questions. Please also open public threads in GitHub Discussions → github.com/JournalFoundation/cipherlot/discussions

• Press & Speaking — press@journalfoundation.org

  Media requests, interviews, event invitations.

• Funding & Grants — grants@journalfoundation.org

  Philanthropy, research grants, programmatic support.

Community & Code

GitHub Discussions: GitHub Discussions → github.com/JournalFoundation/cipherlot/discussions
Best for public questions, RFC debates, and roadmap ideas.

Security / Responsible Disclosure

Report vulnerabilities to security@journalfoundation.org. Encrypt mail with our PGP key (download) and verify the fingerprint:

Fingerprint: 0000 0000 0000 0000 0000  0000 0000 0000 0000 0000
Key: https://journalfoundation.org/pgp.txt

We publish /.well-known/security.txt (RFC 9116) with these details.

Tips for Sensitive Outreach

You may use Signal: +1-281-532-5205. Signal shares your number with us; feel free to use a secondary number. We may introduce heavier-weight options (e.g., SecureDrop) as the program matures.

Response Policy

We triage new messages weekly. If we miss you, please nudge us or open a GitHub Discussion. Security reports are prioritized and acknowledged within 72 hours.

Privacy

No forms. No trackers. Email us or open a public thread; we don’t harvest, resell, or profile your contact info.