SECURE DISPATCH

Secure Dispatch

Encrypted channels for time-sensitive or confidential contact. Three paths below — pick the one that matches your situation. All channels are monitored. None require a web form.

// ACTIVE BREACH — START HERE

If your AI system is actively leaking data or executing unauthorized commands right now: reach us on Signal.

Signal is faster than email, more secure than phone, and the channel security professionals actually use to coordinate sensitive comms. We monitor the incident channel continuously and respond as quickly as a real person can — usually within minutes, always within hours. Once engaged, we scope a response immediately and can have practitioners committed within 48 hours of confirmed scope.

// SIGNAL · INCIDENT CHANNEL@logicleak.01Signal app required. Add as contact and message ‘BREACH’ to trigger priority routing.Don’t have Signal? Get it at signal.org →
Signal QR code linking to @logicleak.01 incident response channel
Scan from Signal
// ENCRYPTED EMAIL · BACKUPir@logicleak.ioBackup channel if Signal is unavailable. Use PGP key from Section 3 for sensitive content.

These channels are reserved for active incidents. Non-breach contact via the channels below.

// VULNERABILITY DISCLOSURE
For security researchers reporting findings in LogicLeak's systems, tools, or website

We follow coordinated disclosure practices on findings in our own systems. Acknowledgement within 48 hours, remediation timeline confirmed within 7 days, remediation complete within 30 days for critical findings. We credit researchers (with their consent) in published disclosures.

// EMAIL · ENCRYPTEDsecurity@logicleak.ioPGP key required for sensitive content. Fingerprint below.
// PGP KEY · FINGERPRINTABCD 1234 5678 9012 3456  7890 ABCD 1234 5678 9012Download full key →
// BUG BOUNTY

No monetary bounty currently. We credit researchers in published advisories and reference contributions in our hiring conversations. Significant findings receive named acknowledgement in our Vulnerability Disclosures stream on /research.

// SENSITIVE INTAKE
Pre-engagement contact for prospects whose initial materials require encrypted handling

Most engagement inquiries can begin through standard channels — the audit request form on /services covers typical pre-engagement conversations. Use this path only when the initial conversation itself requires encrypted handling (regulated industries, undisclosed AI deployments, contracts under active negotiation, etc.).

// ENCRYPTED EMAILintake@logicleak.ioUse the PGP key in the previous section for encryption. NDA before any sensitive content.
// SIGNAL · INTAKE LINE@logicleak-intake.01Separate from the incident line. Used for pre-engagement and NDA discussions.
// OPERATIONAL COMMITMENTS
What we commit to on every channel above
// INCIDENT RESPONSE

Real person

Signal monitored continuously
// DISCLOSURE ACKNOWLEDGEMENT

< 48 hours

Vulnerability reports on our systems
// INTAKE RESPONSE

< 24 hours

Sensitive intake channels, business days
// CHANNEL MONITORING

24/7

Signal monitored continuously. Other channels: business hours.
// NOT THIS CHANNEL
What to send elsewhere

General engagement inquiries → /services or via the audit request form. These channels are reserved for time-sensitive or encryption-required contact.

Press, partnerships, or hiring → hello@logicleak.io. Not monitored 24/7 and not appropriate for time-critical outreach.

Legal or privacy questions → legal@logicleak.io or see /legal, /privacy. Routed and tracked separately from operational channels.

// CHANNEL VERIFICATION

If you need to verify these channels are legitimate before initiating contact: this page is accessible only at logicleak.io/firm/secure-dispatch. The PGP fingerprint above matches the key published at /pgp/security.asc. Our Signal usernames are confirmed in our Lead Investigator profile at /firm/lead-investigator. Any other ‘LogicLeak secure contact’ channel claiming these addresses or usernames is not us.

Last verified: May 2026 · Channel hashes available on request

All channels above are monitored by named practitioners, not autoresponders or AI.