Contact
Real humans on real channels.
Every address below reaches a person who can act. Choose the door that fits — and for product help, support has its own path.
01 / FOUR DOORS — EVERY ONE A REAL MAILBOX
Pick the door, then write to a person.
-
General
Anything without a sharper door
Questions, ideas, partnerships — a person reads it.
-
Press
Interviews and accuracy checks
The press kit answers most of it; write for the rest.
-
Security
Vulnerability reports
Good-faith research is covered by the published safe harbor. Put SECURITY in the subject and include reproduction steps and impact.
-
Evaluation
Government and enterprise evaluation
Conformance evidence, deployment questions, formal review.
Product help lives at Support — answers first, tickets second. There is no chat widget, no phone tree, and no bot on any of these channels.
02 / BEFORE YOU WRITE
Read the three answers first.
How fast do you respond?
We do not publish a response-time promise we have not earned yet. Security disclosures are read first; everything else follows in the order it arrives.
Can I encrypt my report?
A PGP-clearsigned copy of security.txt ships after the key ceremony; until then, the plain-text policy at /.well-known/security.txt is the canonical reference for the security channel.
Where do legal requests go?
To the same doors, in writing. What a request can actually yield is a property of the architecture — the carrier model states it primitive by primitive.